Privacy is another obvious challenge … Google suggests that on-device processing and face authentication could help address those concerns
So create the misconception the data remains local (as the processing happens locally), while incentivizing them to using face authentication (enabling the 8-second selfie cam video clip upon unlock: used for heart rate estimation through skin changes), and the EULA roofying of course serving as the “explicit consent”.
This should be protected health data.
Yes I love not having choices
fantastic, now they can tell which specific parts of the jeep ad get my blood pumping
Hopefully they’ll continue utilising Outrage as the Prime Engagement Metric, so that when I start swearing loudly at annoying scammy ads, they’ll assume that means I’m “engaged”, and that’s good, so they’ll serve me more and more ragebait
That’s exactly what they’ll use it for. We so desperately need a european alternative to android and ios, something that actually respects your data
It’s naive to think that European companies won’t find a way to do the same level of shady shit in the future once everyone is nice and complacent.
The idea is that it would force vendors to easily let users install other OSs and app providers to not only allow android and ios
Graphene OS, join it. Motorolla is making compatible phones but the google pixel phones are compatible for now.
I would rather have an actual alternative instead of something that still depends on the whims of Google. Also this would not help in untying the current hard coupling between hardware and software
The pixel phones aren’t tied to google after you drop the graphene open source operating system on them, that’s the entire point. There are tech enthusiasts here that could explain it better than I.
But android is open source, google used it, forked it off, and are trying to make their fork proprietary or something idk, but the phones can be used without being compromised by google. They are working on sabotaging graphene quite predictably.
Google didnt fork Android, they own it. It’s also not really open source anymore since the aosp codebase is only updated every few months and doesn’t accept contributions.
I would not build something new from that. I would rather pour money into fixing the few issues with Ubuntu mobile or something similar and be rid LF Google
Motorolla has been building a phone just for graphene os, and these pixels are safe to use as such I’ve been assured, there are a lot of people in on the collaberation that know what they are doing.
Idk about ubuntu. But graphene will get the economy of scale which is key. It’s already fairly big.
The issue is not what specific vendor produces the OS, but that it should not be based upon something that Google controls. If Google stops publishing the code for the Pixel tree, GraphenOS is fucked. They already had great issues when Google stopped using a public repo and only published updates on a quarterly basis
This is kind of incredible. No longer need to purchase a smartwatch to track heartrate.
