nostr:nprofile1qqsfzzhequxl66lwucls6j42cd2ttkskf44my0yusakd75jvwgzwvmgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9thwden5te0dehhxarj9ehhsarj9ejx2a30qy88wumn8ghj7mn0wvhxcmmv9u80rd8x What nostr:nprofile1qqsp77g933m6yf89hc3xerczfjkd44xhgxz46a0dnug5wwagawrwrjcppemhxue69uhkummn9ekx7mp0qys8wumn8ghj7mn0wd68ytn9d9h82mny0fmkzmn6d9njuumsv93k2tcpz4mhxue69uhkummnw3ezummcw3ezuer9wchsdcndl4 said. 

Imagine X published all the source code for running x.com. You could set up your own version at y.com, but nobody who created an account there would be able to follow accounts on x.com, or vice-versa. So there's no point.

That's essentially the situation with ATProto. In theory, you can set up a complete clone of the BlueSky service, but it's totally up to them whether accounts on your service can be seen on BlueSky.

The chokepoint is not the software, it's the ID layer. The fediverse/ ActivityPub tried to solve that by taking a leaf out of the IndieWeb's book, and outsourcing the ID layer to DNS. The Zot/ Nomad branch of the fediverse has always had NomadicIdentity, which makes accounts ("channels") independent of the domain names of servers, and there are a number of FEPs describing how to do that in AP software;

https://wedistribute.org/2024/03/activitypub-nomadic-identity/

Nostr solves the ID chokepoint problem in a similar way, by having a decentralised ID layer. So that's a step forwards from the existing AP+DNS dominated fediverse. BlueSky is a step backwards, and the main reason people use it is the aggressive Safer Spaces Policing that their ID chokepoint allows;

https://wedistribute.org/podcast/blacksky-rudy-fraser/

For some people that's a feature, and a permissionless network is a bug that feature solves.