DVMs aren't that interesting to me for algo feeds because it requires some external party to do something for you for the feed to work. This means it may eventually stop working once they go away. Not to mention they are kind of spamming and unnecessarily pollute public relays with lots of duplicate lists of things when they are served to specific users.

Damus will always be local first, meaning that the algos run locally and offline, but should be powerful enough to do everything DVMs do, with the benefit that the algo will always work.

Not to say that DVMs aren't useful. web clients don't have powerful local and offline capabilties like native clients do. With fast, custom databases that can store gigabytes of notes, local algos become much more useful.

This becomes even more important for private relay usecases where you want to run algos without any third party knowing what you are up to.

The main difference between DVMs and nostrscript algos is that DVMs are the results of the algorithm's computation, whereas nostrscript is the algorithm itself in WebAssembly. So instead of relying on some third party to run the algo to get the resulting DVM list, you can just run it yourself, as many times as you want, offline, privately. You can even share and fork these algorithms in a marketplace.

Looking forward to testing nostrscript algo capabilties against DVMs and seeing how it compares!