HTTP message signature standards to federate with Threads
This information is for admins of other servers on the fediverse.
Our Beta experience for sharing to the fediverse is currently only available to Threads profiles in certain areas.
When someone turns on sharing to the fediverse, users on other servers can search for and follow their Threads profile, view their Threads posts, and interact with and share their Threads content with anyone on or off another fediverse server. Learn more about Threads and the fediverse.
When someone turns on sharing to the fediverse, users on other servers can search for and follow their Threads profile, view their Threads posts, and interact with and share their Threads content with anyone on or off another fediverse server. Learn more about Threads and the fediverse.
There are certain HTTP message signature standards that Threads implements and are required by other servers, otherwise known as instances, on the fediverse in order to communicate over the ActivityPub protocol and federate with Threads.
HTTP message signature standards
- Threads implements:
- The IETF draft standard, established as the de facto fediverse HTTP message signature standard and supported by Mastodon, Pixelfed, Wordpress, and other services that implement the ActivityPub protocol.
- HTTP signatures according to the documentation available from Mastodon, here, and behaves in the same manner as a Mastodon instance that has the AUTHORIZED_FETCH feature enabled (also referred to as “secure mode”), as described here.
- Threads signs outgoing POST and GET requests, and requires incoming requests to be signed, with the exception of the public Webfinger API.
| English (US) | + |