atproto, however, could learn a lot from torrents and all of the other protos since then. for example, their recent push to centralize bookmarks.
atproto, however, could learn a lot from torrents and all of the other protos since then. for example, their recent push to centralize bookmarks.
It's worth noting that the current bookmarks implementation is "temporary" and will be moved to the PDS as soon as private data repos are supported on the PDS.
The approach they are taking (and are recommending to other devs in the space) is "develop your private data as if it was stored on the PDS but stored on the appview. then migrate to the PDS once private data launches". If you maintain the same lexicon/schema under the hood, you can just copy the data to migrate it.
Private data is unfortunately really hard to do right so this "start workshopping it and get ready for us to roll support out" approach seems like the best temporary solution.
Related pet-peeve: Folks who say "there's still great promise in private blockchains." This is equivalent to saying that self-balancing Segway-style devices can still become the dominant mode of transportation if we juuuuust make them bigger, enclosed, and add another pair of wheels so that they don't have to self-balance anymore.
I'm highly involved in the private data work and we'll have a better bookmarks in the long run
I like that atprotocol sits in the middle of web 2 & 3, ideas from both without being beholden to either
EDIT: also fwiw, I got my start in 2012 working on ssb and then in 2013 on dat, both of which were conceptualized as bittorrent variants. Atproto has a pretty clear lineage from that p2p work. You just can't do large scale social computing on user devices.
ssb had private bookmarks, let's dig into how those were enabled
(transactional semantics over accounts and xrpc calls)