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...

trezy.comThe Marshmallow Test - Bluesky signals it's willing to eat its youngAt AtmosphereConf, Bluesky celebrated its community, then signaled it's willing to eat them alive. No context. No acknowledgment. I was in the room.

Boris

@bmann.ca

31 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.

Trezy

@trezy.codes

I’m not sure I see the value of that distinction. Both are built for effectively communicating with a community, regardless of the integration points.

31/3/26, 6:39 pm0 reposts18 likes

Boris

@bmann.ca

31 Mar

If you haven't been doing much ecosystem relations then it can be challenging. Probably should have been called Bluesky Report too Something like (not fully fleshed out): protocol (pre standards) -> protocol IETF -> ecosystem -> implementation codebases w/ contributors -> operators -> etc