Thank you! I LOVE visuals for things like this! It helps me to understand and remember. Imprint and absorb.
It makes my brain happy 😊
# Visual depiction of the architecture of 3 different decentralized social networking protocols
## Fediverse
First of all we have **Mastodon** (I often call it by this name because Mastodon is the _de facto_ controller of the protocol), but a better name would be _the Fediverse_, which is ugly, but still better than **ActivityPub**, since "Activity" depicts a much broader protocol, conceived by the minds of unreasonable academics, unimplementable in nature, which was only partly adopted by Mastodon.
Anyway, it is very straightforward: clients talk to a single server, that server talks to other servers.

## Nostr
Well, **Nostr** has been [described](nostr:naddr1qqyxgetyxu6kxcnrqyghwumn8ghj7enfv96x5ctx9e3k7mgzyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6qcyqqq823cp96gup) [elsewhere](nostr:naddr1qqyxgvrzxy6kzcehqyghwumn8ghj7enfv96x5ctx9e3k7mgzyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6qcyqqq823cpr9f3d) [many](https://www.youtube.com/watch?v=8GhEezzto4Y) [other](https://newsletter.squishy.computer/p/natures-many-attempts-to-evolve-a) [times](https://www.youtube.com/watch?v=Tbt3jL1Ms0w), but its core new idea is that clients can talk to multiple servers, which gives us a very chaotic ecosystem of signed messages.

## ATProto
Finally we have **Bluesky**, or, if we go by the name of the overall protocol, _ATProto_. Its core new idea is that the basic functions of a social networking server can be broken up in mainly 3 different kinds of servers, which then talk to each other in a pipeline.

Thank you! I LOVE visuals for things like this! It helps me to understand and remember. Imprint and absorb.
It makes my brain happy 😊
Diagrams, eh? 🤔
Yep. Still waiting…
Bonus points for colour!
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 knows the way 😎