As @Dennis Schubert said on (and about) diaspora* three years ago:

"Nobody implements ActivityPub. People implement Mastodon."

#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ActivityPub #FediverseDevelopment
firefox web compatibility at mozilla. certified member of the blockchain hate club. sometimes doing other stuff as well. for science, you monster. he/him/they/meow. ------- **blog**: [overengineer.dev](https://overengineer.dev/) **photos**: [photos.overengineer.dev](https://photos.overengineer.dev/) **how to contact me**: contact details on various channels are listed [on my website](https://overengineer.dev/me/card.html). ------- All Computers Are Broken.

firefox web compatibility at mozilla. certified member of the blockchain hate club. sometimes doing other stuff as well. for science, you monster. he/him/they/meow. ------- **blog**: [overengineer.dev](https://overengineer.dev/) **photos**: [photos.overengineer.dev](https://photos.overengineer.dev/) **how to contact me**: contact details on various channels are listed [on my website](https://overengineer.dev/me/card.html). ------- All Computers Are Broken.

Geraspora*

@jupiter_rowland

As one ages one occupies a world of analogies that no one else understands, bear with me.

It's like TCP/IP but maybe in not in a terrible way. People implemented "Cisco" if they needed to interoperate fast.

But yes, having #ActivityPub just dissolve into the background of awesome new apps is the game.

@CartyBoston I guess people who only know Mastodon see this differently from people who actively use something in the Fediverse that is not Mastodon.

The difference is:

If you "implement ActivityPub", it will work with, for example, Mastodon and its forks, Pleroma and its forks, Misskey and its forks, GoToSocial, Friendica, Hubzilla and (streams). As long as they have a reasonable ActivityPub implementation itself.

If you "implement Mastodon", it's only guaranteed to work with Mastodon.

It may or may not work with Mastodon forks, Pleroma and its forks, Misskey and its forks, GoToSocial and Friendica. If it doesn't, it never will because the non-Mastodon Fediverse is not officially supported. In fact, the devs may not even know that there's something in the Fediverse that's federated with Mastodon, but that isn't Mastodon.

It will most likely not work with Hubzilla, which is what I use, and (streams). They, too, are federated with Mastodon, by the way.

But this is the way a whole lot of things in or for the Fediverse are developed.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ActivityPub #FediverseDevelopment
Netzgemeinde/Hubzilla

@jupiter_rowland AP c2s is not widely adopted, e.g. Pixelfed implemented the Mastodon API.

AP s2s is widely adopted and doesn't depend on the Mastodon API.

@Jan Well, it is possible to use the Mastodon client API for features that Mastodon itself doesn't have like text formatting. But, for example, many mobile apps don't support text formatting because Mastodon doesn't, although everything that isn't Mastodon does. They're built only against Mastodon.

And there are things, mostly Web services, that either do the same, use the client API, implement only Mastodon features and depend hard on features that only Mastodon has. Or they skip APIs and build directly against Mastodon, again, requiring the presence of features only available on Mastodon in the required way.

Then they have the audacity to have "Fedi" in their names while being completely incompatible with Pleroma, Misskey, Iceshrimp, Friendica, Hubzilla etc., essentially everything that isn't Mastodon or maybe a Mastodon fork.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #MastodonAPI #FediverseDevelopment
Netzgemeinde/Hubzilla

@jupiter_rowland

totally, e.g. I am no fan of HTTP signatures but I implemented it so I could see what was going on. I am just earlier in my activitypub journey (hah! I hate "journey") I think.