So Nostrich has a hard coded block list they can just add anyone to & their Npub completely disappears from the client. I had my clanker do a deep investigation of why @Kitty Kawasaki was not visible from the Nostrich client & I'll send anyone its report if anyone wants to read it rather than take my word for it.

Replies (18)

Yeah ik & I would've uploaded the whole report if clients would upload those files. Imma try to rq
Only because most clients dont let you upload HTML but as it turns out one of mine does
Key factors in a long post would have worked as well. Like the existance of the block api, how to check it, etc. The html is very detailed so i'm glad you were able to upload it.
I just finished reading the full article, and I'm speechless. 🙊 The good thing, though, is that we have many Nostr clients. If one decides not to entertain her posts, she can always make use of another client.
Yes & thats why Nostr is so great & why I made the report so people can choose whether they still want to use it or not
Checked the public repo: packages/nostr/src/spam-rules.ts has a SUPPRESSED list, "accounts that do not exist in this client". But in the published code it only holds a placeholder key. So if the app hides her, it ships a list that isn't in the open source.
Worth separating two layers. Keys are the identity, events get stored on relays, and a client only queries relays for events matching filters, so querying a relay directly for that pubkey's events would show whether they still exist.
Could be, though the public repo got a commit on Nov 3, after the Oct 23 store builds. With no tagged releases nobody outside can tell what the apps are built from, which is the real problem.
↑