neko-moe

5 ms·

1.
by neko-moe 2mo ago
or keeping your own plc rotation key and a backup of your user repo, then you can migrate even after bluesky issues a takedown on your user.
2.
by neko-moe 3mo ago
Because if you want to relay every single public event for every single user on the entire atproto network in real-time to many consuming apps and services… that's gonna cost something. Not that it costs a lot, but to expect what a r
3.
by neko-moe 3mo ago
They're funding Fig to create and run a "full network backup" solution. What Bluesky really needs to do is figure out a way to get users to own their own backup recover key, whether personally or through some third-party serv
4.
by neko-moe 3mo ago
Not really, considering there aren't that many app servers. Each PDS sends out its events, those events are picked up by whoever wants them, mostly relays but some apps might directly subscribe. The more apps in play, the more connecti
5.
by neko-moe 8mo ago
You can host your own instance, but resolving forks is not self-authenticating and requires some central trust (because of the 72 hour rollback window for higher priority rotation keys). Not counting that, you could essentially run your own
6.
by neko-moe 1y ago
> I can't stress this enough: I don't find it acceptable to ban people if they like posts or follow someone who gets banned. To the best of my knowledge, that kind of banning has only happened once[1] (I was one of the handful
7.
by neko-moe 1y ago
Relays aren't really user-facing, so most relay operators would probably only censor a user on the relay if there is some legal or network reason to do so, say content illegal in their jurisdiction or excessive spam. If an app is conce
8.
by neko-moe 1y ago
> [...] It's technically possible for people to use alternative services, but the community would have to wrestle the majority control of the network away from Bluesky Social PBC for it to really matter. [...] > [...] now you jus