💻️ Reading BlueskyがActivityPubを採用しなかった3つの理由 (Three reasons why Bluesky didn’t adopt ActivityPub)
This page discusses why Bluesky chose not to adopt ActivityPub, the open protocol used by Mastodon and others, and opted to make its own, ATProtocol.
- Architectural Differences: ActivityPub’s model did not align with Bluesky’s vision for scalability and flexibility.
- User Experience: Integrating with ActivityPub could have limited Bluesky’s control over its features and user experience.
- Technical Challenges: Compatibility with existing ActivityPub networks would require significant adjustments that might compromise Bluesky’s goals.
AT Proto addresses these by improving:
- Scalability: Designed to handle higher traffic and expand seamlessly.
- Modular Flexibility: Allows customization without being constrained by the limitations of ActivityPub.
- User Data Portability: Focuses on improving data interoperability between platforms.
🤔 The author equates ATProto to solving for “Big Fedi” while still maintaining the nimbleness within to handle “Small Fedi” ideals on a granular scale. This is as opposed to Mastodon’s catering to “Small Fedi,” only. Oh what are these anyway? It’s a concept that Evan Prodromou (@evan@cosocial.ca) outlined in his blog post here defining two schools of thought regarding social networks. It’s highly encouraged to read through that post and perhaps even drop him a line if you’re interested in these topics.
At some point I’ll give my thoughts and post them over on the main starrwulfe.xyz blog once I unpack them, and also how I’m doing this with some #indieweb secret sauce; stay tuned! 📺️