Post

I wonder if atmospheric websites (websites were most or all of their content is natively stored on the AT protocol) would alleviate this because there are so many places to get the content that aren’t just the website

it's better than that, by design atproto alleviates the need to crawl entirely by providing incremental updates as a primitive (relays) this is actually what got me on here, I think it may be the only way to save the web

going by vibes mostly bc i am not really technically competent at ATProto, i have nevertheless fully committed to the idea that ATProto is to the 2020s what HTTP was to the 1990s

It's more like a modern RSS IMHO? It's RSS but instead of syndicating an XML document you syndicate a collection of JSON documents. Relays full the role of PuSH/WebSub. Bluesky is Google reader.

(I think many people struggle to understand atproto because start from the misconception that atproto is a social networking protocol. But atproto does not understand follows or likes or posts. It's a publishing and syndication protocol designed to make it easy to build social things on top of it.)

yeah, I see the parallels to RSS on technical terms but I would say that atproto's potential impact is closer in scope to the web itself RSS was poisoned by a very unix-like "worse is better" mentality, but thankfully atproto is a hard turn in the opposite direction

I don't think the fight here is over rdf, but, I do think it's pretty fucking ridiculous and you should be a little less gratuitously brutal, given how atproto lexicons are really not that far askance from rdf / semantic web. The bandwagon hate train is long long long on this one.

There's a ton of great very near stuff. Schema.org, microdata, email actions... A ton of stuff is semantic web. It's also incredibly popular to dump on. So much unsubstantiative "give up" "it'll never work".

I don't have a problem with RDF as a technology or a concept. I think it's cool and interesting in a lot of ways.

HOWEVER. The W3C's FIXATION on RDF and the semantic web was a horrible mistake that helped lead to the W3C's loss of relevance in the mid-2000s with disastrous consequences for the open web as a whole and I'm not going to pretend it wasn't.

no not at all, I just mean that there is an enormous difference in complexity between rss and atproto and all of it is essential, which is why atproto can displace closed socials where rss succumbed to them

imho the big innovations are using a merkle-tree based CRDT for efficient synchronization/verification of the data and using DIDs as a stable identifier to enable migration.

rss could never grow into such a thing because its simplicity is attractive to the sort of people who say things like "we don't need chat apps we have IRC" and then lose repeatedly just search any atproto hn thread for "too complicated" and you'll find them

As with all old technologies, that is true now (See people talking about how Wayland is too complex and modern and we should RETVRN to X—which is extra funny because Wayland is dead simple and X is ridiculously complicated)...