Skip to main content
 

What if we worked together

"Remember! If you only signed up to hear when this feature is available, or you're wondering what ActivityPub even is: This probably is not the newsletter for you. This is a behind-the-scenes, engineering-heavy, somewhat-deranged build log by the team who are working on it."

And I love it.

Ghost's newsletter / blog about building ActivityPub support into its platform is completely lovely, and the kind of transparent development I've always been into. Here it's done with great humor. Also, they really seem to be into pugs, and that's cool, too.

In this week's entry the team is investigating using existing ActivityPub libraries and frameworks rather than building the whole thing from scratch themselves - and doing it with not a small amount of humility.

And they're building a front-end to allow bloggers to consume content from other people who publish long-form content onto the web using ActivityPub. I'm excited to see it take shape.

[Link]

· Links · Share this post

 

Bluesky and Mastodon users can now talk to each other with Bridgy Fed

"An important step toward a more interoperable “fediverse” — the broader network of decentralized social media apps like Mastodon, Bluesky and others — has been achieved."

Bridgy has always been a useful product; Bridgy Fed is an easy way for folks on the fediverse and on Bluesky to be able to interact with each other. I've opted in and I expect many other people to do the same.

Ideally it wouldn't be an opt-in - I think this kind of bridge is incredibly useful in its own right. I know it's been fraught on the Mastodon side because of Bluesky's provenance and former relationship to both Twitter and Jack Dorsey. I personally don't see the issue at all: the more the merrier.

Ryan Barrett is brilliant: I really appreciate his ability to quietly add value by creating user-first technology solutions that speak for themselves.

[Link]

· Links · Share this post

 

Why publishers are preparing to federate their sites

"At least two digital media companies are exploring the fediverse as a way to take more control over their referral traffic and onsite audience engagement."

The Verge and 404 Media will both support ActivityPub (a protocol, not a "plugin", as the article calls it) and plug into the fediverse.

This dovetails with what I've been talking about for some time: "Instead of spending time building a presence on other platforms for their benefit, a publisher can do that on their own sites — while giving readers the ability to see those posts on other federated platforms." And while the fediverse is still in an early, growing stage, it's worth taking a bet on.

As Flipboard's Mike McCue says further into the piece, "What The Verge is doing is definitely pioneering the future for media." I'm hopeful that more publishers follow suit - with this and other experiments that have the potential to help them build more direct first-party relationships with their audiences.

[Link]

· Links · Share this post

 

Extinguishing the fediverse

The Mastodon homepage, displayed on a smartphone

I’m soliciting prompts for discussion. This piece is a part of that series.

 

Erlend Sogge Heggen asks:

There’s legitimate reason to be worried about Meta’s P92 project being part of a EEE play against the fediverse.

How might the fediverse community counteract this, perhaps with its own EEE strategy?

We know Meta will attempt an EEE play, but what if we play the reverse UNO card and EE(E) them instead?

Embrace: Carefully federate in a minimum-viable fashion that doesn’t overrun the existing .

Extend: Make a reality, so accounts can be moved effortlessly.

Extinguish: In case of misconduct, defederate and provide mass-migration assistance.

First, some quick definitions!

P92 is the codename for Meta / Facebook’s new app that will support the same ActivityPub protocol as Mastodon and its cousins. Users will be able to log in with their Instagram credentials, and one can potentially (but not definitely) imagine it being folded into the mainline Instagram app.

Embrace, Extend, Extinguish was a phrase coined internally inside Microsoft to describe its strategy with respect to the web. The idea was that the company would embrace open protocols, extend them with its own proprietary extensions, and then use its control over those extensions to extinguish competition. In particular, its plan was to do this with HTML in order to cement Internet Explorer as the web browser.

Finally, the fediverse, of course, is the community of small, independently-owned, largely non-profit social networks that interoperate using shared protocols, on which Mastodon is the largest platform.

There is legitimate concern that a company like Meta might attempt to control the fediverse. This is particularly true if they are allowed to create a uni-polar world: one where Meta is the only large company embracing these standards. In that world, Meta can throw hundreds of millions of users at the protocol, and it will instantly become its largest user.

