The protocol is protected. https://github.com/bluesky-social/atproto/ https://github.com/bluesky-social/atproto/ "Dual MIT/Apache-2.0 License Copyright (c) 2

The protocol is protected. https://github.com/bluesky-social/atproto/ https://github.com/bluesky-social/atproto/ "Dual MIT/Apache-2.0 License Copyright (c) 2022-2024 Bluesky PBC, and Contributors Except as otherwise noted in individual files, this software is licensed under the MIT license (<http://opensource.org/licenses/MIT http://opensource.org/licenses/MIT>), or the Apache License, Version 2.0 (<http://www.apache.org/licenses/LICENSE-2.0 http://www.apache.org/licenses/LICENSE-2.0>). Downstream projects and end users may chose either license individually, or both together, at their discretion. The motivation for this dual-licensing is the additional software patent assurance provided by Apache 2.0." Even when Bluesky decides to fuck around with the licenses, everybody is free to fork the current version crediting Bluesky PBC due to the MIT and Apache 2.0 license allowing this. And besides that, the community could also decide not to support AT at all but put their full weight behind Nostr (https://nostr.com/ https://nostr.com/) UPDATE: And the protocol spec is licensed under Creative Commons: https://github.com/bluesky-social/atproto-website/ https://github.com/bluesky-social/atproto-website/ "Creative Commons Attribution (CC-BY) Copyright (c) 2022-2024 Bluesky PBC, and Contributors Documentation text and blog posts in this repository are licensed under a permissive CC-BY license. For anybody interested in derivative works of documents and specifications, remember that: - you must give attribution (credit) to the original work - you must indicate any changes made - trademark rights are not granted (for example, to "Bluesky", "AT Protocol", or "atproto", or any logos or icons) Inline code examples, example data, and regular expressions are under Creative Commons Zero (CC-0, aka Public Domain) and copy/pasted without attribution."