[cxr]

> Atproto was designed for social media, in an age of Twitter users getting their news in seconds, to the point of being able to comment on live events play-by-play.

And this is widely recognized by now to have been a very bad thing, even/especially those most susceptible to its draw. It's strange that you're framing it as a strength and not a lament.

> There's no coming back from that world.

You can't say that when everyone just begs the question and shoves application-server-needed-here protocol designs to the fore.

[JoshTriplett]

> And this is widely recognized by now to have been a very bad thing

It has upsides and downsides. The ability to live-post an event, or get up-to-the-minute news, can be a good thing.

[janalsncm]

Because this is about synchronizing code and not realtime social media? Social media is just an example application of the technology.