Thread

DVM Algo's + Custom Feeds = ๐Ÿ”ฅ Had to quickly prototype this to see how all these pieces could fit together and how to not make it a UX nightmare. ๐Ÿ‘‰ Some Algorithms will need a specific input (profile list, setting) and some will not. That's why that's selected first. ๐Ÿ‘‰ Proposed DVM's need to filtered (f.e. using NIP-31) I like that this is (hopefully) where the complexity would stop for the app, since the DVM's take over from there. #nostrdesign #customfeeds #dvm #dvms #feed

Replies (5)

Love this! I was kinda hoping you would take the mantle in making this graphical when I wrote my note about this yesterday! A few notes: "Proposed DVM's need to filtered" should refer to NIP-89 instead of 31. DVMs should announce themselves with NIP-89 which allows them to give a specific "sales pitch" on why a user might choose to use that DVM for each particular use case. Here's an example of what it would look like in Highlighter: image The NIP-89 can provide anything a typical profile has: * avatar * name * about For nostr content discovery probably I wouldn't add parameter support, as the vast majority of DVMs of this kind won't require them and it makes the UX much more complex. Nostr content discovery DVMs that require a parameter are probably better left to more advanced/nice UIs.
Cool, similar to how I imagined it could work. Could be a good time to take a look at implementing and with other algos like: DVMs I think will be useful for search and discovery outside follow graphs, or a very wide view of a follow graph and/or relay list.