diamsa / nostrbounties Goto Github PK

With recent update changing timeout from 15 seconds to 2, Im now seeing this on nostrbounties.com when trying to view some bounties and cant update their progression status.

The home page shows a list of bounties. The purpose is supposedly to find stuff worthy my time to work on.

I want to see only bounties that

• were authored or increased by people I follow or their follows
• pay more than $x or x sats
• are still up for grabs (what's status "in progress"? Can I still beat the other guy if I'm faster and he was in progress for months now?)

and I want to see the discussion that's going on. Until nostrbounties adds conversations, how about linking to habla.news or habla.nostrbounties.com?

The e tag will change when the author changes the text. Once it does the pledged amounts by other people disappear. You can filter for the a tag instead.

Fiatjaf had supported my bounty and now "he doesn't" but it's probably a bug in the page or the original pledge. Are there any dangling pledges after fixing the naddr bug earlier?

https://nostrbounties.com/b/naddr1qq9rzdesxqmrsvfexgeqygppksv3qtdgls96jpyy4mynf064k74u7a0wmvu3yn5dwhjfraq6tcpsgqqqw4rs8z0zyv

The nostrbounties.com website is a nostr client for finding and posting bounties to nostr. To improve collaboration and compatibility with other bounty systems, it would be helpful if the structure of events were documented to avoid the need to reverse engineer/infer the structure

To satisfy this bounty,

