I think what many folks really want from "federation" is a situation where no one party has more than 40% (or 10%, or whatever) of the network. That is a powerful and special property! Fediverse has it today, and most networks don't. It is different from adversarial interop though. There are open systems, like email (gmail) and git (github) which have sort of lost this. I still think the interop in those systems is valuable.

bluesky got more funding, and is working on several sustainable revenue models: subscriptions, domain registration, and payments. work continues on atproto: tooling for independent Lexicon development; more docs/specs and testing for interop; more complete and documented SDKs

Bluesky

Bluesky Announces Series A to Grow Network of 13M+ Users - Bluesky

Bluesky now exceeds 13 million users, the AT Protocol developer ecosystem continues to grow, and we’ve shipped highly requested features like dir...

#bluesky #atproto

wrote up a proposal for exposing "moderation history" back to individual accounts as part of Ozone, an atproto moderation system. I think that the Mastodon reporting system already has similar functionality, but not sure about other ActivityPub project. Curious for feedback!

GitHub

proposals/0005-mod-history at main · bluesky-social/proposals

Bluesky proposal discussions. Contribute to bluesky-social/proposals development by creating an account on GitHub.

#atproto #bluesky #moderation

really excited about this tutorial we put out last week describing how to build a minimal non-bsky app on atproto: "Statusphere"

AT Protocol

Quick start guide to building applications on AT Protocol - AT Protocol

In this guide, we're going to build a simple multi-user app that publishes your current "status" as an emoji.

GitHub

GitHub - bluesky-social/statusphere-example-app: An example atproto application using ExpressJS and Typescript.

An example atproto application using ExpressJS and Typescript. - bluesky-social/statusphere-example-app

there are a lot of questions (and options!) about how cross-app data+interaction will work in atproto, but at a minimum I think the protocol is quite solid for building new apps/modalities, and excited to finally demonstrate it!

is adversarial interoperability a goal for the ActivityPub/Mastodon ecosystem? how does it interact with opt-in culture/expectations?