Threads, Bluesky and Decentralised Social Networks: Who Really Owns Your Followers and Digital Identity?
A large follower count can look like a personal asset. Creators spend years building audiences, companies invest money in community management, and individual users accumulate relationships that become part of their public identity. Yet the number shown beside a profile does not necessarily mean that the account holder controls those connections. In most social networks, followers exist as relationships recorded and managed by the service where the account was created. If access to that account changes, the rules change or the service closes, taking the same audience elsewhere may be difficult or impossible. Threads, Bluesky and decentralised social networks have made this issue much more visible by 2026. They represent different approaches to identity, interoperability and account migration. The important question is therefore not simply who technically stores a follower list, but how much practical control a person has over their name, content, relationships and ability to move without rebuilding an audience from zero.
What It Really Means to Own Followers in 2026
Followers are not property in the ordinary sense. Every follower is another person who has chosen to create a connection with an account, and that choice can normally be withdrawn at any time. What users can reasonably control is the account through which those relationships are organised. On a conventional social network, the service maintains the account database, decides how profiles are identified and determines which actions are available. A creator may therefore have hundreds of thousands of followers while still having limited control over the infrastructure that makes those connections usable.
This distinction becomes important when an account is suspended, deleted or moved. Having access to a list of usernames is not the same as carrying an active community to another service. A downloadable archive can preserve information, but it may not recreate follow relationships elsewhere. Genuine portability goes further: the new account needs a recognised identity, compatible data and a mechanism that allows existing connections to continue. That is why data export and audience portability should not be treated as identical features.
Digital identity is broader than a username. It includes the public name people recognise, the account history associated with it, posts, reputation, follower relationships and sometimes verification through a web domain. Control over all of these elements varies considerably between social networks. The strongest form of user control available in 2026 is therefore not literal ownership of followers. It is the ability to maintain a recognisable identity, retain useful account data and change service providers without unnecessarily losing established relationships.
Threads: Interoperability Without Complete Audience Portability
Threads illustrates how a large centrally operated social network can become more open without giving up its central account structure. Meta reported in June 2026 that Threads had reached 500 million monthly active users. This scale gives creators and organisations access to a substantial potential audience, but the core Threads account, its availability and much of its distribution remain managed by Meta. Feed ranking, moderation decisions, account features and access conditions can consequently affect how easily an account reaches the people who follow it.
At the same time, Threads has moved significantly towards the fediverse through ActivityPub, an open standard that allows compatible social services to exchange posts and social interactions. Users who enable the relevant fediverse features can interact with people outside Threads, while people using compatible services can follow eligible Threads accounts. Meta also introduced direct searching for fediverse profiles and a dedicated feed for posts from federated accounts. This means that part of a Threads audience no longer has to exist exclusively inside Threads itself.
Interoperability should not, however, be confused with complete account portability. The ability of a Mastodon user to follow a Threads profile does not automatically mean that the owner of the Threads profile can move the entire account, historical content and all follower relationships to a different service whenever they choose. Meta has described full interoperability as an ongoing objective, and its published fediverse updates have concentrated on cross-service following, viewing and interaction. In practical terms, Threads gives users a broader communication boundary than a completely closed social network, but control over the primary account still remains closely connected to Meta.
How Bluesky Makes Digital Identity More Portable
Bluesky approaches the problem from a different direction. It is built on the AT Protocol, which was designed so that identity, follows and account data are not permanently tied to one social application. The protocol separates a person’s identity from the particular service used to display posts. For ordinary users, much of this happens invisibly, but the effect is important: the account can have a persistent technical identity that applications can recognise even when some visible account details or hosting arrangements change.
Bluesky users normally see a familiar handle, but underneath it the AT Protocol also uses a persistent identifier. Handles can be connected to internet domain names, allowing a person or organisation to use a domain they control as part of their social identity. A publication, for example, can use its own domain rather than relying entirely on a name issued by one social company. This does not make the account immune to every problem, but it reduces dependence on a single company-controlled naming system and makes identity easier to verify across compatible applications.
The account data model is also designed with movement in mind. Posts, follows, likes and other records are stored in a user’s data repository, while personal data servers host and distribute that information. Bluesky has supported migration between compatible hosts, and in September 2025 it also enabled eligible users who had moved away from Bluesky’s own hosting service to migrate back. By March 2026, Bluesky reported more than 40 million users, meaning that account portability was no longer merely an idea being tested by a small experimental network.
What AT Protocol Portability Can and Cannot Protect
Portability does not make changing account hosts completely risk-free. Bluesky itself has warned that account migration can be a potentially destructive operation if something goes wrong. Users still depend on software working correctly, compatible services recognising account information and the account owner keeping credentials secure. A more portable architecture reduces dependence on one provider, but it cannot eliminate ordinary risks such as account compromise, lost access credentials or poor management of a domain used as a handle.
Moving an identity also does not guarantee an identical experience after the move. Social feeds, recommendation systems, moderation services and interface features can be provided separately from the underlying account data. A person may therefore keep an identity and social graph while seeing different recommendations or moderation decisions in another application. This separation is intentional: it allows several services to work with the same underlying social network without requiring each of them to present information in exactly the same way.
There is another trade-off that is easy to miss. Portability is not the same as privacy. Bluesky’s AT Protocol was designed primarily for public social communication, and much of the information associated with public interaction can be available across the network. Follows, public posts and other social records need to be readable by compatible services if those services are expected to reconstruct relationships and conversations. Users gain more freedom to move their identity, but that freedom should not be interpreted as a guarantee that social activity is private or stored only in one location.
What Decentralised Social Networks Change for Users
Decentralisation changes who can operate the infrastructure behind social communication. ActivityPub, the standard used by Mastodon and supported by Threads for fediverse communication, allows independent servers to exchange social information. A Mastodon community can therefore be run by a company, organisation, university, individual administrator or another group while still communicating with accounts located on other compatible servers. There is no single organisation that owns the entire fediverse or controls every account within it.
This arrangement does not mean that nobody has authority. Each server has an operator, technical infrastructure and its own moderation rules. Administrators can decide which accounts are accepted, what behaviour is allowed and which other servers their community communicates with. Users are less dependent on one global company, but they may still depend heavily on the operator of the server hosting their account. Decentralisation redistributes control; it does not remove control from the system.
Mastodon provides a useful example of both the benefits and the limits of this model. Its account-migration system can redirect an old profile to a new one and automatically request that followers move to the new account when the receiving software supports the relevant ActivityPub mechanism. However, historical posts do not automatically move with the profile. Lists of followed accounts, blocks and mutes may also need to be exported and imported separately. A user can therefore carry an important part of the social graph while still leaving some account history behind.
How to Build an Audience You Can Actually Carry With You
For creators, businesses and public figures, the most reliable approach is to avoid making one social account the only point of contact with an audience. A personal or company web domain provides a stable reference that can remain the same when individual social services change. An email list built with proper consent can provide another direct communication route. Social accounts can then work as distribution channels around a more durable identity rather than becoming the sole place where the relationship between a publisher and its readers exists.
Users of newer decentralised systems can also make practical use of the portability features already available. A Bluesky user can consider using a domain-based handle and should keep account recovery information current. Mastodon users can maintain exports of useful account lists and understand the migration procedure before they need it. Threads users who have access to fediverse sharing can use it to make their public posts and identity visible beyond Threads. Regular data exports are useful in all cases, although an export should be viewed as a backup rather than proof that every social connection can be reconstructed elsewhere.
By 2026, social networking is no longer divided neatly between closed services and fully decentralised alternatives. Threads combines a centrally managed account system with growing fediverse interoperability. Bluesky gives identity and social data a more portable role through the AT Protocol. Mastodon shows that follower migration between independent servers can work while also demonstrating the limits of moving historical content. None of these approaches gives a user ownership of other people. The meaningful form of control is the ability to preserve a recognisable identity, keep useful data, maintain several routes to an audience and leave one service without automatically losing every relationship built there.