Live data from Hacker News

Viewing profile — neko-moe

neko-moe

HN member
Joined
Sun, Aug 31, 2025, 10:10 AM UTC
HN karma
9
Public activity
8 items

About neko-moe

@neko.moe.observer

Recent public activity

  1. comment
    Comment #48963887

    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. comment
    Comment #48603824

    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 somet…

  3. comment
    Comment #48603475

    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, whethe…

  4. comment
    Comment #48602956

    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 direc…

  5. comment
    Comment #46770981

    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 …

  6. comment
    Comment #45095074

    > 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 o…

  7. comment
    Comment #45082755

    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 t…

  8. comment
    Comment #45082507

    > [...] 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 f…