Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Is ATProto federated, P2P, or a protocol flexible enough to build all kinds of things?

Is it opinionated about which type of system to build?

Skimming this page, it looks like ATProto is a schema for the ontology, and despite saying "P2P", it looks built around federation and concerned about scaling infrastructure (rather than scaling message broadcast).

I'm interested in a p2p social network with federated supernodes (p2p first class, federation second class, relays for devices that don't want to join the swarm) for people and agents. Could you easily build that with ATProto, or is it the wrong domain?

I'm interested in true, first-class P2P. Not a bolt-on afterthought. That's the problem with all of these federated services like Bluesky and Mastodon.

A true social protocol should work like email. Any machine on the network should be able to talk it to any other machine. Of course centralization nodes will appear, but they should be optional. Used as aids for user friendliness, anonymity, and firewalling yourself off.



Then maybe what you want is email?

Sprinkled with a little bit of https://delta.chat ?

And potentially a dash of iroh https://news.ycombinator.com/item?id=48542480 https://www.iroh.computer/solutions/delta-chat ?


Delta.chat no longer uses email though, right?



Some atproto designers come (somewhat disillusioned) from the p2p world, you can read what they have to say about that here: https://atproto.com/articles/atproto-ethos#peer-to-peer and https://atproto.com/articles/atproto-ethos#synthesis


> A true social protocol should work like email. Any machine on the network should be able to talk it to any other machine

You may find littlefedi interesting

https://littleone.littlefedi.social/@stefano/blog/2026/08/07...


Mastodon works like email. Users have their data hosted on instances and most big instances can communicate with most other big instances, and all instances blacklist a bunch of other instances for spam or political reasons. Just like e-mail.


ATProto is definitely not P2P and probably not federated. Every user has their own personal storage and gives apps like Bluesky permission to write to them.

They solve different problems and, in theory, you can use ATProto and ActivityPub (Mastodon/Threads/Peertube/etc) together


Any PDS can talk to another PDS, yes.


They do not directly talk/query each other. But Relays and AppViews allow PDS's to be aggregated to create apps like BlueSky.

I don't think anyone would describe ATProto as p2p


Yes, and is that useful within the structure of the Bluesky ecosystem?

What if PDSes replicated the content of PDSes? Then it'd be available.




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: