@phnt @PurpCat @p @romin as for atproto itself. the few times i looked over the spec there is nothing special about it. claude seems to think it CAN federate now, but there's still basically zero independent implementations. same problem as matrix where its federated on paper but every install is basically new vector's.
nostr actually went and did the thing, has servers, has clients, negentropy sync works and is pretty efficient. some nostr's use the separate in/outbox for logistical reasons but it didn't even require a protocol rewrite to do it, it's just a convention about how to send messages to people.
xmpp already did the thing but people really are severely allergic to XML these days.
there's really nothing interesting at all about atproto.