I genuinely don't understand the relationship between atprotocol and bluesky. Bluesky is a company, with a board and CEO, with bans and an ideology. Can atprotocol exist without Bluesky? If apps are built on atprotocol do they have to fall in line with Bluesky company policy?
Genuinely have no idea.
#asknistr
#asknostr * 🙄
Wondering similar. Hadn't heard of AT Protocol, but the architecture doesn't look too far off of Nostr.
Maybe Bluesky is just the centralized name running the protocol for rapid growth, and decentralization will take over later. If so, this isn't a bad network growth strategy.
But ya, "Is AT Protocol truly decentralized and independent from Bluesky?". Million dollar question.
Atprotocol and Nostr both emerged from 'secure scuttlebutt' or something. I have no idea. nostr:nprofile1qqs8d3c64cayj8canmky0jap0c3fekjpzwsthdhx4cthd4my8c5u47spzfmhxue69uhhqatjwpkx2urpvuhx2ucpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwdehhxtnnda3kjctvll3q2p 's videos at the nostr conference has more info on this:)
Interesting. Didn't know this!
HAH.
I emailed them.
Oooh curious to see if/what you get as a reply 👀
We'll see 🤣 I was nice, but also told them all of what they're asking already exists and Bluesky isn't the way forward if they're truly trying to facilitate a future where no one controls social.
I suspect they don't actually want Nostr, they actually want a central moderation company lol. They want the old regime of social media and it's ideologies back lol. Just a suspicion, hopefully I'm wrong 🤞
Neither apps built on ATproto nor self-hosting users have to fall in line with Bluesky company policy. A lot of confusion about that.
Curious
Basically if you host your instance you have all your history content-addressed, and none of your rotation keys are controlled by Bluesky. So you can in theory detach and then plug into any other relay or client(AppView in their lingo), including those run by Bluesky and those not. (Appviews can also pull directly from your instance without a relay.)
On the dev side, you can build any AppView, or full relay, or partial relay, and set your own policies, and invite self-hosting users with their own keys to join it, and Bluesky can do nothing about that.
However the one thing Bluesky still have control over in that relationship the DID:PLC directory (DNS pointing equivalent). So that's of note. Though supposedly that's going to be spun out into something ICANN like, who knows. Also on the self-deployed relay side things can get very expensive very fast.
I think ATProto is pretty well thought out for certain town-square-like use cases, where users need both a way to exit and a global view (i.e. some users simply must know exactly how many followers they have down to the individual follower, contradicting reports won't cut it.). But Nostr is much, much better for other use cases.
I understood some of this, thank you for your detailed response tho. I just wish I was clever enough to understand half of it:)
