I’m not a GrapheneOS developer, nor part of the GrapheneOS team, I’m a GrapheneOS user and community member. I can’t go ship code. Agreed that open source development is a difficult work environment due to some people feeling heavily entitled and those people being very vocal. As to for the actual GrapheneOS team, they would love to waste less time with responding to attacks and false information. However, it’s a very normal, human response to not want misinformation about yourself and your project to thrive all across the internet. This also can hurt the project in many ways, it’s not an ego thing.
Look I have no idea about all of the community drama and I don’t care if you are a community member of the leading dev. I’m shipping code every day and if someone talks shit, let them talk, I literally don’t have time for it because I’m busy shipping code. So if you just code and not react, what are those vocal people gonna do about it? Jump out of their screens and beat you up irl?
I think you underestimate the burden of misinformation being spread about you and your passion project online, and having a KiwiFarms thread about you on the internet. The harassment also has a real life impact because the founder has been swatted multiple times, endangering their lifes. So they can sadly do much more harm than just being a keyboard warrior. And besides that, it also has an impact on cooperation the project can do with other organisations and companies. GrapheneOS has asked whether other organisaties would want to share their Android partner access with them and they got replies stating that they would want to share the partner access but will refrain from sharing it becuase they were scared that if people found out they helped that they would also get harassed. Also, GrapheneOS had tried for many years to get a cooperation with a non-Google OEM to support other hardware than just Pixels and the harassment has also been an issue for things like that in the past. Luckily, GrapheneOS is currently in active talks with an OEM though who hasn’t taken any issue with it, so let’s hope for the best.
I’m not a GrapheneOS developer, nor part of the GrapheneOS team, I’m a GrapheneOS user and community member. I can’t go ship code. Agreed that open source development is a difficult work environment due to some people feeling heavily entitled and those people being very vocal. As to for the actual GrapheneOS team, they would love to waste less time with responding to attacks and false information. However, it’s a very normal, human response to not want misinformation about yourself and your project to thrive all across the internet. This also can hurt the project in many ways, it’s not an ego thing.
Look I have no idea about all of the community drama and I don’t care if you are a community member of the leading dev. I’m shipping code every day and if someone talks shit, let them talk, I literally don’t have time for it because I’m busy shipping code. So if you just code and not react, what are those vocal people gonna do about it? Jump out of their screens and beat you up irl?
I think you underestimate the burden of misinformation being spread about you and your passion project online, and having a KiwiFarms thread about you on the internet. The harassment also has a real life impact because the founder has been swatted multiple times, endangering their lifes. So they can sadly do much more harm than just being a keyboard warrior. And besides that, it also has an impact on cooperation the project can do with other organisations and companies. GrapheneOS has asked whether other organisaties would want to share their Android partner access with them and they got replies stating that they would want to share the partner access but will refrain from sharing it becuase they were scared that if people found out they helped that they would also get harassed. Also, GrapheneOS had tried for many years to get a cooperation with a non-Google OEM to support other hardware than just Pixels and the harassment has also been an issue for things like that in the past. Luckily, GrapheneOS is currently in active talks with an OEM though who hasn’t taken any issue with it, so let’s hope for the best.