Sure, but most of the replies to your op here aren’t debates, just shit-flinging lol.

Man why do you spend your time responding to these people (if not LLMs)?

Honestly preferring an enum and avoiding the assert is incredibly Rust-y.

Errr trivial portability lol

The design of Bluesky was intended to allow for tribal portability such that a PSS banning you didn’t really matter, you’d just move your data and use a new one. AFAIU (and I don’t follow it closely really) that isn’t quite what has happened.

A big part of these types of outcomes is also based on the community that forms around them. Bluesky ended up, for various reasons largely unrelated to its underlying protocol, being adopted by a very specific community, and that community views policing untoward speech as a core part of how social media should operate (not passing judgement on that here!). While the protocol design attempted to do that at a higher layer, the community’s strong stance on moderation and the developer’s need to fight urgent spam and moderation fires meant that protocol neutrality took a back seat. Once it was there, with a rapidly-growing community that viewed this as good, it wasn’t coming back.

And in this case it doesn’t apply :)

The community that adopted it is quite different from the folks who built it.

Same, man. Same 😢

Welcome to the Bitcoin/nostr community. Lazy people who don’t like you for reasons they can’t even articulate default to “scammer”.

It’s quite a shame where Bluesky ended up. Having infrastructure be neutral was a core tenant of the way it was originally pitched, and is why the whole “labeler for moderation” thing was built at all. They’ve ended up rebuilding Mastadon with the insane cross-instance blocking wars.

@note1s5vc4...

Idiocracy, but for people with Narcissistic Personality Disorder.