mirrors/fediparty
1
0
Fork 0
mirror of https://codeberg.org/fediverse/fediparty.git synced 2024-11-21 16:11:28 +00:00
Code Issues Packages Projects Releases Wiki Activity
Page: uses of various federating (and some non federating) protocols
Pages
Collectively owned instances Early adopters (personal accounts) Federated Social Web Timeline Fediverse app criteria Fediverse development FediverseParty agreement Hosting services offering managed fediverse servers Organizations supporting federated social software The fediverse on the web Wordpress integration with Fediverse blockchain social apps considering federation watchlist data porting and cross posting watchlist donations home instance monitoring sites non fediverse federated social apps uses of various federating (and some non federating) protocols watchlist for Diaspora protocol apps watchlist for Zot apps
0 uses of various federating (and some non federating) protocols
strypey edited this page 2020-03-14 09:31:51 +00:00

This protocol summary was originally put together by Strypey on the Ind.ie GitLab server.

Tent is dead (last commit on Tent code was in 2016), and OStatus has been superseded by ActivityPub. Depending on what kind of interaction you want to federate, the actively used protocols are:

  • social network (private, asynchronous messaging): Diaspora protocol (as used internally by Diaspora, and implemented for inter-operation with them by SocialHome, Friendica, and Hubzilla), Zot (used internally by Hubzilla and Zap), email protocols! ActivityPub can support private messages in theory, but so far Mastodon and Pleroma are the only AP-supporting apps that allow private "Direct Messages", and it's unclear if this is compatible with the AP spec.

  • social media (public, asynchronous messaging): ActivityPub (used internally by Mastodon, Pleroma, and implemented for inter-operation by Hubzilla and Friendica, implementations underway for GNU Social and pump.io), Diaspora protocol, Zot, Micropub (micro.blog and IndieWeb sites), Litepub (a subset of AP).

  • realtime chat (1=1 instant messaging): XMPP used mostly in desktop clients like Pidgin and Jitsi, but there are a few mobile clients (Conversations, Yaxim, Tigase, Xabber, Kontalk) and web clients (Let's Chat, Converse, Xabber), Matrix (Riot.im as used on Matrix.org).

  • realtime chat (group chat): IRC (as used on Freenode), MUC (group chat room extension for XMPP), Matrix (Riot.im as used on Matrix.org).

Some newer client devs are trying to make more Slack-a-like IRC clients, but I suspect Matrix might be better for this, as it handles server-to-server federation in a more standardized way. There are even people trying to build social network web clients on XMPP (Mov.im, Libervia). It's been suggested that this may create challenges, due to the fact XMPP was not designed to be web native, although the Matrix team have backed off from the claims on this they used to make in the Matrix FAQ (try using web.archive.org to compare this with what it said about XMPP a year ago).

See also this work-in-progress bubble map of Internet Standards: https://metamaps.cc/maps/3161