Subnostr

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:

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.

PABLOF7z 2y ago

Also, fwiw, as a user, I think this is too complex of a flow. I would just show the DVMs on the first dropdown afer the list of feeds the user created so there it would list stuff like the "What you missed DVM", perhaps filtered by the DVMs my follows are using or something like that.

Reply to this note

Please Login to reply.

Discussion

Niel Liesmons 2y ago

For most feeds (highlights, notes, articles, even DVM's) it can completely be a dropdown on top of the feed.

But here I'm combining several feeds for a more modular set up in an Amethyst-like app.