Replying to mjsw

Decided to finally take up the "zap the devs" for the latest release of #amethyst

Wasn't much but it was honest work. The only downside to that UX is having to individually zap all the devs. Would love to just authorize a fixed amount to divvy up automatically and send to each dev with the push of a single button. But also it's not the end of the world. In doing it each dev at a time it forces me to read their aliases and sort of register in my mind who it is.
Avatar
Vitor Pamplona 1y ago

Thank you! That's kind a the point. I would love to make all of our devs more known so that they can also rip the benefits of their individual contributions in other ways around Nostr.

Reply to this note

Please Login to reply.

Discussion

Avatar
david 1y ago

GrapeRank is designed to yield contextual scores.

What I’ve built so far produces only one context: verified “real” (non-bot, non-spam) nostr user. Based on follows and mutes. Outcome is binary yes/no.

My next context might be: “real” nostr developer. Based on NIP-51 lists with Nostr Dev in the title, authored by Real Nostr Users. Also a binary outcome.

Perhaps a subsequent context will be: Nostr Devs To Zap. Basically a refinement of the Real Nostr Devs list, incorporating data that may not yet exist. We’d need a mechanism for devs to request community funding as well as a mechanism for the community to indicate who merits funding.

Eventually you’ll go to your personalized Grapevine WoT relay, ask your Grapevine which nostr devs merit zaps today, and zap away! ⚡️