Someone related to the GOS project was caught red-handed calling for this just a few years ago. Both Louis Rossmann and Techlore did videos on the whole situation with Micay and the drama surrounding him, including that bit (I forget which video showed that particular bit), and brought receipts.
I have no doubt in my mind that GOS is a solid OS, being created by someone so obviously paranoid. But that paranoia is causing a lot of other issues and infighting within the ROM community.
All that stuff was being sent around in the .ml Privacy community again recently, including their favourite conspiracy theory involving Techlore, Louis Rossmann and Nicholas Merrill (founder of Calyx Institute and CalyxOS). According to the GrapheneOS cult, Techlore and Rossmann are paid employees of Merrill’s and have been attacking GrapheneOS on his behalf. Zero evidence, of course. Just the usual “source: trust me bro” you expect from GrapheneOS.
And as usual, a lot of it was orchestrated in the comments by a moderator of the GrapheneOS community here. Guess what the thread was about? Yes, another attack on the security and privacy of /e/OS. It’s all so predictable.
Someone related to the GOS project was caught red-handed calling for this just a few years ago. Both Louis Rossmann and Techlore did videos on the whole situation with Micay and the drama surrounding him, including that bit (I forget which video showed that particular bit), and brought receipts.
I have no doubt in my mind that GOS is a solid OS, being created by someone so obviously paranoid. But that paranoia is causing a lot of other issues and infighting within the ROM community.
All that stuff was being sent around in the .ml Privacy community again recently, including their favourite conspiracy theory involving Techlore, Louis Rossmann and Nicholas Merrill (founder of Calyx Institute and CalyxOS). According to the GrapheneOS cult, Techlore and Rossmann are paid employees of Merrill’s and have been attacking GrapheneOS on his behalf. Zero evidence, of course. Just the usual “source: trust me bro” you expect from GrapheneOS.
And as usual, a lot of it was orchestrated in the comments by a moderator of the GrapheneOS community here. Guess what the thread was about? Yes, another attack on the security and privacy of /e/OS. It’s all so predictable.