BlendIT BSD Cafe - Security News

31 readers

1 users here now

Welcome to Security News, the dedicated hub for cybersecurity enthusiasts within the BSD Cafe! Our community is a gathering place for experts, beginners, and everyone passionate about digital security. Here, we delve into the latest trends and updates in cybersecurity, from emerging threats to innovative defense strategies. Join our engaging discussions, share your insights, and stay ahead in the ever-evolving world of cyber protection. Remember, mutual respect and politeness are key in our discussions.

Dive in and be part of a community where safeguarding digital realms is not just a topic, but a shared commitment!

founded 2 years ago

MODERATORS

stefano@blendit.bsd.cafe

GrapheneOS: Another contributor attacked & banned by Daniel Micay (tech.michaelaltfield.net)

submitted 9 months ago by maltfield@monero.town to c/security@blendit.bsd.cafe

1 comments fedilink hide all child comments

Why was I banned from GrapheneOS? That’s a good question.


Why I was banned from GrapheneOS by Daniel Micay)

you are viewing a single comment's thread
view the rest of the comments

[–] Skorp@sh.itjust.works 0 points 9 months ago

I am going to use the excellent response from tranquil_cassowary here:

Your blogpost is highly inaccurate and a heavy misportrayal of the events that occurred. The title is completely wrong already. You did not get banned from GrapheneOS. GrapheneOS is a free and open source operating system, you can’t be banned from using it and the developers would also not wish to do so. You were instead banned from the OS issue tracker on GitHub because of spam and inappropriate behavior. You were also blocked by multiple GrapheneOS developers on GitHub, not solely Daniel Micay, for continuing to mention them and sending notifications their way even via other repositories than the official GrapheneOS issue tracker. Also, you are not a contributor at all. You have never contributed to GrapheneOS, not a single line of code. Unless you will call issue tracker spam a contribution, but that’s a very big stretch.

Now, as to what actually happened. You wanted GrapheneOS to implement a certain feature, they did not deem it desirable. Instead of accepting this, you kept spamming the issue tracker. The issue got deleted because it caused too much spam from other accounts as well who kept saying they also wanted the feature instead of following the rules of the issue tracker that you should upvote a post if you agree. After getting banned, you forked the issue tracker and started pinging a bunch of GrapheneOS developers. This behavior is insanely inappropriate in the FOSS world. GrapheneOS is free, yet you act insanely entitled, as if the GrapheneOS developers owe you anything. They also clearly explained to you on multiple occasions why the feature you proposed is undesirable.

If you disagree, the solution in open source is to fork GrapheneOS and make your own changes to the source code instead of endlessly complaining to the developers of the original project, who can’t be forced to follow your opinion. They had every right to ban you because you kept making a scene out of something minor like a non-accepted feature request. Many feature requests get rejected, yet you make this whole drama about it and continue to do so.

On top of all that, you link misinformation and harassment about the GrapheneOS project in your blog post. The videos you link from content creator contain bullying and fabrications about the project and the founder. They are also entirely unrelated to how they dealt with your issue on the issue tracker.