In the software industry, we often take open protocols for granted. The foundational layers of the internet—like email (SMTP), the web (HTTP), and file transfers (FTP)—are public utilities. No single corporation owns the trademark for "email," and no board of directors can revoke a developer's access to write an HTTP-compliant web server.
However, as the social web shifts from centralized walled gardens to decentralized networks, a new governance dilemma has emerged.
With Bluesky's recent acquisition of the trademark for the AT Protocol (atproto), creators and developers are facing a complex question: Can a social protocol remain truly open and decentralized when a single corporation owns its name and brand?
To understand what this means for the future of independent media and online business, we have to look closely at how these protocols are governed, how they differ, the legal realities of open-source trademark policy, and why trademark ownership is the new battleground for digital sovereignty.
1. Protocol vs. Platform: Why Trademarks Matter
To evaluate this change, we must first separate the protocol from the platform.
- The Protocol (AT Protocol): The invisible plumbing that defines how user data, identities, cryptographic keys, and social feeds move across the network.
- The Platform (Bluesky): The specific app, user interface, indexers, and hosting infrastructure run by Bluesky PBC to access the protocol.
In a fully decentralized ecosystem, anyone can host their own Personal Data Server (PDS), design a custom algorithmic feed, or build a third-party client app.
However, a trademark is a legally enforceable right to prevent confusion in the marketplace. While the software code itself is open-source (under permissive MIT or Apache 2.0 licenses), the brand name is proprietary.
According to Bluesky's official announcement, their acquisition of the "ATPROTOCOL" trademark was a defensive measure. A third-party company was threatening legal action that would have prevented Bluesky and other developers from using the term. By securing the trademark, Bluesky aims to shield atproto developers from legal trolls who might otherwise hijack the brand name.
2. Open Source Code vs. Proprietary Trademarks: A Common Practice
For many developers, the idea of a trademark on a decentralized protocol feels antithetical to open-source software. However, in the wider tech ecosystem, decoupling code licensing from trademark ownership is the industry standard.
While an open-source license allows anyone to copy, modify, and distribute the code, it does not grant the right to use the project’s name or logo for commercial branding. This distinction exists to protect user trust and prevent malicious actors from distributing harmful forks under the guise of an official project.
Consider these high-profile examples:
- Linux: The code is open and free under the GPL, but the "Linux" trademark is owned by Linus Torvalds and administered defensively by the Linux Mark Institute to ensure the name is used only for legitimate Linux-based operating systems.
- Python: The Python Software Foundation (PSF) holds the trademark for the Python logo and name, requiring third parties to obtain licenses for commercial conferences or products using the brand.
- Rust: The Rust Foundation's draft trademark policy generated significant controversy in the developer community when it attempted to restrict how developers could use the name in package managers, events, and project names.
- Mozilla Firefox: Mozilla famously enforces its trademark strictly. For years, the Debian project had to distribute Firefox under the name "Iceweasel" because Debian's open-source modifications did not align with Mozilla's strict trademark guidelines.
By owning the trademark defensively, Bluesky PBC adopts this same model. It ensures that a bad actor cannot build an incompatible, insecure fork and market it as the "Official AT Protocol" to phish user credentials.
3. ActivityPub vs. AT Protocol: Two Paths to Decentralization
The open social web is currently dominated by two different philosophies of governance:
| Feature | ActivityPub (W3C Standard) | AT Protocol (Bluesky Standard) |
|---|---|---|
| Governance Body | W3C Social Web Working Group | Bluesky PBC (Transitioning to independent org) |
| Trademark Owner | W3C (Neutral Standards Consortium) | Bluesky PBC (Holding defensively) |
| Standardization Path | Multi-stakeholder consensus | Corporate draft submitted to IETF |
| Ecosystem Control | Highly fragmented, no single authority | Highly aligned around Bluesky's indexers |
The ActivityPub Model: Democratic & Slow
ActivityPub is governed by the World Wide Web Consortium (W3C), the same standards body that oversees HTML and CSS. W3C is a neutral, non-profit consortium consisting of hundreds of member organizations.
Because of this, no single company—not even Meta with Threads—can unilaterally change how ActivityPub works or restrict who uses the name. The downside? Consensus takes time. The W3C Social Web Working Group is currently working on updating the protocol specifications to solve interoperability issues, but the process is deliberate and slow.
The AT Protocol Model: Defensive Ownership & Open Use
The AT Protocol was built to move fast. Spun out of a Twitter-funded project, it has been guided primarily by the Bluesky development team.
To address centralization concerns, Bluesky has explicitly stated that they plan to transfer trademark ownership to an independent, neutral protocol governance organization in the future. For now, holding it under Bluesky PBC is a practical way to provide an immediate legal shield using the company's corporate resources.
Furthermore, Bluesky's trademark policy draws inspiration from major open-source projects like Rust, Python, and Apache. Under this policy:
- Everyday Developers Don't Need a License: You can reference the protocol, state that your app is compatible with atproto, write documentation, and name open-source libraries (e.g.
atproto-feed-toolorAT Protocol SDK) without fees or permissions. - Only Commercial Brands Need Gating: Product names, paid events, registered domains, or company brands that present themselves as AT Protocol (rather than compatible with it) require a commercial license to prevent confusion.
4. What This Means for Independent Creators
For the average creator, artist, or independent business using these platforms to build an audience, the trademark acquisition has minor immediate technical impact, but major strategic implications.
1. Your Data and Identity Remain Secure
The core promise of the AT Protocol is cryptographic data portability. Because your handle is tied to a domain name you own, and your data is stored on a PDS, Bluesky PBC cannot seize your audience or delete your content. Even if they enforce trademark rules on their app, they cannot technically lock you out of your cryptographic data.
2. The Nuance of Commercial Branding
While open-source compatibility is protected, developers building commercial tools must tread carefully. If you plan to market a paid product or register a company name directly using "AT Protocol" or "atproto", you will need to coordinate with Bluesky's trademark team. This ensures the brand remains associated only with authentic, compatible implementations.
3. The Importance of a Hybrid Approach
This development reinforces why creators should rely on the IndieWeb philosophy of POSSE (Publish on Own Site, Syndicate Elsewhere). By hosting your primary business directory and content on your own self-hosted domain, you ensure that no matter how protocol trademarks, server rules, or corporate alignments change, your home base remains secure.
Sources and References
- Official Announcement: Bluesky AT Protocol Trademark Policy and Defensive Acquisition
- IETF AT Protocol Drafts: Taking AT Protocol to the IETF
- PDS Reference Architecture: Personal Data Server (PDS) Federation Architecture Guides
- AT Protocol Specifications: AT Protocol Brand and Domain Registry Guidelines
- W3C Social Web Working Group: Governance and Multi-Stakeholder Standards
- Linux Trademark Policy: Linux Mark Institute Trademark Guidelines
- Rust Trademark Policy: Rust Foundation Trademark Policy
Comments
Loading comments from the Open Web...