The more you look at the challenge of getting people off X and onto Bluesky, the more multilayered it becomes.
(This is published on my experimental wiki because I'm looking for comments, feedback and ideas, preferably on the Discord server, or just ping me). This is version 1 (more version control info in the footer).)
!
As I mentioned in Feel the ATmosphere: it's 1995 all over again, my Ahoy! workshop explored one aspect of what I've come to call "the Bluesky Adoption challenge": getting people to move away from X and the rest and onto Bluesky and the rest of the ATmosphere.
Back then I had a reasonably simplistic view of the problem:
There's therefore a direct line between the above two posts and my Ahoy! conference session, which focused on developing software, services and content to help large organisations adopt Bluesky, the one way I thought a non-developer like me could help (see the Ahoy! proposal and the current version: how could a large organisation best use bluesky)..
But at Ahoy! and since, amid wave after wave of mostly nonsensical "Bluesky is dying" hot-takes, I've discovered that the Adoption challenge is a little more multilayered. I'm following up with those who attended, so this post is me getting my thoughts in order before continuing those conversations.
It’s not enough to have decentralised technology: people have to use it for true decentralisation (and I don't).
Top of mind for everyone throughout the conference was that on day one Bluesky apparently “went down”, leading to a predictable flurry of snark from Mastodon users across the Fediverse (and also, strangely, on Bluesky).
Of course, the truth was far more nuanced:
As one of Bluesky’s engineers mentioned in a testy exchange with ActivityPub co-author Christine Lemmer Webber, the same sort of attack would have taken down a Mastodon server just as quickly. The attack had high impact because although Bluesky’s architecture is decentralised, currently “things are still pretty operationally centralized on bluesky infrastructure”. Or, as another person put it, the headline could equally have been "Bluesky Hit with Massive, Targeted DDoS Attack, Some Users Didn't Even Notice".
The above attack came days after another, equally misunderstood episode, when Bluesky restricted access to 72 accounts in Turkey at the request of the Turkish government. This inevitably leading to claims that Bluesky is “just like Twitter”, from which many Turkish users had fled to Bluesky earlier that month, fearing government censorship.
Except it’s not “just like Twitter”… but again this is hard to follow for those who simply see Bluesky as “Twitter minus Nazis”. As Ahoy! co-organiser Laurens Hof explains in Bluesky, censorship and country-based moderation, the blocked content was visible to not only everyone outside Turkey and anyone in Turkey using a VPN, but also to anyone in Turkey using a 3rd party Bluesky client, which are free to ignore Bluesky PBC’s geographic moderation labeller.
This is therefore a second example of a technically decentralised network looking centralised in practice because most people still use Bluesky Social PBC’s apps and/or infrastructure, creating “a single chokepoint where governments can apply pressure”.
Moreover, as Laurens points out “The output of the geographic moderation labelers is easily and publicly accessible”, so custom feeds can easily highlight the content various governments don’t want their citizens to see.
governments trying to censor Bluesky would just embarrass themselves and highlight the content they’re trying to suppress
If people made real use of the ATmosphere’s decentralised nature, therefore, these chokepoints would disappear: governments trying to censor Bluesky would simply embarrass themselves and highlight the content they’re trying to suppress.
These examples show that while almost everyone on Bluesky uses one company's infrastructure, the network will look centralised, even when built with decentralisable technology.
This undermines one of Bluesky's differentiators against its better-funded, walled garden incumbent competitors. Getting people to migrate to Bluesky is therefore only part of the challenge - getting them onto alternative infrastructure may be almost as important.
I'm embarrassed to admit that I for one still haven’t: like 99% of the population, I don’t have the skills to self-host. Setting up easy-to-use hosting services, in my view, should therefore be a priority for Europe in general, and in particular Indiesky Europe.
At the risk of stating the blindingly obvious: we won't meet the adoption challenge without something it makes sense for people and organisations to adopt.
The past few months have demonstrated that only a small percentage of X users will move to Bluesky in disgust at the prospect of continuing to reinforce the influence of the world's richest Nazi. If this didn't get them to make the move, what on earth will?
!
In a better world, perhaps, people and organisations (companies, governments, civil society, etc.) would adopt Bluesky simply because it's an ethically superior microblogging alternative. But in our timeline, the facts are:
We all know why. X has massive social lock-in: it's where its users' friends and audiences are, and in many cases that network of followers is mission-critical to their livelihood. They're trapped by their followers who are trapped by them, and the "idealist" reason to migrate to Bluesky is simply not strong enough to get most of them to escape the trap, despite what they think of Elon Musk.
I have to say that while this disappoints me, maybe it's crazy to think another outcome was possible.
Talking of crazy... how about launching a product which is almost identical to an incumbent competitor which:
I'm not criticising Bluesky Social's decision-making: it's precisely because they launched a product similar to X that we have ~35m people with ATmosphere accounts, all able to kick the tyres of every other ATmosphere app under development.
Moreover, there are plenty of novel things one can do on Bluesky that you cannot do on X. The problem is that most people don't make good use of them - many people don't even see them, or really understand what they are and how they can use them.
Partly this is because of its deliberate similarity to X: we're so used to microblogging as defined by X, it's difficult for many people to see Bluesky as it's own thing, rather than a left-leaning X. I think it will take time for people to understand what you can and cannot do with features like custom feeds, labellers and verifiers ...if they stick around long enough to scratch below the surface.
Fwiw, my sense is that you can do a lot in terms of open community building, notably by combining Bluesky with other ATmosphere-capable tools into entire ecosystems (see Three things you probably didn't know about Bluesky). But to make those benefits accessible will take high-quality information, inspirational demonstrations and (perhaps most importantly) new management tools, as I explored in Ahoy!
"One way to encourage the transition from X to Bluesky is to help large organisations efficiently organise and manage their Bluesky presence. The better they use Bluesky, the quicker they can accelerate their eXit Strategy" - how could a large organisation best use bluesky).
Most presentations at Ahoy!, however, introduced some of the apps currently under development. At least some appear to be offering "ATmosphere alternatives" of existing incumbents (Tiktok, Instagram, etc.) which are also massively entrenched and superfinanced, with friends at the very summit of political power and are advertising-financed, a proven business model which these new apps (I think!) deny themselves. Sound familiar?
These similarities are probably superficial: just as digging into Bluesky surfaces roll-your-own custom feeds and labellers, I'm sure these apps are improvements over the originals. But maybe we need to step back and ask whether every ATmosphere app wants to make a promise along the lines of "we're just like X/Instagram/X, but with none of your friends, an unclear business plan and a few months of funding"?
Also, the incumbents they're competing with are designed as they are because they're built around the surveillance capitalism business model - they dropped features that weren't useful to that model, and chose features and designs that were. If we don't want to join the surveillance capitalism club, is even superficially mimicking those feature and design choices the best idea?
maybe the best battlefield for competing with incumbents is by offering something they cannot?
Instead, maybe the best battlefield for competing with incumbents is by offering something they cannot? I doubt most people will pay for social media which is identical to the free incumbents but lacks their audience. I can imagine some of them paying for something which delivers greater value than incumbent social media ever can. There are so many things you cannot do with X, Facebook and the rest. Can we have some apps that provide value people cannot get anywhere else, and can we communicate the differences, not the similarities?
Maybe, at the end of the day, the social media we have today is the social media which can be supported by advertising, and X-style microblogging simply cannot provide enough value for most individuals and organisations to pay for it. But there are plenty of online content applications that some people do pay for, and to date they are either productivity software or longform publishing (enewsletter and website publishing). My goal is to combine them, but that's another story.
The adoption challenge sounds simple - let's get people to move from X to Bluesky! - but it's in fact a multi-layered challenge that needs to be tackled on several interrelated fronts:
These activities and goals are interrelated. To envision this I like frameworks. Unfortunately I'm not an artist, but hopefully this shows that my Hamburg workshop tackled a small part of one part of meeting this challenge:
!
Have I missed anything? Let me know*.
*
Unless it's "solve the Bluesky Purity Spiral" argument, which I deliberately left out because (a) I want to tackle problems that can be solved, and (b) I'm totally chicken.
This is one of this wiki's pages managed with the permanent versions pattern described in Two wiki authors and a blogger walk into a bar…