> Standard.site provides shared lexicons for long-form publishing on AT Protocol. Making content easier to discover, index, and move across the ATmosphere.
Which part of these required a new protocol and couldn’t be built before @at existed? Seems to me we’re reinventing the wheel for I’m not entirely sure which benefit. But maybe someone who’s more into this part of the web can educate me on this.
The atproto folks went and categorized all of the other attempts to do this at the time. (They even had some I hadn't heard of!)
All of them make various tradeoffs. None of them were the set of tradeoffs the team wanted. So they needed to make some new things. That's really the core of it.
My sibling has one of the largest and most specific things, but this is the underlying reason.
Is this study/exploration available anywhere? I’d love to give it a read if that’s available. If you have a link to share I’d really appreciate it.
> Content portability
> Users move between hosts without losing their content, audience, or metadata.
ATProto has lexicon, which are more about social coordination than schemas for data correctness
https://pfrazee.com/blog/lexicon-guidance
The protocol is much more than data portability, it essentially turns the global social media system into a giant distributed system anyone can participate in at any point. Imagine if FB also let you tap into the event stream or produce your own event stream other FB users could listen to in the official FB app. That would be a pretty awesome requirement for all social media apps, yea?
Don’t we already have that and is called “the web”? It’s already a giant distributed system anyone can participate in at any point.
What are we really gaining here?
Perhaps it is time to read more about the protocol directly instead of asking questions on HN to poke holes in it from a position of ignorance.