EnderWigginMar 13

RE: https://grapheneos.social/@GrapheneOS/116217279930043732

To anyone who's actually confused about what to pick between GrapheneOS and Murena/eOS. I very much encourage you to read the article linked by GrapheneOS in the description (Kuketz's blog post as well, linked inside the Graphene blog post) and if you go to the referred iFixit post mentioned in the article (which has corrected some of its mistakes after Graphene pointed it out), you can also find the official /e/OS response to Graphene's blog post as well.

Kuketz's post is really informative on how /e/OS works and I'll strongly recommend people considering /e/OS to give it a proper read.

Once again, thanks to @GrapheneOS for linking me towards the information I needed politely.

#Android #grapheneos #Murena #aosp #eos #IodeOS #security #privacy #opensource

Show threadGrapheneOSMar 13

@skywalker2k17

> which has corrected its mistakes after Graphene pointed it out

It hasn't been anywhere close to fully corrected. In fact, they added a false narrative from Murena to the article misrepresenting GrapheneOS as not being a privacy project or /e/ somehow being more focused on privacy. They left around implying that devices can't be purchased with GrapheneOS which is inaccurate too.

Show threadEnderWigginMar 13

@GrapheneOS But they didn't say that Graphene isn't a privacy project and they also corrected to say /e/ is for people who wants to avoid sending their data to Google (which is kinda true but also not). They didn't correct the last part though, they should have added that you can purchase Nitrophones and I'd say the editorial note they added at the end helps, that /e/ can have more device vulnerabilities that can leak users data and obviously they didn't want to openly pick either side and just left it to the community to decide.

They didn't go as deep as Kuketz's article which was why I mentioned that people should read through it as well if they are considering /e/OS.

Show threadGrapheneOSMar 13
@skywalker2k17 They misrepresent GrapheneOS as a security project which is a false narrative from Murena and other groups pretending it isn't a privacy project. They're misrepresenting it as not being for people focused on privacy when it provides far better privacy. Unlike /e/, GrapheneOS avoids connecting to any Google servers itself and avoids including a bunch of privileged Google app/service integration as /e/ does. Their comparison is thoroughly inaccurate and based on false narratives.
Show threadEnderWigginMar 13
@GrapheneOS That's a hardline stance but yes, I agree with what you said as /e/ isn't truly open regarding their unnecessary connections to Google servers, enabling microG by default, unique device identifier ID and the constant pings to Murena's servers despite it set to once daily. Which was why I also mentioned in the post to read the article which is eye-opening regarding /e/. As for why I am not saying /e/ or other ROMs are bad outright is because I am not as well versed as either you or any of other tech companies and this isn't my area of expertise and I believe it best left to people involved in the process and the person choosing their OS after they properly research.
Show threadEnderWiggin
@GrapheneOS And I edited my toot to say ifixit corrected "some of their mistakes" after Graphene pointed it out and I forgot to say this earlier, I did find it amusing how they said Graphene is focused around security and didn't mention privacy but even if we were to point it out they will just say what I said earlier "we didn't say it's not private" and didn't pay it much attention cuz they did go into the vulnerabilities of using /e/ which at least shows their intention to not be openly biased against Graphene if contested.
Mar 13 at 2:46pmWeb
Show threadGrapheneOSMar 13
@skywalker2k17 Getting the current point the article is in took many people complaining about it across platforms including people outside of the GrapheneOS community who don't use GrapheneOS. We aren't the only ones sounding the alarm about /e/ and their inaccurate marketing. It was originally people from LineageOS talking about it years before we started saying anything. We only started regularly talking about it after years of them misleading people about GrapheneOS. We used to ignore them.