Amethysts bug bounty thing rubbed me the wrong way. Report not submitted, back to Ditto.
If there is a bug so blatant that it ruins the experience for everyone there shouldn't be a need to pay to report it through the proper channel. That just means I either have to pay or me submitting it without that means the bug won't be fixed even if it effects everyone.
Because your right, I don't care if its fixed or not, this was about the quality of your app I was helping with to notify you of the issue. I'm fine sticking to other desktop clients until its fixed.
What bug you ask? I don't need to tell you. You will hear it from every other user this impacts. And if its only me who triggers this within a minute and my usual skill of breaking things? Well then I don't need you to waste your time fixing it for just me, I'm fine using something else that already works even if I really like the client.
I 100% get that if I wanted some obscure thing fixed or implemented that i'd have to pay for that effort. But you should really add a clarification that these bounties are optional for major bugs because now you simply won't know.
Login to reply
Replies (10)
They have the same thing for adding a feature request, which is fine but asking a bounty for submitting a bug doesn't make sense. Maybe it just copied the template everywhere and it wasn't done on purpose.
I don't exactly want to jump on the bandwagon either way. Personally, I basically don't accept issue submissions. I encourage people to tag me on nostr or email (which will likely be taken down when I get enough spam), nearly all PRs or issues are generated by llms at this point automatically or human directed but theyre usually garbage and a waste of time. I think public GitHub issues and PRs on by default is largely a mistake. Im very glad GitHub gave maintainers the option to disable them.
Most of nostr has attempted to be pay to reduce spam over the past few years. Now I'm not sure the reasons @Vitor Pamplona implemented this, but I would mostly assume a way to 1) help fund the project, and 2) dramatically reduce spam issues.
Maintainers were grateful for user reports, but we've crossed a line at the moment where spam is too cheap to generate so only larger teams with larger funding have the resources to help mitigate spam.
Also we're all glad to have users here, but if this note was seen 1-2 years ago there is a good chance your replies would have been filled with a bunch of GFYs at "Report not submitted, back to Ditto."
We've calmed down significantly as people have left over the years XD
The template just tells the author to add a bounty for anyone that fixes the issue.
The template just tells the author to add a bounty for anyone that fixes the issue.
The template just tells the author to add a bounty for anyone that fixes the issue. It's not asking you to pay to post... You didn't even read it.
@:H::e::n::k::y:!! are you talking about the GitHub issue template?
> **Bounty (in Bitcoin sats) offered for a solution**
The size of the bounty is proportional to how much this matters to you. If no bounty is offered,
not even a small one, this bug will not be worked on because it doesn't matter to you. We prioritize
bug fixing to issues that have bounties, even small ones.
The grammar is wrong on it. It needs to be worded better, that's why henky was confused.
how would you word it? It has been working for 5 years.. so I am not sure what's so difficult to understand.
The bounty wording makes sense for feature requests, but not for bug reports.
Right now, the bug report form says that if someone doesn't offer a bounty, their bug won't be fixed. That makes it sound like users are required to pay developers to fix problems.
I didn't notice for 5 years because I've never submitted a bug report.
Something like this.
**Bounty (in Bitcoin sats) offered for a solution**
The size of the bounty is proportional to how much this matters to you. If no bounty is offered, the bug will still be worked on based on its severity and impact. We prioritize fixing serious bugs regardless of bounties, while bounties, even small ones, can help prioritize less critical issues.
Although that is still too complicated. When I read it on the feature request I had to think about what it meant.
Why not something like:
"Optional reward for contributors. The amount in sats you're willing to offer to see this feature or bug fix. Setting a bounty offers a reward to maintainers and contributors as an incentive to prioritize your request. It helps reduce nonsense and help maintainers know what is most important to users."