The whole idea of BlueSky supporting nomadic identities but the rest of the ActivityPub (plus other stuff) Fediverse being unable to do so is such an oversold idea.
A new service using ActivityPub behind the scenes (and not the AT Protocol) can absolutely support nomadic identities, even if the service doesn't treat a whole website as the actor.
It will still use did:plc, same as AT Protocol (BlueSky), but once done so, an application that understands how to work with did:plc can dereference an actor based on the DID.
That said, an existing service will simply not be compatible with this idea, without changing how it operates.
But if #BridgyFed becomes more user-friendly, that will be a big step towards interoperability. And we can finally put this silly competition between #ActivityPub and #ATProtocol to rest.
“Blacksky is providing a platform to amplify, protect, and moderate Black content so users can safely build community online.
“The mission and purpose of the project is to de-center whiteness as the default and to provide a space for Black folk to discuss the Black everyday in a way that feels affirming.”
Successfully moved from mastodon.online to mastodon.social.
All that waffle in @theverge interview with Jay Graber about things such as Bluesky being better for portability, and AT Protocol being more centred around the user, and that somehow servers are bad, and... ah, I think @reckless1280 just didn't challenge her enough. I'd think what I'd much prefer is a proper panel debate, not a one-sideded AT evangelism/sales-pitch like that.
Great interview with Jay Graber (CEO, #Bluesky) on Decoder with Nilay Patel (@reckless1280), where they dig into some of the major difference between Bluesky (#ATProtocol) and #Mastodon (#ActivityPub).
Manton from Micro.blog intends to enable the service as an ATProtocol PDS:
The long-term plan for Micro.blog is to fully support AT’s PDS — Personal Data Servers. Any blog hosted on Micro.blog would plug into Bluesky seamlessly, with data portable to other AT Protocol hosting providers.
A major difference between the #ActivityPub federation and the #BlueSky#Atproto (#Atprotocol) federation is that under AcitivityPub, used by Mastodon, all servers that need to send or receive data from other servers need to make direct connections to each other. This means many queued jobs and many connections, maybe thousands. This leads to the classic sidekiq queue problems when Mastodon instances have numerous users with numerous follows, and relays.
In contrast, in atproto, the user's PDS, Personal Data Server, doing equivalent work of a Mastodon server, for example, only makes a few connections to the relay server's fire hose to deliver and pick up messages. It never connects to any other PDS directly. Theoretically, a tiny #PDS on atproto can handle a considerable number of users. This seems to be an advantage.
Mastodon admins spend a lot of time and money fighting performance issues, database connection counts, and sidekiq queues because the server has to talk directly to other servers. But the PDS only needs to talk to maybe one, or possibly a few relays to get and send messages.
Here's a diagram of the atproto architecture. It appears quite a simple architecture.
ICYMI — you can now listen to my interview with Bluesky CEO Jay Graber on Spotify or wherever else fine podcasts are traded.
We go pretty deep contrasting #ATProtocol and #ActivityPub, discuss challenges with "creator mobility" and touch on opportunities to serve the decentralized social web.
BlueSkys official #ATProtocol account just highlighted a community developer project to bridge it with #ActivityPub
#BlueSky early on decided not to go with the open #W3C standard in favor of implementating features like account migration. Planning to start federating next year, they've made some decisions I'm skeptical about.
I'm studying the docs, and I have a question for those who might know better:
The big thing AT is promising is better portability across instances (when such instances appear). My understanding of the docs (https://atproto.com/guides/overview#account-portability) is that this is made possible, in part, by having a copy of my data on my client.
So, I do have a bsky.app account. Where is my local data? I don't see any anywhere. Is that not implemented yet?
#Streams galaxy
-- note 1: communication with the Fediverse is standard practice in this universe.
#Hubzilla galaxy
-- note 1: developed a way to communicate across the Mycelial Web (a.k.a. the multiverse). Can also communicate with BlueSky and diaspora.
#Friendica galaxy
-- note 1: developed a way to communicate across the Mycelial Web (a.k.a. the multiverse). Can also communicate with BlueSky and diaspora.
#X#Twitter Mycelium (closed borders; isolated; have not discovered there are other mycelium/universes besides their own)
#Tumblr Mycelium (closed borders; isolated; rumours has it their government decided against connecting with the other mycelium/universes, but they are aware)
#Flickr Mycelium (closed borders; isolated; aware of other mycelium/universes)
The #IndieWeb service #Bridgy is ready to handle bridge AT protocol and ActivityPub protocol posts and replies once federation is enabled in production (already working in sandbox test server).
The format will be:
To follow a #Fediverse account from BlueSky / AT protocol: <username>.<server_domain>.ap.brid.gy
To follow a BlueSky / AT protocol user: <username>@atproto.brid.gy
Example: @atp.youronly.one@atproto.brid.gy
This allows users from each side to see new posts and to reply to these threads.
What is more interesting is that, if you have IndieWeb support on your website or blog, you will see comments from BlueSky / AT protocol appear as a comment, thanks to #Webmention. It is already possible to do this with Fediverse / ActivityPub. ^_~
It describes it as:
“Autistic burnout is a syndrome conceptualized as resulting from chronic life stress and a mismatch of expectations and abilities without adequate supports. It is characterized by pervasive, long-term (typically 3+ months) exhaustion, loss of function, and reduced tolerance to stimulus.” ~Raymaker et al, 2020
Typically the Autistic person in question will still have multiple demands in their life that require cognitive resources, despite having little to no resources left to give. Life goes on, as they say.
oo I didn't know the #bluesky#atprotocol sandbox was public. looks like I'll be making an adversarial instance.
They say they will ban you if you don't follow the rules or cause trouble. I guess we'll see if it's even possible to ban an instance that constantly hops DIDs and attacks through tor lmao
The sandbox environment has now been launched, which means you can set up your own AT protocol-enabled server.
It's possible that Bluesky will finally start federating by the end of summer. However, knowing how most dev teams work, this launch is not a certainty. It always takes time to iron out bugs.
How successful do you think Bluesky's federation will be? And how will it impact the current userbase using Bluesky?
There seems to be a growing amount of uninformed, negative posts on #Mastodon about #Bluesky.
It’s unfortunate that a platform which believes is populated by open minded people do not gather information themselves to form a balanced opinion, but rather jump on the “echo chamber” bandwagon instead.
Kind of reminds me of behavioral patterns on #Twitter. Remember it’s not the platform, but what you bring with you that matters.
@alastor8472 Sure, there are a lot of concerns about minor issues with an app in its beta phase that are being overblown. That always happens with new products, #ActivityPub clients included. A lot of those minor issues will surely be resolved and don't maybe deserve too much attention.
But there is also a growing amount of informed, realistic posts about fundamental issues with #BlueSky and the #ATProtocol. Issues that will likely not be resolved as they are intentional design choices baked in.
But for everything there is a price. I think #BlueskySocial makes a bit more of a balance between #Twitter and Mastodon’s spartan approach. Including algorithms, search, where it’s usefulness for discoverability will also have a another side of the coin.
In the end the user decides though, as long as it’s well informed.