Ryan Barrett
Ryan Barrett
The one related NIP is https://nips.nostr.com/72, but that's for communities with admins that proactively moderate them, which isn't what we're thinking about here.
Hey, thanks! I like that idea a lot, definitely makes sense. Having said that, I don't have a clear sense of how we'd actually do this with the current code....
This applies to Nostr too. [email protected], [email protected], and even a.b.c.d (technically [email protected]) are all valid, distinct NIP-05s, and we convert them all to the same Bluesky handle, a.b.c.d.nostr.brid.gy. Worse, this...
Will be harder to do after we launch, so we should probably do it before.
Should try this again now that I've overhauled our user id vs profile id handling.
Most of these lists have semi-permanent URLs that stay the same across updates, ~but not all. DNI, for example, seems to be year/month based. I may ask Jaz if he...
We'll probably also want to show the lists you're blocking, both fediverse domain blocklists and maybe Bluesky blocklists too (?), on the settings web UI and via DM.
Also, this might give us one way to do #1672, we'd just store each user's personal list of domain blocks in a custom `Object`'s `csv`.
Trying to think through the logic here more, and I realized/discovered that blocking itself isn't well-defined on the fediverse, ie there's no single, authoritative, comprehensive spec for how blocking should...
Given a user who's blocking a given domain, we can definitely start with: * block authorized fetches for any of the user's objects signed by the blocked domain * don't...