I think it’s helpful to look at how Microsoft’s EEE strategy failed. There were arguably two main factors: antitrust risk and competition.

The Department of Justice sued Microsoft for monopolistic business practices, ultimately leading to a settlement where Microsoft capitulated to changing some of its approach in return for the DOJ dropping its desire to break up the company. It’s not clear to me that this kind of case would or could take place with respect to Meta extinguishing the fediverse; while I’m not a lawyer, I think the argument would probably be that many other social networks are available.

The other thing that hurt Microsoft’s dominance was Firefox. It was a good browser backed by a good community, but that wasn’t the deciding factor; Firefox gained market share because Google pushed it at every possible opportunity. Because Internet Explorer’s dominance was a business risk to Google, and because Firefox was built by a non-profit that was non-competitive with Google’s business, it made financial sense to try and break Microsoft’s stranglehold. Mozilla’s model was stronger than its predecessor Netscape’s had been: whereas Netscape needed to sell licenses, Mozilla’s deal with Google meant it made money every time someone used Firefox to search for something on the web. There was almost no friction to its growth strategy.

This activity led to a resurgence in a healthy ecosystem of standards-based web browsers for years — until Google decided to re-use the technique it had used on Firefox to push its own web browser. Even then, Chrome is a far better standards player than Internet Explorer ever was.

There won’t be hard evidence that Meta is adopting ActivityPub until we see its app in the wild. But if it is, that likely means that it sees the protocol as at least worth experimenting with, and maybe even as a potential threat. That’s a sign of great progress, and everyone involved in building the fediverse should feel good about it.

If Meta wants to own the fediverse, this isn’t a battle that will be primarily won with features or technology. Easy-to-use platforms, nomadic identity that easily lets you move your presence from one provider to another, and assistance will all be essential, but they’ll be table stakes. (If Meta is working on the platform today, it’s probably also too late for truly nomadic identity to make a difference.) To really stand a chance, the fediverse will need the kind of marketing and go-to-market support that Firefox enjoyed back in the day. Which may mean support from another large player that considers Meta’s ownership of the standard to be an existential risk.

It’s hard to see who that might be. Twitter is now the incompetence wing of the incompetence party. It’s highly unlikely that networks like Pinterest care. Microsoft’s platforms are tightly bound to its ecosystem, with access control at their core; I don’t see LinkedIn joining the fediverse any time soon. Google has fallen on its face every time it’s tried to build a social network, and runs YouTube as a separate entity that strongly benefits from closed ads. Salesforce might consider it a risk, as it provides social tools for businesses, which are easier to build and sell on an open social networking standard. Some of these entities might consider the fediverse to be worth exploring — but there’s no clear technology backer. Cloudflare actually did provide its own Mastodon-compatible platform that runs on its CDN, but it hasn’t seen anything like wide use. Medium has embraced Mastodon but has not deeply built support into its existing platform.

Perhaps media companies, who generally live and die on the size of their audiences, and have often been beholden to the large social networks, might find themselves interested in embracing a social networking federation where they have more say and control. The rise of the fediverse certainly is a de-risking of their business models. But I don’t think they see it yet; nor do I think they consider it their place to pick a winner. (Nor should it be, really, in practice.)

Perhaps there can be another kind of backer: an entity that sees the existential thread centralized control of social media poses to democracy itself. We’ve already seen how, left unchecked, centralized companies like Facebook incite genocides and throw elections. The fediverse can be an antidote to these trends — if we see it as a set of collaborating communities rather than simply the technology alone. The erosion of democracy, like monopolistic abuse of power, are human problems with human solutions rather than technological ones. Foundations and philanthropists may choose to provide this level of support, if they continue to see Meta as a threat to democracy.

Building features will not protect the fediverse from being extinguished, although they may provide a useful baseline. It’s going to take a whole different level of strategy, relationship-building, deal-making, and movement-building. I believe the fediverse is capable of doing this, as long as it doesn’t mistake building software for making true progress.

· Posts · Share this post