0.1.12

Another threadcap update:

• Support for Threads ActivityPub
• Support for Bluesky

0.1.11

Another threadcap update:

• Fixed the AP summary property calculation for some instances

0.1.10

Another threadcap update:

• Add the AP summary property to the normalized Comment object, since Mastodon uses it for content warnings

0.1.9

Another threadcap update:

• Support for http request signing to enable fetching comments from Mastodon instances in "secure mode"

0.1.8

Small threadcap update:

• Fallback to non-standard comments more often if replies are not found, handle OrderedCollectionPage type

0.1.7

Another threadcap update:

• Optimized twitter protocol to make far fewer calls in general, achieving much better performance when enumerating large threads in particular.
• Since Pleroma is known to not support the ActivityPub replies property, crucial to enumerating child replies for a given post, fallback to using the Mastodon API to find the replies only in this case.

0.1.6

• Update to the Deno std lib dependencies (@0.129.0) corresponding to the latest Deno release 1.19.3, which once again works on older linuxes like Ubuntu 16.04 and Amazon Linux 2
• Big threadcap update
  • Documented threadcap json example in the readme
  • Remove optional chaining syntax from npm esm js to support older environments
  • New experimental support for two new underlying comment protocols (lightningcomments and twitter) in addition to activitypub, pass new optional protocol option into makeThreadcap, protocol will be saved as a new top-level threadcap property
  • (breaking change) Threadcap root is gone, replaced with a roots string array, to support protocols that return multiple top-level nodes, there will still always be a single root id for the activitypub protocol
  • Commenter url and fqUsername are now optional
  • RateLimiterInput, WaitingForRateLimitEvent renamed hostname -> endpoint, to support protocols that have different endpoint-specific limits, like Twitter
  • New bearerToken option to makeThreadcap, updateThreadcap to support the Twitter implementation, which makes underlying Twitter api calls using this token

0.1.5

• More http request info logging when running rpc-based cli commands with --verbose
• New --verbose option for minipub server, logs stringToSign to help debug http-signature-auth issues
• Fixed a bug with the server verifying http signatures when the request host header does not match the public origin hostname
• Include redundant content string property in Note payloads as a workaround for the WordPress ActivityPub plugin.
• Successful federation to WordPress! Just waiting on them to implement the client-side replies property (to read comments) before promoting it.
• Fixed a bug when updating a user's url property after initial creation.
• Regenerate the threadcap commonjs npm package with a new target of es2019, to remove optional chaining. Makes it easier to integrate in downlevel node environments.

0.1.4

• Option to use a bearer token instead of http-signatures when calling admin rpcs (the admin ip check is still used in both methods)
• New generate-admin-token rpc/cli to generate or regenerate the admin bearer token
• New revoke-admin-token rpc/cli to revoke the admin token and go back to http-signatures only

0.1.3

• Update threadcap to avoid using Response.clone and new Headers(), which are unreliable on Node 16 with node-fetch@2.
• New InMemoryCache listener for when the cache is used.