When you say "Ok, Google," it must respond every. single. time. Always. No matter what.
When you dictate a command, it must be interpreted quickly, and correctly, 100% of the time. None of this "Sorry, can't reach Google at the moment" garbage it currently replies with about 70% of the time.
Fix this first before addressing all the cutsie UI crap. Please!
Hopefully this three-way battle between Google, Amazon and Oracle will result in an opening a new mobile competitor can squeeze into. Android desperately needs some legitimate competition.
So I'd been a Netflix customer and firm proponent since they went online. Not a heavy user, by any means, but I did enjoy shows at the gym, and I spread the gospel to anyone I met who still had legacy Cable TV.
About 6 months ago, Google added an option in the Play Console (for app developers) to exclude devices that fail to pass their so-called "SafetyNet" provisions.
Unfortunately, I and many others are unable to meet that requirement. "SafetyNet" isn't some simple checkbox agreement like "device modified; I know what I'm doing [Y]," but rather a set of secret scripts Google runs as root on your device to determine if Google has full control. Activities like patching security vulnerabilities, rooting, running AOSP, or even unlocking your bootloader disqualify you. The entire list of checks is, to date, secret. Their code updates happen automatically, in the background, without user control if you have the Play Store installed.
Once upon a time, the excuse for "SafetyNet" was that soon, Android devices could be used to pay for things. Fair enough. Just like my PC.. but it's mobile, so I guess different rules apply (?)... I can use cash, or a credit card. Frustrating, but not a huge deal.
Of course that wasn't the end goal, as we've seen. The end goal was to discourage rooting, so that they could guarantee that their products (also known as users) would be forced to watch ads. Ad blocking is designed to be incompatible with "SafetyNet."
Lo and behold, back in June, Netflix started requiring "SafetyNet" certification in the Play Store. If your device doesn't qualify for any reason, you're excluded. Sideloading may still be an option, but I'm not sure.
Lucky for me, there are alternatives; I went to Amazon Video and YouTube, and cancelled my longstanding Netflix account. If the others follow suit, I will abstain from mass media and spend my money elsewhere.
Not everyone is willing to jump through such hoops though, and it's entirely possible this little stunt will bring back piracy from its death throes. All so that Google (and one day, surely, Netflix) could force more ads on us all.
Side note: yes I know Magisk can help. It's an arms race, for sure... but a great departure from what made Android successful in the first place.
I am with Ajit Pai on this for the following reasons: private property owners must not be oppressed by any form of business regulations. That's my position on regulations.
I agree with you with one critical stipulation:
The abandonment of regulation must be a complete "atomic" transaction.
If the radio spectrum is suddenly a free-for-all, such that I'm able to erect and operate a 10,000W transmitter and establish my own Internet links, and rules governing access to established wirelines are abandoned so that I can use the dark fiber I paid for through previously collected taxes, then fine.
But the dissolution of regulation must happen all at once.
What's not okay is the removal of regulations on communication providers without the associated removal of privileges they enjoy.
Senior systems architect of 20 years. Grew up on Solaris 2.6, Slackware, and have been an exclusive Debian user for the balance.
Designed and built embedded flight controllers, vehicle dynamics processors, power controllers...
I am not smart enough to troubleshoot Windows issues. So give 'er a break.
Alongside net neutrality, laws should exist that dictate no owners of general technology devices can be artificially/intentionally restricted from accessing any part of their device.
I don't mean "thou shall include a JTAG port and dongle".. I mean that it becomes illegal to import for commercial sale any device that the manufacturer/reseller has locked down for the sole purpose of excluding access to tinker.
This succinctly summarizes what I've been trying to relate to others for quite some time.
"Active" security is generally treating the symptoms of poor quality software. selinux, "SafetyNet," virus scanners.. all of these things, while masking some issues, add code complexity and expose a larger attack surface.
Simple, clean, elegant, and obviously correct code (and that includes design) needs no complex "security" bolted on. It just needs to function as documented.
These tax credits aren't intended as help to the individual, so the individual's wealth status is irrelevant.
These tax credits are the reverse of taxation. Taxation tends to suppress behavior, where tax credits tend to encourage behavior.
The poor have the most to lose from climate change, and therefore the most to gain - long term - from anything that helps mitigate it, which expediting the growth of the electric vehicle industry does.
Read your typical facebook feed, packed with "ur genious if you can solve this (grade 3) math prblem!" and the hundreds or thousands of comments getting it wrong.
.. to care deeply about security, the biggest derp I personally struggle with is the fact Chrome, in 2017, still isn't able to remember user-signed certificate fingerprints. It's bizarre.
I generally prefer Chrome to Firefox, but have to use the latter for most of my internal applications if I want any reasonable assurance that my SSL session is actually secure.
- Proper GNU utilities instead of whatever *box flavour they've used in the past
- Collaboration with the xposed team
- Package pinning
- Official Magisk/SuperSU support
- Toggle switch for Doze
- Safetynet override
- Proper SD/local storage volume management
- Renewed committment to community development
- Proper OS-level package management and forced integrator acceptance of Google security patches for continued access to the Play Store
- Outlawing (forced) locked bootloaders on new devices in exchange for access to the Play Store
These changes would ensure their continued dominance as a platform, as us powerusers/developers would have little desire to seek alternatives.
If you think exposed blades are bad, imagine what it feels like to hit by a car that was legally travelling 40mph within 3' of you, as a cyclist/pedestrian.
Getting hit by a 2lb plastic drone with spinning plastic propellers sucks. But let's try to keep risk assessment in perspective.
Slashdot Mirror
Android watches have one job, first and foremost:
They must work 100.0% of the time.
When you say "Ok, Google," it must respond every. single. time. Always. No matter what.
When you dictate a command, it must be interpreted quickly, and correctly, 100% of the time. None of this "Sorry, can't reach Google at the moment" garbage it currently replies with about 70% of the time.
Fix this first before addressing all the cutsie UI crap. Please!
Hopefully this three-way battle between Google, Amazon and Oracle will result in an opening a new mobile competitor can squeeze into. Android desperately needs some legitimate competition.
I was under the impression that tampering with telecommunications was illegal in Canada, punishable by imprisionment.
Can someone explain to be how these acts could be legally conducted?
.. between not supporting and actively blocking. If Google intentionally changed their code specifically to block Amazon's hardware, that is not okay.
So I'd been a Netflix customer and firm proponent since they went online. Not a heavy user, by any means, but I did enjoy shows at the gym, and I spread the gospel to anyone I met who still had legacy Cable TV.
About 6 months ago, Google added an option in the Play Console (for app developers) to exclude devices that fail to pass their so-called "SafetyNet" provisions.
Unfortunately, I and many others are unable to meet that requirement. "SafetyNet" isn't some simple checkbox agreement like "device modified; I know what I'm doing [Y]," but rather a set of secret scripts Google runs as root on your device to determine if Google has full control. Activities like patching security vulnerabilities, rooting, running AOSP, or even unlocking your bootloader disqualify you. The entire list of checks is, to date, secret. Their code updates happen automatically, in the background, without user control if you have the Play Store installed.
Once upon a time, the excuse for "SafetyNet" was that soon, Android devices could be used to pay for things. Fair enough. Just like my PC.. but it's mobile, so I guess different rules apply (?) ... I can use cash, or a credit card. Frustrating, but not a huge deal.
Of course that wasn't the end goal, as we've seen. The end goal was to discourage rooting, so that they could guarantee that their products (also known as users) would be forced to watch ads. Ad blocking is designed to be incompatible with "SafetyNet."
Lo and behold, back in June, Netflix started requiring "SafetyNet" certification in the Play Store. If your device doesn't qualify for any reason, you're excluded. Sideloading may still be an option, but I'm not sure.
Lucky for me, there are alternatives; I went to Amazon Video and YouTube, and cancelled my longstanding Netflix account. If the others follow suit, I will abstain from mass media and spend my money elsewhere.
Not everyone is willing to jump through such hoops though, and it's entirely possible this little stunt will bring back piracy from its death throes. All so that Google (and one day, surely, Netflix) could force more ads on us all.
Side note: yes I know Magisk can help. It's an arms race, for sure... but a great departure from what made Android successful in the first place.
Design a model of your laptop with the original IBM 7-row keyboard and trackpoint, and you've got a customer for life here!
Not a Mac fan, but this is the most honest, respectable response to a mistake I've seen from a corporation in a long time.
Props, Apple.
I am with Ajit Pai on this for the following reasons: private property owners must not be oppressed by any form of business regulations. That's my position on regulations.
I agree with you with one critical stipulation:
The abandonment of regulation must be a complete "atomic" transaction.
If the radio spectrum is suddenly a free-for-all, such that I'm able to erect and operate a 10,000W transmitter and establish my own Internet links, and rules governing access to established wirelines are abandoned so that I can use the dark fiber I paid for through previously collected taxes, then fine.
But the dissolution of regulation must happen all at once.
What's not okay is the removal of regulations on communication providers without the associated removal of privileges they enjoy.
I've never heard this perspective before. Interesting.
Let this be a lesson.
He's not some old guy who misunderstands technology, and he's not dumb.
This is an act of malevolence.
Senior systems architect of 20 years. Grew up on Solaris 2.6, Slackware, and have been an exclusive Debian user for the balance. Designed and built embedded flight controllers, vehicle dynamics processors, power controllers...
I am not smart enough to troubleshoot Windows issues. So give 'er a break.
.. and it would be immoral for them not to use and abuse them.
It's our fault that we are where we are, and we can hardly blame a company for gouging us while we sleep at the wheel.
No, not bitter at all.
Alongside net neutrality, laws should exist that dictate no owners of general technology devices can be artificially/intentionally restricted from accessing any part of their device.
I don't mean "thou shall include a JTAG port and dongle" .. I mean that it becomes illegal to import for commercial sale any device that the manufacturer/reseller has locked down for the sole purpose of excluding access to tinker.
Alcoholic, but nice try. :p
This succinctly summarizes what I've been trying to relate to others for quite some time.
"Active" security is generally treating the symptoms of poor quality software. selinux, "SafetyNet," virus scanners .. all of these things, while masking some issues, add code complexity and expose a larger attack surface.
Simple, clean, elegant, and obviously correct code (and that includes design) needs no complex "security" bolted on. It just needs to function as documented.
Retrain DEA agents to go after spammers.
You're missing the point entirely.
These tax credits aren't intended as help to the individual, so the individual's wealth status is irrelevant.
These tax credits are the reverse of taxation. Taxation tends to suppress behavior, where tax credits tend to encourage behavior.
The poor have the most to lose from climate change, and therefore the most to gain - long term - from anything that helps mitigate it, which expediting the growth of the electric vehicle industry does.
I'm an Apple / iPhone hater, but Google and Android desperately need some legit competition. This can only be good for the marketplace.
Read your typical facebook feed, packed with "ur genious if you can solve this (grade 3) math prblem!" and the hundreds or thousands of comments getting it wrong.
People are fucking dumb. :(
.. to care deeply about security, the biggest derp I personally struggle with is the fact Chrome, in 2017, still isn't able to remember user-signed certificate fingerprints. It's bizarre.
I generally prefer Chrome to Firefox, but have to use the latter for most of my internal applications if I want any reasonable assurance that my SSL session is actually secure.
... and now I feel old.
How about:
- Proper GNU utilities instead of whatever *box flavour they've used in the past
- Collaboration with the xposed team
- Package pinning
- Official Magisk/SuperSU support
- Toggle switch for Doze
- Safetynet override
- Proper SD/local storage volume management
- Renewed committment to community development
- Proper OS-level package management and forced integrator acceptance of Google security patches for continued access to the Play Store
- Outlawing (forced) locked bootloaders on new devices in exchange for access to the Play Store
These changes would ensure their continued dominance as a platform, as us powerusers/developers would have little desire to seek alternatives.
If you think exposed blades are bad, imagine what it feels like to hit by a car that was legally travelling 40mph within 3' of you, as a cyclist/pedestrian.
Getting hit by a 2lb plastic drone with spinning plastic propellers sucks. But let's try to keep risk assessment in perspective.
lol
I mean it's great that it can monitor your audio 24/7 and can make some nice numbers flash up in a benchmark and all...
But, uh.
Replaceable battery? Rugged/IP68? SD card slot? Headphone jack? You know.. things that actually matter?