GrapheneOSGrapheneOS started in 2014 and was originally named CopperheadOS. In late 2015, the Copperhead company was founded which was meant to support the project. Copperhead didn't create CopperheadOS and didn't own or control it. Copperhead made a failed takeover attempt on it in 2018.
GrapheneOS still has the original CopperheadOS repositories on GitHub. Copperhead seized a bunch of the project's infrastructure and accounts. They created a closed source fork of GrapheneOS called CopperheadOS after the split which was not the same CopperheadOS as the original.
Copperhead remained entirely dependent on GrapheneOS and had to keep forking our code for each major Android update. Despite depending on GrapheneOS, they waged a war against it trying to destroy the project and attempting to ruin the lives of our team, especially our founder.
Copperhead heavily pushed the false narrative that they created the project and that we created a fork in 2018 which absolutely isn't true. Their claims fell apart in their legal attacks on GrapheneOS and we wiped out their closed source fork by forbidding them using our code.
Copperhead heavily edited Wikipedia to push their false narrative. It's why there's a huge article on CopperheadOS presenting it as a separate product when it wasn't one and an inaccurate history in the GrapheneOS article. False narratives about our team are still there too.
Copperhead published a bunch of press releases and did interviews pushing their false narrative. Many companies including Twitter defaulted to taking the word of a tiny corporation falsely claiming credit for our work over us. We've yet to receive back our stolen Twitter account.
Copperhead made the attacks personal and targeted the founder of GrapheneOS with fabricated stories and vile personal attacks. Henry Fisher (Techlore) collaborated with Copperhead to make it into widespread harassment. Others opportunistically took advantage of the situation.
Nicolas Merrill took advantage of the situation. He hired a Copperhead employee involved in the takeover to create CalyxOS. CalyxOS heavily used our code and documentation. It was promoted by attacking us and portraying themselves as being above the situation with Copperhead.
Nicolas Merrill burned down Calyx and CalyxOS on his way out. Nick was secretly working on a for-profit company to replace Calyx. He used Calyx resources for his personal benefit and was pushed out. Louis Rossmann is one of 3 co-founders of the company:
https://www.sec.gov/Archives/edgar/data/2009536/000200953624000001/xslFormDX01/primary_doc.xml
No one should believe the false narratives peddled by these people. They've always been in it for personal benefit and have caused immense harm to actual efforts to improve privacy and security. We're willing to forgive people who were duped by their fabrications, just reach out.
We're offering forgiveness to people who have engaged in years of libel/harassment towards us if they take down their attacks, debunk it and help repair the harm caused to us. This offer even extends to Henry Fisher and Louis Rossmann. Alternatively, we can address it in court.
Kuro@GrapheneOS just out of curiosity, what has happened between Louis Rossman and GrapheneOS?
@kuro Rossmann was brainwashed by the attacks on GrapheneOS by Copperhead and Henry Fisher (Techlore). He was being hostile towards the founder of the project for many months including actively supporting the attacks with jabs in chat rooms and his content. Rossmann expected us to be super grateful to him for covering GrapheneOS and to make content with him. After the swatting attacks in April 2023, our founder got upset with him in private and Rossmann decided to try to destroy his life.
@kuro Rossmann began trolling in a private direct message denying all knowledge of what had happened and deliberately misrepresenting what was being said. He began live streaming the private chat to his followers while delighting in tormenting someone who had just been repeatedly swatted. Later that day he published his video to cause as much harm as he could to our founder and to GrapheneOS. He pushes a bunch of fabrications and misrepresentations in the video including to justify him doing it.
@kuro He pretended he was scared to keep using GrapheneOS because a developer was upset with his support for personal attacks. In reality, his own followers figured out he continued using GrapheneOS for many months afterwards as his daily driver due to repeatedly leaking that he was using it in his videos without realizing it. He pretended he was scared of us replying to his attacks as if our tiny audience compared to his made him scared. These were lies to justify the horrific thing he did.
@GrapheneOS from time to time I have seen videos from him but never anything regarding Graphene. Very disturbing to hear that about him but seems on par with his character
@GrapheneOS that sounds awfull. Sad to see him do such things.
Claudius Link@GrapheneOS
Thank you for this background information 🙏🏻💜
Thank you for this background information 🙏🏻💜
Centi Quetzal@GrapheneOS This has been going on for a while, and i really hope it can heal. Privacy projects share a mission that is always bigger than individual agendas. Let's fight together so that this situation isnt a "divide and conquer" that ends up benefitting surveillance capitalism. Jonah from Privacy guides recently posted about this.
Draken BlackKnight@centiquetzal @[email protected]
Sadly this is the dev team gaslighting everyone still following them. It's usually GrapheneOS's dev team starting the harassment campaigns.
Sadly this is the dev team gaslighting everyone still following them. It's usually GrapheneOS's dev team starting the harassment campaigns.
Xtreix@draken @centiquetzal There is no evidence to support that claim, and plenty of evidence contradicts your statements, you are wrong.
@Xtreix @centiquetzal
Is THAT why Louis Rossmann has screenshots?!?!? And here I thought it was because I was right!
Is THAT why Louis Rossmann has screenshots?!?!? And here I thought it was because I was right!
hristogochev@GrapheneOS Although I will probably not find a better OS, there is an issue with the project in the Forums and Discord where anyone asking to gain deeper knowledge about the OS relating a privacy concern (e.g. the WebCam service) is told to just blindly trust the OS instead of being actually explained what is going on on a deeper level. Either he is told that or his posts deleted and labeled as FUD, even though he is simply asking a question, not criticizing the OS in any way.
FNT_SMGLLR@hristogochev @GrapheneOS What was the issue with the webcam service about? This is the first time I've heard about this, somebody catch me up to speed.
@GrapheneOS
Counteroffer: How about you apologize to everyone you have snapped at and then gaslit everyone else into thinking you were the ones who were wronged?
Exhibit A: Me. I asked a simple question and you started going off about how I was trying to dox Micay (false), working for Copperhead and Techlore (false; I was heavily involved in the dev community on XDA at the time), and spreading lies (this one's true but as retaliation to the aforementioned).
I'm willing to talk if you are.
RCSM@GrapheneOS please just drop it and make a better product moving forward that stands on its own. There's not enough usable alternative phone OS's out there to get tied up in a court battle.
@RCSM Henry Fisher and Louis Rossmann need to stop directing harassment towards our team. If they aren't going to do that, then the situation needs to be resolved another way. The level of harassment directed towards us isn't tolerable and the status quo cannot stand. We're absolutely not going to continue living under siege from these people directing hate towards us. There are daily raids because of it across our platforms and relentless harassment towards our team. You don't live it, we do.
@GrapheneOS I have to this response was not unexpected. I think I'm going to tryout Lineage Is this weekend.
@RCSM Go ahead. If you want to make your phone far less private and secure, that's your prerogative. You're not paying us anything to use GrapheneOS. If you don't support us when we're being viciously attacked by people trying to destroy the project, what are we losing if you leave?
HybridStaticAnimate@RCSM @GrapheneOS This is just petty. Losing one user, out of spite, isnt going to matter. GOS is free to all, and its number of users arent a metric that needs to be increased at all costs. Your spite falls short but it is saddening that you tried to be, regardless. The only consequences are you making your device less private and secure. That is to your detriment, not GOSs.
@RCSM @GrapheneOS Your insistence on neglecting active and significant harm is concerning. This apathetic attitude is why people are not held accountable. It cannot just be dropped the same way getting hurt and abused repeatedly cant be dropped. Youre essentially telling victims of abuse and attempted murder to suck it up.
wod0bowI think that communities (GrapheneOS and Rossmann) don't have full view of that case and it never received transparent presentation.
Even if both attacks each other.
IDK if approach you chosen is the best way and I have some doubt's.
Maybe the private message to Louis will be more approperiate? Just to solve all issues between both sides without public.
Personally I don't like washing dirt's in public. But this is only my humble opinion.
We are only people and we all have flaws.
@wod0bow Rossman engaged in his extraordinarily harmful attacks on GrapheneOS with fabrications, misrepresentations and harassment he deliberately orchestrated from his large number of followers. He did it because a developer who was upset with him private message after months of Rossmann's bullying in private and public which included his support for Techlore's attacks on GrapheneOS which had escalated to repeated swatting attacks from his community. We're open to resolving it with lawsuits.
I understand your approach. Even the legal path. I just don't know if it should be public before the final resolution or even any true actions.
IMHO if you are trying to have good relations with someone you should talk with that particular person and try to solve issues instead of talking about that to the public.
If you are going with legal path than instead talking about that file a lawsuit. And announce that to public.
But maybe this is only my approach.
@wod0bow @GrapheneOS
Concealing abuse, as a victim of it, is not really a good idea.
Last time GOS tried to privately raise the issue and discuss it, they were publicly humiliated and misrepresented. GOS is giving them a chance for forgiveness.
Johnny Doe@GrapheneOS Isn't one of the core points of open source, is to give the freedom for others to use the licenced fcode and documentation, heaviliy or otherwise and for any purpose.
@pickadollen @GrapheneOS Copperhead CEO James Donaldson and others have relentlessly tried to make people believe that Copperhead is the creator of CopperheadOS and that GrapheneOS is a fork of CopperheadOS initially released in 2019, which is a lie and has nothing to do with the availability of the source code.
Copperhead's scam archives : https://github.com/beerisgood/Mobile_Security?tab=readme-ov-file#copperheados-warning-scam
GarretSidzaka@GrapheneOS
I read this story and I want to say that it feels like these guys are part of a growing social movement of untalented authoritarians who are trying to destroy what they cannot consume utterly
I read this story and I want to say that it feels like these guys are part of a growing social movement of untalented authoritarians who are trying to destroy what they cannot consume utterly
d@nny disc@ mc²@GrapheneOS i have seen this happen repeatedly and far more often lately they will lose legitimacy eventually
Jerome@GrapheneOS Did the court publish their decision? They do in many countries. If they did, you can use that as evidence to correct the Wikipedia articles.
@GrapheneOS i cannot express my gratitude for you and your team's work and it is the one single thing that reminds me safety is something we can build together. within adversarial channels they remain powerless against the discrete log. that hardware resources can be made more or less deterministic to any necessary tolerance if you don't ever compromise and you research and test and measure in a way that means something new
@GrapheneOS my favorite fun fact about rust is from a blog post by the person who presented about failure at the mozilla rust meetup a decade ago with rainbow hair and cursed me to love the language. i disagree with the content of this post in the strongest of terms (as in making a separate language because of this and other decisions—but the author makes absolutely sure to credit the right person with the design of rust iterators, based off of a 2013 mailing list post https://without.boats/blog/why-async-rust/ i am still in awe of this. astral got sold to openai off of erasing my work. python is dead, rust is now too. but there are ways to change the world that last forever and i will find out mine too
@GrapheneOS oh my god i did not realize they also saw a future of coroutines
@GrapheneOS i would be interested in any critique or associations you may have regarding the two separate proposals i made to the coroutine discussion https://github.com/rust-lang/rust/issues/43122#issuecomment-3614498718
@GrapheneOS i thought i recalled a lifetime issue i discovered when making a ring buffer (https://codeberg.org/cosmicexplorer/corporeal/src/commit/a3a36a088d932f69ba6974933fc2ee86ed0e3895/yzx/core/mony/src/coro.rs#L84since) since literally no one in all of rust has ever considered that a ring buffer of fixed size produces backpressure. given that astral refuses to touch the zip crate that has my innovations written all over it i think being declared radioactive is a success of the highest caliber
@GrapheneOS unfortunately i'm scared of rust now but the rpgp crate is lovely and it writes great code
@GrapheneOS oh while i continue to post nonsense at you i'm going to be working on a double ratchet impl with ed25519 keys and it will likely be in c++. if it becomes something i can stand by i will find the appropriate contact route to message the project about it and how it might be used
@GrapheneOS (which may be nil. but the qtconnections library for kde connect is intentionally bad does this pinball loop around the file while parsing. almost cpython behavior)
@GrapheneOS oh last thing i did find a clear backdoor in the linux 7.0 rc last weekend from david howells editing linux-crypto source code. i have precise commits but i'm sure you'll find the problems if you look and i felt incredibly nihilistic to finally understand what you meant when you said the kernel is not serious about security
Taureon@hipsterelectron @GrapheneOS "python is dead, rust is now too" what are you talking about?