Comment by manuelmoreale
8 hours ago
I’m looking at the site and right at the beginning it says:
> 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.
> 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.
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.
One answer is right under Introduction:
> Content portability
> Users move between hosts without losing their content, audience, or metadata.