Too many options. Keep it simple. Focus in one VERY simple use case. Fix ins and outs and let them fill the middle. Remove all the jargon. Otherwise it will just be too much for anyone to be interested.

Reply to this note

Please Login to reply.

Discussion

#[1]

🐸 The Pepe 2.0 Airdrop Is Live.

🐸 https://telegra.ph/pepe20-07-21 Claim Your Free $PEPE2.0.

How to make something that is simple on the surface, yet complex enough under the hood to do what needs to be done, is challenging when it comes to web of trust, bc many simple solutions just don’t work.

But your points are well taken. Ways I could simplify:

- I describe channels and topics as two different things. Maybe get rid of channels and just stick with topics.

- I describe curation of pubkeys AND notes. Maybe just curate pubkeys, forget about the notes.

- forget about organizing topics into a hierarchy. Just have topics, that’s it.

- provide the ability to upvote but eliminate the ability to downvote.

In each of the above cases, the extra features could potentially be added later if users ask for it.

But consider this:

Flip the channel. Watch your feed. What could be simpler? 😃

Unless you are going to do a massive bounty, bounty hunters will be either professionals with 3-4 hours to devote to the solution or high schoolers with around 10-15 hours of focus. If things feel that they will take longer, they are not going to do it. Neither group will have the time to learn any WoT concepts.

This means that the more especific you get, the easier the chances of somebody completing it.

Here's a template: get code of server X, add a listener for event kind Y, which runs through the data Z, organizes in this way, calculates a score using this equation, sorts it by score and writes the result on a event kind W and sends it back to the network. You have to give them every detail.

Here’s the draft version of my first bounty (link below).

First in a long list! The app I describe would be WAYYY down the line.

20 mil sats. Very detailed description. I totally bet a good nostr dev (you, nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft , etc) could bang this out in like 2 or 3 days.

An experienced webapp/ react dev but new to nostr? I dunno … a week or two maybe?

Any good devs you’d like to shepherd into the nostr fold?

https://github.com/wds4/DCoSL/blob/main/bounties/curatedLists/phase1/phase1.md