ATPROTO isn’t just for Bluesky weiners

Dan Abramov: with time it's gotten more social right like social networks and so on. So like we've gotten like shared spaces but then these shared spaces they feel like internet inside of internet like you know different world gardens uh like Facebook or Twitter where we're going to put our stuff there you know like I I put like my answers on Stack Overflow or my issues on GitHub or like my like posts on Reddit or somewhere else. But then with time these platforms they kind of you know they fatten up with like everyone's content and then they start doing you know they're like shutting down alternative clients, start showing like ads everywhere trying to milk you know everything that and like we can't really like walk away from them because then we're going to erase everything that we created there. So, in a sense, it's kind of like we put our stuff into somebody else's box and then this box is just, you know, it's not on the open web anymore. It's kind of there's like a ghost of it on the open web, you know, like the projections like the HTML that you can hit through the servers, but like in a sense, it's like it's it's locked somewhere somewhere else. And the big thing about that PRA is it's kind of like a data layer for the web is how I like to think about it. ... what if that JSON just you know hung on the web like that JSON was part of the web uh kind of like in the personal sites era but um you know you still can use apps of course so like apps are kind of the consumption and production model but it lives sort of like in everybody's like it's it's like if everybody had a Dropbox folder that all apps apps can kind of interact with and then you can always leave an app but your stuff is still going to be in that folder and so other apps can kind of you know present it differently or even like write to it differently and different apps can see each other's content and and kind of interoperate

Dan Abramov: the first thing that it introduces is it really upstreams that concept into web itself. So the idea is that identity should actually be a legible concept in the web. So you should have a web account and you know you don't have to be logged in all the time of course or you can have multiple uh but ideally we upstream this so that you don't depend on Google and so uh you know it could be hosted by Google but you should be able to switch it to another provider or to host it yourself on your own server but basically like the the thing that you log into apps with that should be something that you know that is like under your control and that is a web standard. ... there's like a identifier that's associated with you and then there's like a JSON document that says three things. One is like what your current username is which is you know a domain but it can change over time kind of like your passport. So like it says who you are like what's your name? You know what is what is your handle? The second thing it says is where is your data stored? So what is your current hosting? And that is the novel concept, right? Like in today's web, we don't really have a concept of per user hosting, right? ... And the third thing is just your public key so that the things that you do can be verified.

Dan Abramov: I like to think of at Praa is like web three. The good parts uh but the good parts uh you know not not a lot. ... it's crypto in the sense of cryptography. So the lessons are ... you want to have intermediate nodes like you want to have this kind of retransmitters like relays ... how do you trust that it's not, you know, it's not lying about the content that's flowing through it? And so the solution is kind of the same as in Git, right? In g you can sign commits. ... the content like the event stream is signed but in that sense it's closer in lineage to uh maybe git or you know like uh I don't know bit torrent or like some of those other things that are not about blockchain and the only thing that is because like in I think like people try to build social stuff on blockchain but is super inefficient because there's a bottleneck of like every right is like an append to a single kind of shared queue. ... the big insight for for it prior developers was that actually you don't need global ordering on the event log and if you drop the glo global ordering constraint like everything is in a single queue it actually becomes just the web