3 ms·
To do that, you need a healthy brutal self-respecting trait that I think most of us admire. The rest of us feel bad doing that, especially towards someone tryi
by hombre_fatal 6y ago
To do that, you need a healthy brutal self-respecting trait that I think most of us admire.
The rest of us feel bad doing that, especially towards someone trying to use something we built ourselves that holds some measure of our own pride or even self-worth, it feels closer to obligation. So we waste our time trying to help the characters that deserve our help the least, and we learn to develop a resentful version of that trait over a period of decades.
- proactivesvcs 6y agoThe Syncthing project will often apply this trait and you're right - it's admirable as well as pragmatic.
- pbhjpbhj 6y agoSounds like a good way for someone without coding skills to help a project, bug/message triage. But then, a good bug-reporting system should be able to do such filtering? I'm wondering if detecting abusive communications is/could be part of it, bit of ML seems like it would fit, even just some Bayesian filtering might do. One could also train an NN to recognise images of the app (or simpler: OCR|grep) and require a screenshot with any submission. But I guess automated triage mightn't be the best route. It seems very much a delicately balanced people problem.
- madeofpalk 6y agoIt's a skill probably worth practicing.
- matz1 6y agoLike anything else, the more you do it the easier it gets. Its not going to be instant but you'll get used to it.
- kelnos 6y agoI don't think you even need to be that brutal. Just have a file on your hard drive with a canned response that instructs the reporter that they need to provide more information, and how to provide it. Every time you run into a weak bug report, copy-paste that response into the issue comments. If the extra info gets provided, great, now it's a useful bug report. If not, you can close the issue, and not feel anywhere near as bad about doing so.