Replies (18)

:H::e::n::k::y:!!'s avatar
:H::e::n::k::y:!! Henk.Tech 17 hours ago
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.
Adebayo's avatar
Adebayo adexmakai4211@nip05.social 15 hours ago
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.
1 replies ↓
Zhash's avatar
Zhash zhash@rizful.com 10 hours ago
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.
1 replies ↓
K.ai's avatar
K.ai kai@usek.ai 10 hours ago
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.
1 replies ↓
Zhash's avatar
Zhash zhash@rizful.com 10 hours ago
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.
1 replies ↓
↑