Do you ever get scared of being eating up by a community for reporting problems.

Have you ever been scared or hesitant about reporting flaws or bugs to a community with a strong staunch fanbase ??

Obviously there are different ways of reporting and starting discussions, but I brought up the courage to report a flaw on a subreddit (not to be named) that I knew is very sensitive to criticisme, and I was flooded with downvotes and even was subject to gaslighting, so I gave up on that software and became even more hesitant about reporting problems on other FOSS communities .

Is this mindset very prevalent among all open source communities? have you faced something similar ?

You're viewing a single thread.

35 comments

Do it anyway and ignore the backlash. If no one reports it then it will never be addressed. Its the drawing of attention to the matter that counts in my opinion.
The only complaint I have is that most communities or devs prefer you to open issues on places such as github instead but I feel it doesnt really matter since not everyone is willing to take the extra steps.
- As a software developer, this is constructive:
  open issues on places such as github
  This is removed:
  it doesnt really matter since not everyone is willing to take the extra steps.
- I try to post issues on github , but because I always have to verify my sign-up using email 2auth. It grinds my gears that reporting bugs is becoming tedious.
  I tried to open an account on codeberg.org to report a small issue, the website refused to let me sign-up with a temporary email (I understand they have to fight spam), I don't like using my own email everywhere so its another disappointement on my list.
  
  Protonmail accounts are free. Just make one and use it for bug report signups.
  
  And if you have a paid Proton account, you get SimpleLogin included, so you can use a unique email address for every service. I love that - I now generally have a unique username, password, and email address for every service.
  
  Good idea!
  
  Ran into the same problem as you. Did not feel like making my 273828rd email and ended up not reporting a bug.
  
  Firefox Relay, Proton email aliases, and whatever iCloud's email thing is called all allow you to hide your email. The free versions tend to limit how many you can create, but some let you pay for unlimited. I use a different alias for every single thing I sign up for (i personally use Firefox Relay and only ran into an issue once during a sign up). Since I also pay for Proton Mail though, I can get other aliases through there if need be. Basically the very free things will turn you into a customer, so if you want to keep privacy, paying for the basic protections isn't super expensive.
  
  Why not just make a secondary 'real' email account that you use exclusively for signing up for things? Gets around those problems and gives you a way to retrieve recovery emails if you ever actually need to.
  
  the problem is not the email per se, as I have 2 or 3, but having to open up my email and retrieve the 2auth code each time I sign-in to github to post an issue. my browser is set to autodelete cookies when closed. that's my petpeev. and unfortunaly most projects are hosted on github.
  but in the day it was easier to report an issue straight on the devs websites; very fast and straight forward. times changes
  
  I mean, that sounds like extreme laziness. You're complaining about opening an email (or you could setup an authenticator app). Literally just opening an email is too difficult for you to do and prevents you from telling some other devs about some work you think they should do. I'm being slightly facetious, but you are basically creating work for the devs. The least you can do is open your email. I imagine it's software they made that you're probably using for free. Is it so much to ask for? If it bothers you so much, get a hardware key. Bonus if it's NFC capable so it can work on your phone too. But seriously. This just sounds so entitled at this point. I don't care that your cookies autodelete. You can open your email. Hell, get the email on your phone even. I don't care. This isn't a problem that someone should really be having issues with. It's a minor inconvenience.
  
  I hear what you are saying.
  but did you ever consider how github could be a stop gate to many many tech illeterate people, who don't know how to post an issue or report a bug using github, having to sign-up to website they might never use again, figure up how to fill-in the ever so eleborate issue forms, and have to activate 2FA everytime they want to comment on the issue weeks after it has been posted. that's why you see many project subreddits are full with bug reports and help requests. its easiers for the commons.
  Git technology is def a godsend for developpers but could also be a barrier to less techy people how don't know how to report, or if it is a problem in the software or something they are doing wrong. that's why I think we need to be more welcoming and less standoffish to people with less know how.
  Maybe having a simple form on the project website that can mirror the bug reports to github is oneway to provide people with an easier solution to give feedback that they might not give otherwise.
  
  I guess at the end of the day you'd have to decide for yourself whether you'd prefer submitting bugs to a social media spot (if the project has one), which is a lot more open to drama from others than on GitHub (which is not to say that drama doesn't happen on Git[Hub/Lab/etc]).
  Maybe having a simple form on the project website that can mirror the bug reports to github is oneway to provide people with an easier solution to give feedback that they might not give otherwise.
  A couple of issues with this:
  It'd be easier to spam / fill with junk, and would require either a custom solution that every project would have to reinvent the wheel on, or another centralized service that acts as the "gatekeeper" to spam... in which you just have the GitHub issue all over again
  This method doesn't give developers an easy way to respond/follow-up on the report. It is very common for "bug reports" to not actually contain enough information on how to reproduce the problem unfortunately. You could say, add a field for an email address (which would need to be filtered out before posting to Git and stored somewhere / tied to the issue that gets opened) but I think most people would be against giving every single individual project their email address than GitLab/GitHub/etc. Additionally if we're focusing on tech illiterate people as you mentioned, its unlikely they'd even respond to a follow-up email.
  
  No, most projects have a support email. I rarely see them not include that.
  
  So you delete your cookies and then complain that you have to login again and again?

35 comments