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)