Signal isn't federated ^[1][2][3.1]^; it's decentralized ^[1][2][3.2]^. Though, for all practical purposes, I would generally argue that it's centralized.

References

Signal-Server. signalapp. Github. Published: 2025-01-31T15:34:14.000Z. Accessed: 2025-02-01T09:24Z. https://github.com/signalapp/Signal-Server.
- This is the source code for the server that Signal uses.
"Signal (software)". Wikipedia. Published: 2025-01-06T09:34Z. Accessed: 2025-02-1T09:30Z. https://en.wikipedia.org/wiki/Signal_(software).
- ¶"Architecture". ¶"Servers".
  
  Signal relies on centralized servers that are maintained by Signal Messenger. In addition to routing Signal's messages, the servers also facilitate the discovery of contacts who are also registered Signal users and the automatic exchange of users' public keys. […]
"Reflections: The ecosystem is moving". moxie0. Signal Blog. Published: 2016-05-10. Accessed: 2025-02-01T09:40Z. https://signal.org/blog/the-ecosystem-is-moving/.
1. ¶5. to ¶"Stuck in time". ¶3-6
  
  One of the controversial things we did with Signal early on was to build it as an unfederated service. Nothing about any of the protocols we’ve developed requires centralization; it’s entirely possible to build a federated Signal Protocol-based messenger, but I no longer believe that it is possible to build a competitive federated messenger at all. […] [interoperable protocols] [have] taken us pretty far, but it’s undeniable that once you federate your protocol, it becomes very difficult to make changes. And right now, at the application level, things that stand still don’t fare very well in a world where the ecosystem is moving. […] Early on, I thought we’d federate Signal once its velocity had subsided. Now I realize that things will probably never slow down, and if anything the velocity of the entire landscape seems to be steadily increasing.
2. ¶"Stuck in time". "Federation and control". ¶6.
  
  An open source infrastructure for a centralized network now provides almost the same level of control as federated protocols, without giving up the ability to adapt. If a centralized provider with an open source infrastructure ever makes horrible changes, those that disagree have the software they need to run their own alternative instead. It may not be as beautiful as federation, but at this point it seems that it will have to do.

[–] Lazycog@sopuli.xyz 83 points 7 months ago (15 children)

Yeah. I love Signal but it doesn't belong in that list. Dansup (creator of loops and pixelfed) is apparently working on "Sup" that will be a decentralized alternative to whatsapp.

[–] ProdigalFrog@slrpnk.net 15 points 7 months ago (6 children)

XMPP is an established federated messaging app with encryption.

[–] Lazycog@sopuli.xyz 5 points 7 months ago (2 children)

There isn't much information about "Sup", but if I had to guess it could be that dansup is making sup app with XMPP(rotocol) as the messaging protocol.

[–] poVoq@slrpnk.net 6 points 7 months ago* (last edited 7 months ago) (2 children)

Originally it was supposed to be ActivityPub based, but recently they posted something about it being for XMPP, Matrix and IRC as well 🤷‍♂️ Maybe they decided to fork Pidgin 😂

IMHO Sup. isn't going to happen. They will have their hands more than full with Pixelfed's new popularity and maybe Loops.

[–] Lazycog@sopuli.xyz 2 points 7 months ago

Oh! didn't know that, I thought activitypub can't be used for secure messaging. Lol really hope its XMPP!

Yeah I didn't take it that seriously when it was announced right now. Just hope pixelfed stays afloat amidst the user flood and hope he can publish loops as open source soon!

[–] chrislowles@lemm.ee 1 points 7 months ago

Multi-protocol would be awesome, hopefully down the line it'll come back around to adding some basic AP integration.

[–] ProdigalFrog@slrpnk.net 4 points 7 months ago (1 children)

That would be rad if true ^^

[–] Lazycog@sopuli.xyz 3 points 7 months ago

Let's hope so! :)

load more comments (3 replies)

load more comments (11 replies)

load more comments (29 replies)