[fizwidget]

This blog does a great job of explaining the architecture. In practice though I’d thought the “problem” was that Bluesky (the corporation) runs the main app and hosts almost all of the user data.

So at the protocol level it’s decentralised, but in practice the system is still very centralised (in terms of who controls it).

Not saying this is necessarily Bluesky’s fault, but it’s how things have played out so far right?

[eek2121]

The "problem" is that people are looking for problems. This "problem" isn't specific to Bluesky, ATProto, or anything else. Look at any organization: profit, non-profit, group of volunteers, etc. and you'll always find someone that folks have a problem with.

I'm not an investor and have no conflict of interest with Bluesky beyond being one of the earliest of users. I also understand the protocol, the company, the website within my own limitations.

The site (and app) works just fine. Folks are really focused on finding problems rather than coming up with bigger and better solutions.

Note: the majority of folks don't want an ad-hoc p2p solution like lemmy or mastodon. they want their content in one place, and they want to be able to hold that entity accountable. Because of this, p2p social networking will never take off. I've seen more drama surrounding both Lemmy and Mastodon than I have ever seen with twitter, reddit, facebook, etc. combined.

That's my 2 cents. Also, apparently my spouse feels the same way. So do my friends.

[LudwigNagasena]

Does really do a great job? It just says there are no “instances”, it doesn’t explain how the architecture circumvents all the troubles that it leads to such as auth, sync, discovery, etc.

[danpalmer]

There are other apps, other user data hosting (including personal hosting), and other backend services.

It is decentralised in both theory and practice.

The only thing you could potentially say is that because Blue sky run the biggest parts, it's not decentralised at the community or mind share level, but that's changing.