this post was submitted on 02 Nov 2023
44 points (94.0% liked)
DeGoogle Yourself
8799 readers
2 users here now
A community for those that would like to get away from Google.
Here you may post anything related to DeGoogling, why we should do it or good software alternatives!
Rules
-
Be respectful even in disagreement
-
No advertising unless it is very relevent and justified. Do not do this excessively.
-
No low value posts / memes. We or you need to learn, or discuss something.
Related communities
!privacyguides@lemmy.one !privacy@lemmy.ml !privatelife@lemmy.ml !linuxphones@lemmy.ml !fossdroid@social.fossware.space !fdroid@lemmy.ml
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There are 3 important factors that drove me to CalyxOS rather than GrapheneOS:
1/ There's no way in HELL I'm buying a Pixel phone and giving my money to Google for the privilege of not being tracked by Google. That's really too rich for me.
2/ I want a repairable device.
Therefore I bought a FairPhone 4 (repairable and not Google), and only CalyxOS supports it - of those two that is.
And finally 3/ The GrapheneOS community is toxic. Although in fairness, now that the Chief Toxic Officer is gone, maybe it's gotten better. At any rate, the Calyx community is completely peaceful and exemplary compared to Graphene.
This may not matter to you, but it seems to me like a sane thing to do not to trust software made by someone who talks that much shit.
While I am agreeing somewhat, and I haven't been active in the community much. The few encounters I had was in the matrix chat . Yea toxic af . Checked in too see now , scrolled a bit but quite civil atm.
I repair pixel phones as an hobby / side gig and yea not comparable withe fairphone, but still repairable , better than a lot of others but depends on models.
I buy second hand in bulk and repair whats needed. Bonus of no trail to Google as well.
Off topic: but about repairing pixels as a side gig.
For the Pixel 5A5G, the screens not being responsive issue, it appears to be widespread. The discussion forums, and the Google forums, simply refer to it as a "motherboard issue".
In your experience is that more likely to be a bad BGA join coming loose over time? Is the most likely repair option for those devices reballing the BGA on the CPU?
Graphene community isn't toxic at all, there's some people who you really shouldn't listen to seriously for advice but other then that it's like all community's with some good eggs and bad eggs
I went with GrapheneOS and it is my preference, but we need all this software to mature. We want choices and a hardened more complete feature set, so I really want CalyxOS to succeed also. That and Lineage, /e/os, Linux Mobile options etc.
Also, privacy fruendly esim activation anyone? (Am aware of privacy issues with sim)
Confused on what you mean by that
Well, if you want to activate an esim on any other Android rom, you need to use Google services and have an internet connection. DivestOS is the first rom to implement an open source version of eUICC, which is used for activation, called OpeneUICC. It also does not need an internet connection, so nobody knows that the esim is installed on your device. That is, until you actually use it, of course. This is in line with DivestOS actively trying to "deblob" (remove binary, closed source parts of) Android.
The second part, about why sim is not very private, well it has a unique identifier and the technology was specifically designed to pinpoint your location, as this helps keep a good connection.
Also, why did my comment get downvoted?
GOS also have esim implementation without google
Ah yea, that's true. But at least you can remove it after activation it seems. https://github.com/GrapheneOS/os-issue-tracker/issues/159#issuecomment-1292329307
SIM cards contain authentication keys for the cellular network so it knows who to bill and which cells to send a paging signal over to ring a call. The use of SIM cards does not pinpoint your location, and SIM cards have absolutely nothing to do with keeping a good connection (pSIM or eSIM). The network and handset are constantly re-evaluating signal strength across various bands and modes and the network tells the handset to switch to what works while moving about the network. The SIM just auths the user account. It is ostensibly a key to your service, nothing more.
All the network band/mode hunting will continue with or without a SIM card, the phone would just be limited to emergency calls in that state.
I don't think you understood half of what I wrote correctly. Feel free to skip the next paragraph if you already know about triangulation in the context of cell towers.
Your phone, when connected to a cellular network, can be tracked by cellular towers. Take a single tower to which you are connected. The tower has a multitude of devices which are connected to it. Since latency is a large issue due to distance, communication is less trivial. To prevent waiting for packets from a device for too long, the cell tower will divide a certain time into sectors. In each of these sectors, one device is supposed to send it's packet. To hit this time window however, the device has to send it's packet in advance, as to cancel out the latency of the transmission. By how much is determined by the distance between the cell tower and the device. This system requires knowledge of distance. This distance has to be close enough to the real distance, to cancel out latency and maximize the time a device can send data. With obstacles that may reflect the waves, the preciseness of the distance determined is correlated to the stability of the connection. Given that a lot of people can be using a cell tower at once, there are towers which are segmented. These work slightly differently than non segmented ones, in that they have multiple antenna sending and receiving signals in different directions. A segment of a tower with 6 segments would then be responsible for all devices which are in the area of 60 degrees from the tower. The distance together with the general direction already gives us a pretty accurate depiction of the user's location. However, since most towers are neither segmented, nor would a say 6 segmented one give as accurate of a reading if the device is 3 miles away (that would be a possible curve of pi(≈3) miles which the device could be on, given a perfectly flat ground), let's make this even more interesting. With a simple, rough time stamp, we can find out the location of a device up to an accuracy of a single point. Add a second cell tower, make the device connect to the towers one at a time and you have the exact position of the device. Well, pretty close to exact at least.
With that said, the reason why a sim card is the issue in this constellation is the unique identifier. If a network of cell towers can determine where you are located and the imsi is tied to your identity, then your location is tied to your identity. And if you think, even for a second, that mobile internet providers would not take advantage of this, think again. A very popular example of this are malls wanting to know where their customers came from.
Now, if you have a device with GrapheneOS (DivestOS too I think, don't know) for example, then you will have the ability to entirely switch off the cellular antenna of your phone (which one should likely do if they don't have a sim anyways). This is supported by hardware due to airplane mode, where the airplane requires least interference.
Now that I have explained in more detail, do you understand better why a sim card is a privacy concern?
1/ I know Pixels are technically the best. That's not the issue. My issue is: I am not giving my money to Google, and certainly not for the purpose of escaping the Orwellian dystopia they're building around us. It's not a technical problem, but a question of principle.
I know some people argue that buying Pixel phones specifically to install a deGoogled OS sends Google the message that people are willing to pay for the privilege of preserving their privacy, and the more people buy Pixel phones for that purpose, the louder the message and the more likely Google will finally listen and convert at least part of their business model away from corporate surveillance.
But you know what? That's bullshit. Google will never stop violating people's privacy and monetizing people's data. They just take your Pixel phone money and laugh all the way to the bank at how naive you are.
I will NEVER give Google a single dollar. Full stop. It's not even an option. I'll take the additional risk of using a non-Pixel phone - which, for my threat model, it completely insignificant anyway.
2/ I'll pay whatever it takes to escape Google, and also give the throwaway economy the middle finger. As a well-to-do first-worlder with plenty of disposable and grown up children who have left the house, I have the means to buy overpriced equipment that's compatible with my worldview.
3/ I don't care about drama regardless of where it comes from. Quite frankly, I don't even want to know: I've read enough about and around what was going on with DM to just give the whole thing a pass. Besides, like I said, the man seems crazy enough that it basically invalidates any trust I might have in his code, and it's precisely the type of application for which I desperately need trust. I don't trust DM nor his code, and that's not even a community issue.
I have neither the time nor the desire to review MD's code. I need a working cellphone OS that I can place a reasonable amount of trust in. The Calyx Institute looks 100% legit, run by normal, rational people who aren't off their goddamn minds, and I trust what they do a lot more than GrapheneOS because a lot of GrapheneOS was put together by a nutjob.
Yes. There are deluded, wide-eyed idealists who believe Big Tech should be shown that there are honest ways to make money off of direct sales and they don't need to put people under surveillance, and the best way to show them is proving it with their wallets. What they fail to realize is that Big Tech is unprincipled to the core, and the unprincipled way of making money off of people's privacy is orders of magnitude easier and more profitable.
I have nothing against people who have mental problem. Hell, many people who get heavily involved in computers and into free software are on the spectrum and I have no issues with them or the software they made, which I enjoy using.
What I have a problem with is code made by people who make threats. I don't care why they make threats: if they can code, they can code revenge code. And I have a problem with code made by people who have a persecution complex for the same reason.
DM thinks he's persecuted and he did make threats. Repeatedly - unlike Linus. I'm sorry for him and I sympathize on a personal level, but that makes his code quite untrustworthy, because his motivations for making the code and the state of mind he was in when he made the code make the code inherently suspicious. And like I said, I don't have the time nor the desire to go through and vet his code. I have enough projects to take care of myself without having to second-guess someone's suspicious code.
He may be a genius security researcher and he may be the most talented individual on planet Earth. But in the line of work he chose, having a squeaky-clean reputation and credentials is everything, and his personality issues unfortunately damaged both and tainted his work.
Personally, I preferred not to take the risk and I went with Calyx's work which, while perhaps not as hardened as DM's libraries, is adequate enough for my threat model and - most importantly - made by people with a clean rep. At least it was one of the factor, since I was never going to buy a Google phone anyway, and GrapheneOS only supports Google phones.
GOS also got code upstream in AOSP.
Here is an alternative Piped link(s):
his not a people's person
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
Is it possible to re-lock the bootloader on the phairphone with calyxOS?
Absolutely. It is recommended in fact.