Petitions and shit would only have any meaning if the decisions were based on ethicand public interest, but it's all money and power, so the only petition and open letters worth signing are those just saying fuck google and the human garbage running it
Privacy
Welcome! This is a community for all those who are interested in protecting their privacy.
Rules
PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!
- Be civil and no prejudice
- Don't promote big-tech software
- No apathy and defeatism for privacy (i.e. "They already have my data, why bother?")
- No reposting of news that was already posted
- No crypto, blockchain, NFTs
- No Xitter links (if absolutely necessary, use xcancel)
Related communities:
Some of these are only vaguely related, but great communities.
- !opensource@programming.dev
- !selfhosting@slrpnk.net / !selfhosted@lemmy.world
- !piracy@lemmy.dbzer0.com
- !drm@lemmy.dbzer0.com
Petitions are one tool in a much wider toolkit. As long as they're even somewhat effective, I don't see it reason not to utilize them.
A code repository
What process? It's all closed source drivers by Qualcomm et al.
Lets not act like this is an impossible task.
There is a process and actually multiple ways to accomplish this. Looking into, we might not even need to fork android, but just support existing alternatives.
I would think the first step is to fork the Android Open Source Project. use that as a base, start cutting out any links to google, fill in the gaps, etc. This is obviously not my realm of expertise but there is a path.
"170,000 tech workers lost their jobs in the U.S. in the 18 months prior to mid-2025"
Don't tell me we can't scrape together a team of experts and make this happen. Yes there will be barriers and push-back, but its either this or we just keep deepthroating google.
Thank goodness for existing Android forks (which persist even now), and for projects like the Mecha Comet.
I mean, that's great from a moral standpoint, but forking android will not also switch the billions of devices running it. The real problem is escaping or changing it at scale
Wouldn't funding MicroG be the better call to action?
AFAIK this restriction will be part of Google Play certification and not AOSP itself.
That means we'd need the ability to unlock bootloaders to be maintained, and a good comparable open source abtraction to Google Play Services so users have a soft off-ramp from the Google Play ecosystem
Technically the correct first thing to do is to make the manufacturers release the relock keys for relocking the bootloaders of extant hardware (say, the Moto G6 for an example). Having MicroG or whatever is not much useful if there's not going to be a feasible phone on which to install, so getting extant phones to become relockable with AOSP distros would be priority. And the way the economy si going and the RAM chips are not, forcing everyone interested to have to buy a whole new phone is not a smart choice.
Once the relock keys are out, fund All the Things. Lineage, Calyx, MicroG, what have you.
You'd need phone vendors going along with it. Good luck with that.
Does anyone know if Huawei phones will be affected as well?
Here is the list of brands that it will affect. For the West, it's pretty much everything.
😔 Thank you for the list but yeah basically all of them.
