mmm sorry but I don’t quite get this. Activities are defined in the ActivityPub spec, and Pleroma can simply decide to handle or ignore an incoming activity.
EDIT2: All servers need Webfinger, inboxes, and outboxes to function, but the activities themselves come in wildly different formats, with various extensions, including domain-specific activities. They’re not always documented. Also, most Fediverse software doesn’t even implement basic parts of the ActivityPub spec, such as the client-server API, which is not implemented by Pleroma nor Mastodon (they both use Mastodon’s own client-server API which is based on GNU Social’s client-server API which is based on Twitter’s old API). There’s a ton of history involved and a lot of different ways to do things. I recommend this article by Pleroma’s creator for more explanation: https://blog.soykaf.com/post/pleroma-encyclical-activity-pub/
post
mmm sorry but I don’t quite get this. Activities are defined in the ActivityPub spec, and Pleroma can simply decide to handle or ignore an incoming activity.
Believing this is your mistake :D
EDIT: The Transmogrifier is 1200 lines of code.
EDIT2: All servers need Webfinger, inboxes, and outboxes to function, but the activities themselves come in wildly different formats, with various extensions, including domain-specific activities. They’re not always documented. Also, most Fediverse software doesn’t even implement basic parts of the ActivityPub spec, such as the client-server API, which is not implemented by Pleroma nor Mastodon (they both use Mastodon’s own client-server API which is based on GNU Social’s client-server API which is based on Twitter’s old API). There’s a ton of history involved and a lot of different ways to do things. I recommend this article by Pleroma’s creator for more explanation: https://blog.soykaf.com/post/pleroma-encyclical-activity-pub/