This sounds similar to the once per follow DVM. I look forward to your local first implementation.

Reply to this note

Please Login to reply.

Discussion

Bingo

can't imagine using a DVM for something like this, seems so hacky.

this is just local code for filtering a list you already have. the idea of spamming the network with lists of list notes for every single person who wants this modified view for every single one of their lists is insane to me.

you can block npub locally ๐Ÿ˜‰

not what im referring to.

X people

Y feeds

Size of feeds can be like 100kb

X = 50,000 people

Y = 10 feeds

50,000 * 10 * 100KiB = *50 GB* of DVM spam

vs

0 bytes if you just do this locally. Pushing outputs of algorithms for every single person into the network is just a bad idea

Not to mention it will just break and stop working eventually, is not decentralized, doesnโ€™t work offline, is hacky. I will never understand why all the clients are implementing this as their algo marketplace solution

DVM feeds should be ephemeral events on only the service relay. More like a web service.

I am a local-first maxi you know, but maybe not everything can be produced client side

The one per follow DVM is also super slow for what it does (a simple dedupe)

i too am an enjoyoor of once per follow dvm ๐ŸŽ