manime on Nostr: The problem with pushing custom REQ filters to the DVM marketplace is that relays ...
The problem with pushing custom REQ filters to the DVM marketplace is that relays will become obsolete.
Once this feature is mature, and nostr adoption grows, user customizable content feeds will be what sets nostr apart and keeps REAL user content visible.
Because the threat model from bots and bad actors will be always changing, end users will want to stay on top with the BEST content filters. They will benefit from sharing filters with each other, independent of the client used. If this functionality (to share prepackaged filters) is only available through DVMs, then nostr event traffic will gradually flow more amen more through these DVMs.
In addition, NIP90 for DVMs specifies an event to be published for EVERY request AND response. I kinda think this is overkill for the task at hand.
Just single event to publish the “filtering service offered” by a relay and another event to “subscribe” to that filter. This is the NIP needed. IMHO
Once this feature is mature, and nostr adoption grows, user customizable content feeds will be what sets nostr apart and keeps REAL user content visible.
Because the threat model from bots and bad actors will be always changing, end users will want to stay on top with the BEST content filters. They will benefit from sharing filters with each other, independent of the client used. If this functionality (to share prepackaged filters) is only available through DVMs, then nostr event traffic will gradually flow more amen more through these DVMs.
In addition, NIP90 for DVMs specifies an event to be published for EVERY request AND response. I kinda think this is overkill for the task at hand.
Just single event to publish the “filtering service offered” by a relay and another event to “subscribe” to that filter. This is the NIP needed. IMHO
quoting note1aej…rf85I’m crazy for WoT!!
What’s the solution for having PUBLISHED content filters that end users could subscribe to?
Use case:
“I love my feed. No spam at all, AND I get suggestions for new follows that I actually like! Checkout these WoT filters...”
I’m thinking:
- a WoT filter event that references a relay’s API endpoint and some metadata.
- a WoT subscribe event that references one of these filter events.
- DVM integration?
Also:
- a NIP for WoT actually is kinda exciting.
hodlbod (npub1jlr…ynqn) Vitor Pamplona (npub1gcx…nj5z) PABLOF7z (npub1l2v…ajft) brugeman (npub1xdt…ntxy) Mazin (npub18kz…x5sz) Rabble (npub1wmr…g240) Gigi ⚡🧡 (npub1der…xzpc)
(Sorry for the hell thread, but i don’t know how to get early feedback before making an even bigger fool of myself with a PR.)