But if you’re thinking of building such a “paid algo” service … I wanna know what you think of a NIP standard for subscribing to such an algo. How wd that work?
nostr:note1q2a2stds7ndxe9h9xz82u20szgur0yyp2gmdkz853dvdvl66stqsgj6awd
Discussion
Will take a read.
My primitive understanding is that if DVMs can return something (e.g. text, or an image) DVMs can also return if an image contains a certain thing or not (e.g. a cat).
I would thus pay a DVM to screen all images and expect an answer if an image contains the thing or not.
Right. This same challenge will be encountered by clients and relays as well. All three architectures currently have active development in this space.
How to filter for desired content?
IMHO, framing this as a DVM challenge will only contribute to fractured solutions. So, there’s that.
And otherwise… honestly… if users have free choice and the tools to choose … let the market decide what works and what doesn’t.
So my answer is a question:
What wd we build if we were to let users subscribe to (and share) content filters, delivered by any vendor, and applicable across all clients?