Oh, it's preventing sidloading?! I thought it was just for their app store!
That's shit.
Oh, it's preventing sidloading?! I thought it was just for their app store!
That's shit.
I wish more people focused a bit more on the need to agree to terms and conditions, I didn't know that was a part of this issue and that massively increases the negative impact of this potential policy change
Google's terms and conditions are consistently draconian and stupid. Especially if it's the same terms and conditions applied to the play store, where apps constantly get pulled and devs are always frustrated as hell
Edit: I think pretty much everyone who replied regarding terms and conditions misunderstood what I meat, which leads me to believe I may have communicated poorly. My point is that early news coverage didn't mention independent apps needing to follow Google terms and conditions.
That's not just a privacy issue for devs, that's an issue of Google wanting control over what the apps and actually do, and it changes how severe of a problem this is. I've also learned since then that this may mean only the devs can distribute apps(?), which would potentially kill f-droid outside of custom roms (I still don't fully understand that part but that idea was also not in early coverage)
Google's terms and conditions are consistently draconian and stupid.
They are not stupid, they are just intentionally malicious.
I will always believe that people can't be asked to read a whole fucking T&C written in legalese to avoid being transformed in a human centipede.
Fuck that bullshit!
"I have read and agree to the Terms" is the biggest lie on the web. Together, we can fix that.
I think pretty much everyone who replied regarding terms and conditions seems to have potentially misunderstood what I meat, which leads me to believe I may have communicated poorly. My point is that early news coverage didn't mention independent apps needing to follow Google terms and conditions.
That's not just a privacy issue for devs, that's an issue of Google wanting control over what the apps and actually do, and it changes how severe of a problem this is. I've also learned since then that this may mean only the devs can distribute apps(?), which would potentially kill f-droid outside of custom roms (I still don't fully understand that part but that idea was also not in early coverage)
What are people going to do instead? It isn't really feasible for people to spend hours reading legalese and from the standpoint of the consumer there is really no other option
I think pretty much everyone who replied regarding terms and conditions seems to have potentially misunderstood what I meat, which leads me to believe I may have communicated poorly. My point is that early news coverage didn't mention independent apps needing to follow Google terms and conditions.
That's not just a privacy issue for devs, that's an issue of Google wanting control over what the apps and actually do, and it changes how severe of a problem this is. I've also learned since then that this may mean only the devs can distribute apps(?), which would potentially kill f-droid outside of custom roms (I still don't fully understand that part but that idea was also not in early coverage)
Well maybe companies should make clear concise terms and conditions. No one is reading 30 pages of documentation to use something.
I think pretty much everyone who replied regarding terms and conditions misunderstood what I meat, which leads me to believe I may have communicated poorly. My point is that early news coverage didn't mention independent apps needing to follow Google terms and conditions.
That's not just a privacy issue for devs, that's an issue of Google wanting control over what the apps and actually do, and it changes how severe of a problem this is. I've also learned since then that this may mean only the devs can distribute apps(?), which would potentially kill f-droid outside of custom roms (I still don't fully understand that part but that idea was also not in early coverage)
As I said & many others before me. We need a massive unified push towards breaking the OEM locks on our phones & make it compatible with Linux.
But what can we do beyond letting out elected officials who don't care know about it? How can we really push back against Google for doing this?
Donate to PostmarketOS so that we have a polished Linux alternative to Android.
I will, I think Google has proven that android can't be the "open source" alternative, especially since it's not even open source anymore
Linux desktop isn't even as polished as closed source OS even after all these years. Windows always gets better battery life on the same hardware.
Linux is pretty damn polished now, in some areas more polished than Windows.
Battery management seems to depend on the specific device and how well supported and optimized it is. As an example, the steamdeck gets better battery life on Linux than it does on Windows.
But we're at a point where the 'polished' corporate options are so user-hostile, that a 'good enough' community built alternative is enough.
Only purchase devices you can unlock bootloader and root, then bypass this with an Xposed module that hooks into Package Installer like how you would bypass Google's stupid minimal SDK version requirement for side-loading that's already enforced for years.
Google has made it absolutely clear that for years there's absolutely no reason you should ever use an Android device without root anymore than you should use a personal Linux device without sudo lol
Unfortunately for work I'm not allowed to have a rooted phone, that's their only requirement. On top of that working in finance I know that tokenized payments like Google wallet and apple pay are the most secure, and I like leaving my wallet at home and paying with my phone. I hear though no other OSes or roms support wallet, is that still true?
If work pays for your work phone, then this isn't relevant to that. The company I work for provides me with an iPhone - they pay for the device, service, and insurance. It's not my phone, so I'm not gonna bitch and moan about not being able to jailbreak it. I have my own phone for that.
The iPhone lives in my work backpack with my work laptop. Both are actively ignored unless I'm on the clock.
Let's not confuse rooted with bootloader unlocked. My /e/OS is not rooted and four bank apps work, including Curve Pay for leaving the wallet at home. Probably thanks to microG contacting Google when needed.
This might break if the comment over there is right: https://lemmy.world/post/36621884/19652276
Then get another cheaper phone for work, you don't need an expensive high end phone just for work, it's not like you're gonna run engineering simulations on your phone anyway, and there are a lot of good reasons to keep your personal phone and work phone separate too.
In Asian countries there are many digital payment platforms other than Google Wallet and Apple Pay that don't care about root, or are very easy to spoof for root status. And besides relying on digital payment platforms that are specifically owned by Google and Apple, and willingly stay locked inside their walled garden, is increasingly seem like vert very scary things these days don't you think?
Very good points except for my work phone I need to then pay for a separate sim on that one which is why I haven't. For wallet and finance the problem isn't that the community can't build our own, it's that banks would never trust it because it's not backed by a company. So we're locked into those few for now, but they are more secure
Why not just use credit/debit cards like we used to do before Google Wallet got its current market dominance in certain regions?
And for most of the service apps like Uber you can just add your credit card information so payment never need to go through Google Wallet anyway, and you can also deal without your bank directly if there's a purchase dispute instead of having to have Google in the middle, no?
By the way you're in EU right? I'm curious which region is having so much issues with all of these
I'm in the US unfortunately here.
So working in FinTech for decades taught me a lot about how these systems work. To be clear, I'm talking about adding a credit card to your google wallet, not keeping money in your google wallet, so disputes and everything still go through the credit card company. Call me paranoid, but carrying around cards now is a risk, especially when traveling. I carry around one spare in case the phone gets stolen, but it's the card I know I can lock down immediately.
Tokenized payments are the most secure because no data about you or your payment info is transferred at the PoS/terminal/till when you check out. It requests a one time token from google wallet/apple pay/whatever and some metadata about the transaction into the terminal, which passes the token to the banks. The actual passing of private details then happens solely between those two parties, the money is (scheduled) to move, and the bank informs the register that the sale went through.
Credit and debit cards contain your personal info. While the stripe exists on it it can be skimmed and duplicated, and even with the chip someone can still steal it off of you and make bogus purchases. Tokenized payments you are required to be present for it to work. If someone steals your phone they can't access the wallet app without you there, it's low likelihood they could even access the account without you there. Even then, you can erase it remotely now.
So, I don't care that it's Google wallet, some other name would be fine, if there was a more open one I'd use that in a heartbeat, but I am a stickler for tokenized payments. It's just undeniable that they're more secure.
Yeah... The benefit to increased security there is marginal at best. Google wallet doesn't play nice on rooted devices, and having a rooted device that allows me to tell Google to fuck right off is far more worth it than slightly more convenience.
Yes I agree that in terms of a financial service, tokenized transaction system indeed architecturally guarentees greater safety, but a bigger concern is the provider of this service.
Did you not hear about what happened recently when a certain major payment processor realized they can arbitrarily enforce what they think other people should and should not be able to buy, by withholding the availability of such service? Well functionally the exact same thing is happening to you, Google doesn't want you to be able to control your own devices because Google is an advertising company who also profits from selling your data, annnnd Google also happens to be the commerical supplier of Android with their commerical GMS certification program which includes Play Integrity check and all that, so they can arbitrarily decide that if you attempt to have more control over your own device, you don't get to use Google Wallet anymore.
Are you happy to submit to this mafia practice from Google? I wouldn't lol. Not saying I have a solution but then again I don't think any single individual could possibly have a solution to the disaster that is the US capitalism.
Not using it but I heard curve does it too over graphene OS. (And no, it's not a bank nor FOSS) But if a tokenised wallet app is all that keeps you from Moving forward ..)
It quite literally is the primary thing! This works on Graphene? I'm very interested then! Sure it's not FOSS, but I'd be honestly surprised if anything in the banking industry went OSS, let alone FOSS. I don't care about their money back schemes or anything, but I'm all for more competition in that space!
Tell them its a security risk and refuse to use a phone that's not rooted. You can't even get an iptables firewall without a rooted phone ffs
Elected officials can only do so much as people still need to care. Eenshitification will drive people into other platforms if it gets bad enough.
Degoogled phones, there are plenty.
In any case, you can probably prolong the usage of your current phone for a few extra years without issue. So don't panic yet.
It's not the Gapps, it's Android itself. Have you hit your head?
It isn't Android since AOSP isn't effected
"Android" Open Source Project.
You can sideload until they remove the functionality. You can flash a ROM until they lock the bootloaders.
All things that are happening and you seem oblivious to.
It doesn't impact AOSP what so ever
If you say so.
You have evidence to the contrary?
To someone who's yet to bring their own? You made a claim, prove it. Clownin'.
https://old.reddit.com/r/LineageOS/comments/1nt8k0j/google_blocks_apps_without_a_signature_or/
It is Google play services that enforces this
What the hell are you talking about? Android is OPEN SOURCE. Degoogled phones will simply modify the codebase to avoid Google limits and bloat, like they are doing literally today? LineageOS, GrapheneOS, /e/OS...
I said degoogled phones, not degoogled apps.
"modify the codebase" Alright good luck with that buddy. Let us know when you're in the mainframe.
Go chinese
That is somehow worse
Making my next phone a classic flip phone would probably do me a lot of good.
I think I'm almost at that time where I dump the internet. I'm 50 and I was an early adopter. I'm a very frequent user, however this is not the internet we all fought for. It's been slowly eroded to a corporate money grab and I'm not really down for that anymore. I'm tired and I think the internet needs to go away for me.
Iβm pretty much on the Internet to look up information for video games, Fediverse, and write the occasional email. My smart phone is mainly to receive emergency calls from family, coworkers, and the occasional navigation task but they still make GPS units.
Sounds like weβre both old enough to remember that there is life without the Internet. I could do it. Tech companies are out there acting like thereβs no alternative.
top 100 comments