Post

this seems like a real issue w/ the design of atproto in its present form tbh. i really don't want all my accounts to be entangled with my social media such that if the mods don't appreciate my tone i effectively no longer exist on all the other apps in the ecosystem

ponder@ponder.ooo

something i hadn't considered about using tangled while not running my own pds is it means the bluesky social media moderation staff can lock me out of being able to push to my fucking git repos

9 reposts51 likes

atproto is designed such that you can migrate to a new provider in an adversarial scenario. I don't really see what more could be done

They could make it easier to migrate, I think. Or offer alternate hosts when signing up.

i guess my take at the level of the protocol design is that it just doesn't seem all that beneficial to have one account for everything in the first place

i mean i can migrate to another provider but what i get from that is seemingly quite little: i get to keep having an account on other atproto stuff even if i get banned here. but i could already do that by just not using one unified account for all these apps in the first place

i could try to find a different pds host to be beholden to that might be less weenie-ish about my posting, or just self-host. that seems like a pointless hassle when bsky is still the primary hub of social activity on this protocol

seems better to just treat my "atmosphere handle" as just "my bsky account" and just use wholly different accounts for anything else i want to do, even if it's on the atmosphere

don't forget to think about the implications of the "returning from a ban is banworthy" rule for this strategy

Atproto was designed by people who think decentralization means hosting location instead of administrative power and have reacted to any attempt to point that out by abusing the latter. Good luck fixing it now.

this feels like part of the design (ideally, you """simply""" run your own pds!) but yeah it does create a fucked up serf caste, of which i at least remain a part from simple laziness

it isn't enough; they just !takedown you, you disappear from relay/appview. You have to run your own parallel infrastructure *and get people to use it instead of theirs* to make any traction on this.

there are multiple kinds of takedown; for some, yeah unless whatever the thing you're using queries the PDS directly without using any of bsky's infrastructure