Post

Finally done. I was able to talk with @pfrazee.com, as well as a handful of other folks with insight on the situation. #atmosphereconf trezy.com/blog/the-mar...

One of the challenges here is that "developer relations" in other open source or company contexts is around a single codebase, an inside & outside. So for me, this is "ecosystem relations" & networked orgs, which are subtly different. e.g. there are no third party atproto developers.

"there are no third party atproto developers." This is the other big takeaway for me: Bluesky is a business, Atproto is an open-source protocol, the sooner they operate independently the better. Atproto should have its own governance (beyond IETF work), its own devs, its own funding. ...

Once Atproto is independent, Bluesky can open PRs or issues against the protocol like everyone else. Protocol maintainers are free to prioritize what the entire community benefits from accordingly, and other teams are free to innovate on top of it however they want. This is the way.

And then, you get 3rd party atproto devs. People contributing directly to the protocol because they want to see the protocol be stronger.