• tranquil_cassowary@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    3
    ·
    6 days ago

    Your blogpost is highly inaccurate and a heavy misportrayal of the events that occured. 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 inapprioriate 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 inapprioriate 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 undiserable.

    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 containg 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.

  • AlexTECPlayz@techhub.social
    link
    fedilink
    arrow-up
    11
    ·
    6 days ago

    @maltfield Here we go again, another nothing-burger that doesn’t surprise me at all. I love the project, but Daniel just seems insufferable from his comments in that thread, and other, older, comments.

    With all respect to him and the project, but if something as simple, as miniscule, very little drama-worthy such as a thread asking for a simple gesture feature causes him to “lose an hour of [his] work” and to make him worry about more attacks on the project, it just indicates bigger problems than just a simple focus loss due to some small issue that gained virtually ZERO interactions besides a total of four people, including Daniel and the community mod.

    I get GOS has been harassed by other projects, but even mentioning a ‘competing’ ROM such as /e/OS or CalyxOS counts as bad behaviour and inciting harassment and this and that, it’s obviously not a good look.

    • wildbus8979@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      7
      ·
      6 days ago

      He was behaving like that back in the Copperhead days. He stole work he didn’t understand from Spender and publically harassed him to the point where Spender/GRsecurity pulled the plug on their public kernel patches. Huge loss for the Linux community.

      • Skorp@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        2
        ·
        edit-2
        6 days ago

        This is a blatant and complete fabrication that you are spreading. The project is on good terms with Spender and you have no evidence to support what you are claiming.

        It was after GRsecurity became private that they had an issue with people making upstream security contributions, particularly upstreaming anything from the GRsecurity patches. They had disagreements about that, and then moved past it and are on good terms now.

        It’s absolutely ridiculous to claim that Micay has anything to do with them making things private.

        https://grsecurity.net/announce https://news.ycombinator.com/item?id=10126319

        It was Wind River, owned by Intel, which was the main offender for upstreaming the patches. Micay was the one who introduced GRsecurity in Arch Linux and did all the integration it had for PaX exceptions and the start of RBAC support (systemd was an issue at the time). It was afterwards once it became private that it was awkward because they didn’t want people upstreaming or maintaining ports of their work but at the time Micay was maintaining GRsecurity in Arch Linux and GrapheneOS (then called CopperheadOS) was using the PaX subset for kernel hardening, so there were existing uses of it to try to keep going in some way.

    • AlexTECPlayz@techhub.social
      link
      fedilink
      arrow-up
      5
      ·
      6 days ago

      @maltfield Here’s another example of I’m guessing Daniel, being an asswipe towards someone that had a genuine concern with the ‘apocalyptic’ way GrapheneOS tends to exaggerate their messages. It’s clear from that sentence that “the final version of GrapheneOS” is not intended to be referring to some 24-hour support or whatever they tried to explain later in the thread.

      https://mstdn.io/@eskuero/114824540277758406

      Notice the loaded words in the thread, “extreme”, “misrepresenting”, “lying”, and so on. That user wasn’t fucking lying or misrepresenting, they were genuinely concerned after reading that stupidly-written message on their Matrix.

      There’s a boatload of threads like these where the GOS account jumps to people’s throats with a knife for the smallest things.

      Write something that may not be entirely true, perhaps you’ve heard some rumor or whatever somewhere and just want to get official news? Oops, you’re lying, you’re extremely misrepresenting what we wrote, please don’t ever interact with us again, we’ll ban you, etc.

    • exu@feditown.com
      link
      fedilink
      English
      arrow-up
      2
      ·
      6 days ago

      From when I last checked on that topic I couldn’t find much beyond claims by Daniel that other projects had harassed him.

  • Speiser0@feddit.org
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    8
    ·
    6 days ago

    Yeah, I don’t think I want to believe the person (you, OP, the banned one) who makes drama like this. Who the fuck, after being banned, makes a poster like this against the project they were banned from, and posts it on social media (i.e. here on lemmy)? Someone who shouldn’t have been banned? Where does the hatred come from?

    Idk what your previous interactions with the GrapheneOS was. While the stuff you posted on your website makes the maintainers of GrapheneOS look harsh, it’s just your side. Do I now want the GrapheneOS maintainers to display their side, so the internet judges can make their decision if GrapheneOS is to be canceled? No, I don’t. I don’t see anything wrong in them deciding to ban someone who apparently behaved inappropriately. It looks like your ban reason was something like spreading misinformation, which is a valid ban reason imo.

    You said you couldn’t get in contact with the maintainers, but here they clearly show an e-mail address, as well as other communication channels: https://grapheneos.org/contact

    This is an important security feature for a user who is playing with a new app. Sometimes a fat-finger mistake or a misbehaving app may begin to do something undesired (eg exfiltrating data by mistake), and it’s necessary for the user to quickly kill the app.

    The above process takes a long time, and is probably not fast enough to kill an app that, for example, is sending an unwanted POST request. By adding this feature, the time to kill the app could be reduced to ~1 second.

    It’s not a security feature and this is not a real world scenario.

    Why would you have an application installed that if you start it, it does malicious stuff? Also “kill it fast before it does bad things” sounds kinda absurd to me.

    Anyway, idk if there’s something wrong with GrapheneOS. I didn’t look too much into this stuff. All I want to say is, this kind drama, coming from the banned person themselves, does not play in favor of your case. You should’ve made your blog post as drama-free as possible, shortly naming the reason that was given to you, why you were banned, state why you find it unfair, and move on, not ask the reader “Why was I banned? Please read this 20 pages of drama text.”, and not accuse anyone of anything that you can’t prove.

    Now, the question is: What the heck is wrong with me? I have nothing to do with this. Why am I writing this long comment? Who am I feeding?