> ## Content Index
> Fetch the complete content index at: https://blog.gelbphoenix.de/llms.txt
> Use this file to discover other available public pages before exploring further.

# Threads and the Fediverse: The Threat That Wasn’t
- URL: https://blog.gelbphoenix.de/threads-and-the-fediverse/
- Published: 2026-10-13T15:00:50.000Z
- Updated: 2026-10-13T15:00:50.000Z
- Description: Meta's Fediverse bridge is in maintenance mode. The fear was huge, the usage was tiny and the lesson goes far beyond Threads.
- Author: Phoenix Paulina Schmid
- Tags: Commentary, WtF?! - What the Fediverse?

Imagine the biggest company on the planet knocks on your village's door and offers to connect you to its highway. Half the village shouts that it's a trap and pulls up the drawbridge. The other half dreams of all the traffic. Then the highway gets built and almost no cars arrive.

That is roughly the story of [**Threads**](https://threads.com/?ref=blog.gelbphoenix.de) and the [**Fediverse**](https://blog.gelbphoenix.de/fedi-what/). In 2024, hardly a week went by without someone asking whether **Meta** would swallow the open social web. Servers signed the [**Fedipact**](https://fedipact.online/?ref=blog.gelbphoenix.de) to defederate from Threads before a single post had arrived. Others argued that federation would finally bring millions of people to the Fediverse.

In December 2025, *Connor Hayes* (Head of Threads) said in an interview that the Fediverse integration is now in maintenance mode. The "[Fediverse Report](https://connectedplaces.online/reports/fediverse-report-147/?ref=blog.gelbphoenix.de)" called it an effective end to a turbulent chapter.

Both camps were arguing about a future that never fully arrived.

## ***The threat that fizzled out**

The fear was classic: [embrace, extend, extinguish](https://en.wikipedia.org/wiki/Embrace,%5Fextend,%5Fand%5Fextinguish?ref=blog.gelbphoenix.de). A giant joins an open network, floods it with users and then bends it to its own interests.

The numbers tell a very different story. In January 2025, [mastodon.social](https://mastodon.social/?ref=blog.gelbphoenix.de) knew of roughly 25,000 Threads accounts with federation switched on and only about 800 Threads users followed at least one account on that server as the "Fediverse Report" reported in 2025\. *That's a trickle.*

An earlier analysis put the actual users of the bridge at likely fewer than 50,000 out of around 275 million monthly users and noted that posts only appeared in the Fediverse after a 15-minute delay.

Meta kept expanding the feature anyway. By June 2025, sharing was available globally, with a Fediverse feed and profile search inside the app. Even overviews from early 2026 (by e.g. [FediView](https://fediview.com/articles/threads-fediverse-integration-mastodon-2026/?ref=blog.gelbphoenix.de)) still describe the federation as partial.

The threat existed in theory, but almost nobody used the bridge.

## ***Openness on someone else's terms**

The detail I find more interesting than the user numbers is the EU. 

Threads' Fediverse sharing launched elsewhere first and stayed unavailable for users in the European Union and [Meta's own European Region](https://help.instagram.com/1786494975158796?ref=blog.gelbphoenix.de), and Meta never gave a clear reason. Laurens Hof of the "Fediverse Report" read this as the integration being kept around as a possible bargaining chip with the EU. That is his interpretation, not an established fact *but interesting to look at*.

A platform that decides where its openness applies, how fast it works and how much attention it gets is open only when that suits it. When priorities change, support quietly drops to maintenance.

The bridge belongs to Meta. The protocol doesn't.

## ***What it means if you publish on your own**

This blog runs on [**Ghost**](https://ghost.org/?ref=blog.gelbphoenix.de), which federates via [ActivityPub](https://blog.gelbphoenix.de/deep-dive-into-activitypub/), and its follow dialog even names Threads next to [Mastodon](https://blog.gelbphoenix.de/beginners-guide-to-mastodon/) and [Flipboard](https://blog.gelbphoenix.de/flipboard-meets-the-fediverse-a-new-era-of-content-aggregation/). In theory, anyone on Threads could follow this blog [directly](#/activitypub).

> In my own experience, activating ActivityPub on this blog did not bring a single follower from Threads, and only minimal clicks on individual posts and on the blog as a whole.

***If you like this blog post you can support my work by either becoming a paid member or leaving a tip.**

[Donate ](#/portal/support) 

Whatever your numbers look like, the lesson is the same. Reach through a bridge you don't control is a bonus. The relationship with your readers that lasts runs through things you own.

## ***What you can do**

**Own your domain.** It is the one identity anchor no platform can switch off. I wrote about how in [The Domain as Your Passport](https://blog.gelbphoenix.de/the-domain-as-your-passport/).

**Publish through open standards.** ActivityPub, RSS and email keep working when a single platform loses interest. You can read ["Connecting Your Blog to the Fediverse"](https://blog.gelbphoenix.de/connecting-your-blog-to-the-fediverse-a-guide-for-independent-publishers/) and posts of the "A Beginner’s Guide to Decentralized Social Media" series for this. 

**Treat big platforms as a place you visit.** Threads can be a nice extra audience. *It shouldn't be the place you live.*

**Be skeptical of both hype and panic.** The next big integration will come with the same two choirs. *Look at the numbers first.*

The Fediverse didn't need Threads to survive, and Threads didn't kill it either. A network built on open protocols outlives the interest of any single big participant. Your own corner of it can do the same.

***If you haven't already, point your handles at a domain you own. Then it doesn't matter which platform's bridge breaks next.***