OK even funnier than #bluesky / #ATProtocol 's plc DID method relying on a single domain is that the hardcoded DID for bsky.app isn't registered, they don't even use it for the default algorithms and just hardcode a workaround.
WHICH MEANS that whoever finds a (truncated) hash collision for the bsky.app DID will cause an absolute fucking mess hahhahaahhaah
More Bluesky users understand that the success of Bluesky is not a sure thing, and now that Meta is joining the Fediverse, this is going to be a real fight between ActivityPub and AT protocol.
If I am ever feeling imposter syndrome and start doubting my ability to write a protocol, I can always take a look at #Nostr , whose protocol is just this, a vague example of some JSON message object, and then a zillion nonbinding "enhancement possibilities" with no pretense at consistency.
idk why people are excited about this (ok, i do, everything in cryptobro universe is like this), it's literally just a traditional client-server architecture with the phrase "censorship resilient" stapled on top of it.
i think it's very funny when ppl are like 'this thing is very decentralized' but the governance of that thing is literally a git repository with completely undefined processes for how and who gets to make a change to the thing.
like i know decentralization is basically meaningless but one would hope that it could still mean "not centralized to a single point" but i guess as I learned yesterday with #ATProtocol 's placeholder DID method that resolves by quering a single domain, i guess not.
lmao taking a look at #ATProtocol / #Bluesky's implementation of #DID, and I think they missed the "decentralized" part in their "placeholder" DID method.
Your domain's DNS entries just contain a (truncated) hash that then has to be resolved at plc.directory
recall that the DID method (plc) is part of the DID, so a different method (eg. web) is a different DID. to switch, you'd need to set an alsoKnownAs entry. plc only supports AT handles for alsoKnownAs.
#Bluesky / #ATProtocol is an extremely funny protocol that is explicitly designed to ensure that there are still powerful entities that own your attention. Sure! you can host your own personal data store, but everyone else will be getting your posts through a Big Graph Service that necessarily crawl all posts on the network, so it's actually mostly irrelevant.
Who owns Bluesky? What’s the role of former Twitter CEO Jack Dorsey? What’s Bluesky’s business model? And what prevents another Elon Musk from buying and destroying it 10 years down the line?
...since starting @ClimateMigration yesterday, the vast majority of Followers are from outside the US. Understand this is not a fun subject, but the disparity in attention to this topic is pretty striking.
From what I've read of it, "controlling your algorithms" is you getting to choose radio buttons from a list of canned topics or you get a couple fields to enter keywords into, give it a name, save it, and it's "yours"
The only difference is that #Jack and #Bluesky and the #ATProtocol seem to be farming out algo content and legal liabilities to unknown/unnamed third parties
While #Musk and #Twitter are still trapped with it in-house
The only thing I love about Bluesky / AT Protocol is the use of subdomains for user names.
The double-@ is confusing as heck to people, but a link that also works as a mention name is obvious / intuitable (eg "Find me at jeremiahlee.bsky.social which makes me mentionable @jeremiahlee.bsky.social").
The real sticking point in implementing portable accounts/ nomadic identity in the ActivityPub branch of the #fediverse - like what Zot and AT Protocol offer - is its implications for how moderation works.
"The hard part however, is the social one: we collectively need to agree that the identity resolution layer is infrastructure and not somewhere moderation actions should take place."
Whether it's #BlueSky or #Meta, I just do not understand how anyone can possibly give them the benefit of the doubt when it comes to their intentions with federated networking. Like, it's not like the internet is new. We have countless examples of what billionaires do with their power. They never try to make things better for us. They always try to accumulate profit for them at the expense of anyone else. How many times do people need to be fucked over before they learn?
Will we get adapters / relays for #ATProtocol and #ActivityPub maybe in the future? Anyone working on it? Sure Bluesky is VC backed etc but once they start down the journey of federation it feels like it could help reduce the “oh you’re oh BlueSky, sorry I can’t see your chat on Masto”
@mattjbones there’s already SkyBridge that is doing the Mastodon API translation to enable cross-posting, I think. I’m unsure about the appetite it at the federation level. Potentially worth checking in on the #fedidevs efforts to see if #ATProtocol is part of their thinking.
I wonder if people threatening to block Facebook's/Meta's new ActivityPub-compatible social media network also automatically block emails coming from gmail.com.
#Bluesky 's latest blogpost [1] reveals that the #ATProtocol is a classic bait and switch game, facilitated by the small-world/big-world distinction. [2]
The bait is telling creators that their content is safe (from petty moderators/server shutdown) and that they are not locked into a platform because the AT protocol is federated, so they can self host with a handle under their control. The switch is that the (federated aspect of the) AT Protocol is irrelevant in the big-world.
Apparently there's some hostility coming from the ActivityPub side of things about BlueSky? If true (I haven't seen it yet), that would be very disheartening to hear. This should be a collaboration and an acceptance to federation, not a competition.
A really good read from the Matrix dev about how AT and Matrix have similarities.
i’ve been thinking about #ActivityPub and am going to use this as the start of an ad hoc thread about identity and account portability.
here’s where i think i’ll land:
1️⃣ the Conventional Wisdom conflates #Mastodon features with AP.
2️⃣ the Conventional Wisdom is that AP guarantees a #RightToExit, which it does not.
3️⃣🔥 and a hot take, as a treat: #ATProtocol is currently doing better work building the system that most AP advocates think is being built here.
What will be the tangible difference between the BGS that #Bluesky is making for AT protocol and a really well-connected relay operated with #ActivityPub?
@atomicpoet Is it me, or does #ATProtocol appear unnecessarily complex‽ At least for the foundational aspect of what #BlueSky is trying to do‽ #ActivityPub might not be advanced, but it’s simple enough for the average non-tech person to understand (even if they do not understand the “how” of the #Fediverse).
I know the #Bluesky /AT devs & Dorsey (mostly Dorsey) keep saying that “Bluesky” is essentially a proof of concept and will (if all works according to plan) cease to exist once #federation blossoms.
But…
I don’t believe that. I feel the OG server & native clients will be cemented and always be somewhat of a default.
I've been doing some research on #bluesky, nothing too deep. It piques my interest that they're trying to stand up an entire new federated protocol rather than just use (or even extend) ActivityPub. Not only does this make them incompatible with the Fediverse, it stands them in opposition to it with their own Fediverse-of-one. Remains to be seen if they'll be the VHS or the Betamax of this war.
Yes, they want more control. I personally think portability is just an excuse. I'm not holding my breath about them allowing people to 100% install BlueSky on their server, it's against their business model.
About the meta discussion, he's right about #Fediverse being "suspicious of Bluesky". They haven't given much reason not to be.