Yeah one of the crazy things is that it's like super lucky and rare to detect that kind of cancer early, so all he had to do was help himself and he didn't.

Yeah! Agreed, but I think some of that is still product strategy. If you're building an app that is just straight up dependent on Bluesky, the expectations are that you have access to your BSky social graph.

What's funky are things like Spark, where there's both BSky content and non Bsky content.

It's a fun example of both new apps being possible in the ATmosphere, but the infrastructure supporting multiple actors in the same modality/product space.

Have you checked out blacksky.community ?

You can pay to keep them up and running, their model is pretty clear about how they're going to keep going, and they're running their infrastructure (mostly) independent of BSky, and getting close to being completely independent.

Like having a platform that is default open vs default closed can still respect users' autonomy to pick one or the other, but everybody is going to start with their account in one or the other state, and people will have expectations about how to interact on that basis

Some of this stuff shouldn't be left ambiguous or negotiated on the fly, because setting user expectations is important for both establishing the norms and for making sure folks aren't surprised by how a space operates.

This is ultimately talking about social dynamics and the rule setting (through defaults) for hosting spaces.

User choice is absolutely a thing to be respectful of, but it's kind of missing the point. We're talking about establishing shared social compacts.

PDSMoover is great and handles one specific piece of a much broader ecosystem.

If all of Bluesky's servers crashed tomorrow, PDSMoover by itself isn't going to keep the ATmosphere going.