Almost anything where memorization is the primary skill is going to be dominated by people with specific interest, rather than general high intelligence (certainly doesn't exclude it, but it's just statistics). Gotta look for something frequently requiring novel problem solving and adaption to filter for high probability of high general intelligence.
Then there's also a lot of games requiring very narrow intellectual ability. Being able to parse a specific ruleset, or doing a specific kind of math fast, without needing to be able to handle anything novel. You'll certainly find some "interesting individuals" around those kinds of games.
But that IS the point. The possibility of running independently PLUS the ability of bluesky users to migrate their account wholesale away from bluesky servers to 3rd party servers means you're not dependent on them.
They're literally designing for the principle of "the company is a future adversary" (see: Twitter, et al).
It's always been possible with the use of content addressing, it's just that they've been spending most time building out core services and are now focusing on making it cheaper to run.
First of all, he's saying "you SHOULD make your PDS invisible to the bluesky servers because otherwise what's the point", but that's exactly equivalent to saying "our community want it's own Mastodon server - that means we MUST defederate Mastodon.social or what's the point?"
That's nonsense. Don't enforce silos on people.
Also, which relays to support are not chosen by users, it's chosen by the services the users choose. The PDS choose which relays to sync to, the appview does too, just like feed generators and moderation labelers does. They can trivially sync to multiple.
What people will choose is what app to use. This app will choose default appviews, and that appview chooses a relay, etc. Then they register an account, and the app suggests a default PDS server, or they host their own.
Also moderation labelers can be shared. Communities can run their own, and different communities who trust each other can import labels generated by the others.
Hosting a PDS is very cheap, it's just storage and bandwidth for the posts multiplied by the number of relays you directly sync to. With a few users on each that's nothing. It's in the range of free tier VPS hosting, RPi grade.
Deduplicating is probably the most trivial part. There's already code for handling duplicate events in streams. But more practically speaking, there's algorithms like set reconciliation which can make it significantly more bandwidth efficient to subscribe to multiple relays even when they have overlapping content.
Tldr no there won't be bubbles, unless that's what the users want. They surely CAN choose services which filter out the bluesky servers and which don't make them visible to bluesky, but why?
As for the DID part, the alternative is DID:Web, which requires permanent control over your domain name. With DID:PLC you can control your data by registering your own keys, although there's possibility for censorship. Their goal is to separate out running the DID:PLC service to an independent foundation.
As for the followup comments, just a few months ago bluesky made it significantly cheaper to authenticate jetstream events via Merkle tree diffs (jetstream is the lower bandwidth version of the relay firehose service). This means you can verify correctness quickly just by having a copy of the Merkle root hash & pubkey for the accounts you're interested in, you don't need to store the whole user repositories (excellent for feed generators and moderation labelers and anybody else doing partial sync)
Calling it not federated is silly. It's not like-for-like federated like Mastodon where you have a single server doing all roles, federating to other servers of the same role.
Instead it's cross-layer federation. You can use any app, talk to any appview, use feeds hosted by anybody, use moderation services hosted by anybody, host your account on any PDS service including self hosting, and any appview can talk to any relay. It's fully mix-and-match.
Two people on entirely disparate sets of servers & services using atproto can talk to each other as long as their appviews/relays mutually retrieve content from the other.
That's just if you want a complete copy. You can choose to store only parts of it, and retrieve what's missing from other relay servers when you need it.
They're planning on migrating to the new MLS group messaging encryption standard, which is built to support federated messaging encryption (more efficient than the current Matrix protocol)
(also, Matrix are also planning on adopting it, and the RCS spec is getting it too)
It's long to take a while though. The standard is very recent and nobody has a complete implementation yet.
The whole architecture is built around content addressing and allowing every account hosting server (PDS) talk to multiple relays and to allowing mirroring.
The whole point is to NOT create bubbles.
People already run their own PDS servers and participate with the official bluesky network, and can talk to users there, because their self hosted PDS syncs to the bluesky relay.
If you run your own relay and appview it STILL works, and you can talk without bubbles, if you still link your PDS to the bluesky relay to make yourself visible to their users, and if you set your appview / relay to retrieve content from the bluesky relay then you see content from bluesky users too.
Self hosted relays do exist, they're just not open to the public (mostly used for archival / development currently)
The fix they're trying to implement is to make it cheaper to run relays and appviews, allowing you to run them with only partial network data, prioritizing your own social network first
By the way, those relay storage costs include indexes and not just raw data
Jack Dorsey only provided funding to bluesky while the old plan to make Twitter run on an open protocol was still in place (ironically he wanted to avoid responsibility for moderation by doing that).
He then left Bluesky completely, and never had any major influence after the initial funding.
The content is still accessible, just not via the official Bluesky servers from that region, with content addressing and signatures you can even be certain that mirror sites haven't modified any content.
Almost anything where memorization is the primary skill is going to be dominated by people with specific interest, rather than general high intelligence (certainly doesn't exclude it, but it's just statistics). Gotta look for something frequently requiring novel problem solving and adaption to filter for high probability of high general intelligence.
Then there's also a lot of games requiring very narrow intellectual ability. Being able to parse a specific ruleset, or doing a specific kind of math fast, without needing to be able to handle anything novel. You'll certainly find some "interesting individuals" around those kinds of games.