We can’t spell BUGS without U, especially in Open Source culture 🐞🙇🏽… here’s the latest update on the #Nostropical Hackathon’s Community Voting winner.

Because we conducted the vote transparently on Nostr some users were able to check our work and found different results for the winner. After triple-checking with community members, we indeed found & regret an error in our initial tabulation and announced the winner of the Community Vote. See the image below for the updated correct tabulation.

As noted here…

https://iris.to/note1gct35x084r3l5elv0xyr88v6qc0mn2shcxyyaqdsdngl9h5fa2cqyrgtx6

… it was a neck-and-neck two-way race between:

NostrFollower by #[0]

and Incognito by #[1] #[2] & #[3]

We want to make this right for both teams. So we *added* a Community Vote prize award for 2nd place!

Here’s the correct tabulation for the Community Vote:

1st Place: Incognito - 25,000,000 sats

2nd Place: NostrFollower - 12,500,000 sats

We are sorry for the error, and we are very grateful to this open transparent software culture!

Congrats to both 1st and 2nd place award Community Vote winners!

Reply to this note

Please Login to reply.

Discussion

Thanks so much! This is amazing. We’ve kept going with the project and are actively working on a NIP as well as a library for making it easy to add incognito messages to clients.

Separately we’re building a demo client for people to test out incognito messages!

Here’s a link to our NIP-31: https://github.com/nostr-protocol/nips/pull/410

We won the community vote for the #nostropical hackathon which happened after #nostrica. Thanks for the support everyone!

#[2]

Our work on incognito (private) DMs continues!

Congrats 🎉

Congrats to the Incognito team, your project really is pretty cool.

Also thanks to nos for the second prize, really appreciate it.

Cheers! Congratulations to you as well 🤙

hm ok, this was supposed to be a reply to #[3]. I either misunderstood the gossip UI or it was a bug.

So yeah, the U in BUGS is me. Just wanted to personally apologize for the error. It was a really stupid error and I several lessons about how to do this better in the future. For anyone who is curious, the specific bug is that I counted votes as "kind 7 events where any etag references this note" when it should have been "kind 7 events where *the last* etag references this note". The script I used to calculate the events is published here for auditing and in case anyone else wants to try a voting process like this in the future.

github.com/mplorentz/nostr-voting-tools

In a weird way though I think this is a great example of how transparency and open systems are superior. We decided to do our community vote in the open on Nostr which hadn't been done before. Because the data was public nobody had to take our word for it and it let to the correct outcome in the end. I will be much more careful next time sats are on the line, but I'm going to keep dogfooding and learning at the bleeding edge of what Nostr can do! Thank you for being gracious #[1].

Thank you for all the transparency and working through this. It’s a tricky situation and I think you handled it very well so kudos to you and the team 🤙🫡

The U is also those who noticed different results to help us squash the bug so it’s really more of a WE… but BWEGS doesn’t ring as well as BUGS 😆