Skip to main content


I encourage everybody to adopt the following pattern, when talking about ActivtyPub:

If it's important what you mean by ActivityPub, use more clarifications, e.g. Mastodon-ActivityPub.

in reply to Helge

An example

The syndication of the Delete activity of an actor in Mastodon ActivityPub to everybody, is ridiculous.


joke suggestion: Someone should write a FEP to fix that.

in reply to Helge

> Use ActivityPub for referring to what is actually implemented in the Fediverse

Or maybe "Activity404" for that, to credit the HTTP response when trying to load the Mastodon AP context document ;).

in reply to Nik | Klampfradler 🎸🚲

In my unending benevolence, I grant you the right: If it is important to emphasize that JSON-LD is not used, you may use Activity404.

I'm mostly trying to funny, but this might be really useful.

in reply to Nik | Klampfradler 🎸🚲

In my unending benevolence, I grant you the right: If it is important to emphasize that JSON-LD is not used, you may use Activity404.

I'm mostly trying to funny, but this might be really useful.

in reply to Helge

for what is actually implemented in the fediverse i would use the term "fediverse", or with clarification "mastodon protocol". i don't think it serves well to muddy the waters between following the spec vs following what others have done (which are generally not the same).
in reply to infinite love β΄³

Bad idea. The Fediverse is already ambiguous enough. Suggesting using it to also mean a protocol just creates a mess.
⇧