a colleague of mine recently insisted that bittorrent be included in web3 techs since it uses hashing. if we toss torrents under the title of web3 then it's been a huge success.

atproto, however, could learn a lot from torrents and all of the other protos since then. for example, their recent push to centralize bookmarks.

▲

OneDeuxTriSeiGo 3 days ago | parent | next [-]

> 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.

▲

Terr_ 3 days ago | parent | prev | next [-]

> a colleague of mine recently insisted that bittorrent be included in web3 techs since it uses hashing

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.

▲

verdverm 3 days ago | parent | prev [-]

Yea, the bookmarks thing is interesting, and wearing my conspiracy theory hat (it's not the red one), I wonder if it's not an experiment to see what the people will tolerate or how they will respond. It could equally be attributed to an early win for the new product manager, finally delivering a long requested feature in a POC form factor, while private data gets figured out.

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

▲

pfraze 2 days ago | parent | next [-]

I'm pretty sure the private data model is going to be clearly defined by EOY, between the community group work and bluesky internal work. We also made sure that bookmarks will migrate cleanly to protocol private data when it lands, so no need for the tinfoil hat. Your other explanation is pretty close to the mark.

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.

	▲	evbogue 2 days ago \| parent [-]
		yes, and we are using computers in our pockets now that are way more powerful than the ones we had when we were working on ssb. local indexes are possible, you and dom showed that back then. ssb had private bookmarks, let's dig into how those were enabled

▲

evbogue 3 days ago | parent | prev | next [-]

agreed! we should continue this discussion over on atproto

▲

verdverm 3 days ago | parent | prev [-]

one thing I would like in atproto is some form of smart contracts

(transactional semantics over accounts and xrpc calls)