openEngiadina: From ActivityPub to XMPP

[Sebastian]

Well, just some coming to my mind …
There is much more !

This post is a wiki, add yours:

Implementations of the ActivityPub Client-to-Server protocol (C2S)

• pleroma incl. 12 clients
• mammoth
• socialhome
• μblog.pub
• aardwolf
• pubgate
• and-status (android)

Server

• Go-fed
• Epicyon
• SemApps
• Fedbox

Also leaving this here

The ActivityPub Panel

One thing that I think is key but maybe not obvious from the spec: The AP Client-to-Server API isn’t just aimed at mobile or desktop apps. That’s the obvious and straightforward use case, but not the only one. What the C2S API gives you is delegation. It lets some other agent - which might be a mobile app, or might be a web app - act on your behalf. And, importantly, it gives those agents effectively equal power to the server itself has. In the extreme, you could have a server which has no UI…

Implementing ActivityPub Client-to-Server

ActivityPub Client-to-Server (AP C2S) API compared to other APIs allows to have more flexibility and control of the activities/objects, plus proper multi-instance abilities (origin URIs instead of IDs local to the instance). Pleroma Backend has the ground layer of AP C2S and has been almost not progressing from it for a while. AndStatus is a standalone client which does AP C2S among other APIs. And so far that’s what I’m aware of. I think we should see how to effectively kickstart this API i…

PS: Not sure about https://bonfirenetworks.org but Mayel is also doing Elixir, see GitHub - bonfire-networks/activity_pub: Modular ActivityPub library in Elixir