• a markdown file should be added to the code repository for nostr bounties (https://github.com/diamsa/nostrbounties/tree/master)
• a section of the file should explain the event structure and provide sample json for a new nostr bounty, including the required tags for association
• a section of the file should explain event structure and provide sample json for adding to a nostr bounty
• an optional section can address historical/deprecated formats but this is NOT required to satisfy the bounty

Currently there is no way to enforce the original pledge of sats. Bounty hunters don't have assurances that they will be paid for their work. All hunters can do it publicly shame the bounty funder through their nostr pubkey if the bounty funder never pays. But because bounties can be created pseudonymously, and nostr keys are easy to spin up, there's no real reputational system to deter rug-pulls.

To solve that problem, an escrow system would give bounty hunters assurances that they will be paid if they put in the work and produce the product. At the PlebFi hackathon in Miami, the winning team created an escrow system that uses nostr keys for the makers, takers, and escrow agent, called Celebrity Escrow. It's a very promising system. Here's the repo: https://github.com/ArcadeLabsInc/celebrity-escrow.

That escrow system can be improved upon even further with a neutral dispute resolution panel. Instead of using a single "celebrity" escrow for resolving disputes, a panel of qualified reviewers could be used to review whether the work submitted by the hunter meets the bounty specs. I'm currently working on developing such a dispute resolution system for FOSS bounties here: https://github.com/BitResolve/Bounty-Adjudication-System.

The first step, I think, would be to integrate the escrow system to minimize funder discretion and provide bounty hunters assurances.

After that, the single escrow agent model can be replaced with a dispute resolution panel for further decentralization and due process.

Currently only 10 bounties are shown while 30 fit my vertical screen. Please make the site load another 10 whenever that button to load more is visible for more than 2s - or better go in increments of 50.

This post https://nostrbounties.com/b/naddr1qpqrwve3v56nxv3cxv6nvdeex9jrzctyvdskgcnyvcck2ce5xcekydrpvvungvf4v33njwfkvcmnjcf4vvmn2vrpxqenscnxxe3rwef4xgpzq3huhccxt6h34eupz3jeynjgjgek8lel2f4adaea0svyk94a3njdqvzqqqr4gukgahaj

has the following nddar naddr1qpqrwve3v56nxv3cxv6nvdeex9jrzctyvdskgcnyvcck2ce5xcekydrpvvungvf4v33njwfkvcmnjcf4vvmn2vrpxqenscnxxe3rwef4xgpzq3huhccxt6h34eupz3jeynjgjgek8lel2f4adaea0svyk94a3njdqvzqqqr4gukgahaj

which converts to: 30023:46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d:731e5328356791d1adcadbdf1ec463b4ac9415dc996f79a5c750a038bf6b7e52

However, the post has the following tags.

(2) ['t', 'bounty']
(2) ['title', 'Make Nostr Relay that applies limits based on proximity to a group of accounts']
(2) ['reward', '2172215']
(2) ['published_at', '1679509418']
(2) ['d', '1679509418']
(2) ['t', 'development-bounty']
(2) ['rootId', '11fbe77018024da5770f4193b3211873621827ec7635d97a0a9864274eaca372']

The d tag (1679509418) is not the same as the d tag in the naddr (731e5328356791d1adcadbdf1ec463b4ac9415dc996f79a5c750a038bf6b7e52.

It should have the following address:

naddr1qq9rzd3h8y6nqwf5xyuqygzxljlrqe027xh8sy2xtyjwfzfrxcll8afxh4hh847psjckhkxwf5psgqqqw4rsty50fx

which converts to:

30023:46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d:1679509418

bounty is described as open and toggels to In progress if clicked on it.

Make it easier to find this repo on GitHub by tagging it, please.

I tried to "mention" but none of these worked:

• npub13sx6fp3pxq5rl70x0kyfmunyzaa9pzt5utltjm0p8xqyafndv95q3saapa
• @npub13sx6fp3pxq5rl70x0kyfmunyzaa9pzt5utltjm0p8xqyafndv95q3saapa
• [name](npub13sx6fp3pxq5rl70x0kyfmunyzaa9pzt5utltjm0p8xqyafndv95q3saapa)

That last one generated a link but assumed it would be an naddr... reference I guess, under the /b/... url.

• [name](https://nostrbounties.com/profile/npub13sx6fp3pxq5rl70x0kyfmunyzaa9pzt5utltjm0p8xqyafndv95q3saapa) works but it ties the instance into the bounty.

The overview shows only original pledges and not what others committed, too.

The "share bounty" button on bounty posts leaves off the ".com" in the link produced.

For example: "https://nostrbounties/b/naddr1qq9rzd3cxsmnsdpjxc6qygxs3jf3986ucff2jqtm75heppgxpvg8vcs2trxkjg5mx83h8m7vnupsgqqqw4rsxfs3dy"

I posted a bug bounty for this one.

When I click "post bounty" after editing a bounty I get this:

https://nostrbounties.com/b/naddr1qq9rzd3ex5unjd3hxv6qygq4kh8keh6068qz729uec83jl904exgclrx503wywhelesssaf3tcpsgqqqw4rs4x5p2f

I was thinking that the current way of adding pledges with a kind:1 with just a number as the content is somewhat weird, as it makes no sense in other clients.

I think the best idea for nostrbounties.com would be to display all comments as comments -- this would allow people to say "I'm working on this" or maybe ask "what if I did x or y?" and, of course, to say "I've done what was requested, here is my deliverable".

At first it's not even necessary to build the actual commenting functionality, as that can be done on other websites, like https://habla.news/ -- but displaying them would be nice.

And then the extra pledges could be a special comment -- built automatically by the UI, that says "I pledge 500 satoshis". Just like it is today (with the special t tag and so on), but with the human-readable phrase that can show up nicely on other clients, like https://habla.news/. Then nostrbounties.com can parse the number out of these specially-formatted comments and count these.

In the future there could be a button for "submitting deliverable" in which someone who has completed the bounty can just paste a url and the UI would construct a special comment saying: "I've finished this: " -- I don't know, something like that.

I've clicked on "change status to 'paid'", but the page didn't update, only after a hard refresh it did.

If I understand correctly, when the status is "paid", I can mostly ignore the bounty if I was visiting to find some juicy bounties to work on.

Please make it easier to find attractive bounties.