Citation needed?
Google explicitly stated the exact opposite of what you've said here: Google Drive Terms of Service
kae
joined 1 year ago
It's articles like this that make me glad there are numerous horses in the race.
Autonomous driving is an incredibly complex problem. We have people like Musk who thought they could throw money at the problem and have it solved in a few years, with disastrous results.
We've lost Uber, and Cruise is flagging. Both had been touted as examples to follow. Both have had some serious safety problems from moving too quickly and lacking caution.
Behind all of this is Waymo. Plodding along, gathering vast amounts of data and experience and iterating slowly.
I think they, out of all these players, understand the stakes at hand, and the potential profit on the other end. But you have to get it right. It has to be nearly perfect, because people need to trust it, and our emotions are fickle.
Or, and hear me out here, they heard that the investigative committee was set to release their findings in 2 weeks, and wanted that process to work itself out first.
For the needs you described, you want to go with power efficiency. Check to make sure your quicksync version can handle h265, and you'll be fine
I'm genuinely confused how this is a thing. How are people rapidly pressing the power button 5 times in rapid succession without being aware of what they're doing?
Now adding a 3 second press after those 5 presses is solving the problem? Mine as well go back to opening the phone app and dialling the number.
For those late to the party, this is a day old already. The drivers have been pulled, pending an update.
To be fair, it seems that AMD is intercepting, modifying, and injecting code. That's not a false positive, that VAC working as intended.
What's wild is that AMD didn't have a conversation with Valve before releasing this. You can't go messing with someone else's code, particularly in such a highly competitive game, and not expect to screw some things up for players.
More specifically, it is enabled in the dev builds, but not in the user builds at this time.
Hook, line, and sinker? No. But Pixel Pass was a money thing, this promise is a brand thing.
Most people didn't know Pixel Pass exists. They drop this promise, and I guarantee you your grandparents will know about it. It's a brand killer kind of moment.
All I'm saying is the scales tip in favour of them holding this up. We're on the 8th generation of Pixel phones now. Generations 4&5 we're rough, but they stuck it through when it would have been easier to walk away.
This is a great move for Google, and goes beyond the minimum of what they needed to do. That's a huge step forward for them, Pixels, and Android as a whole.
Right from the first Pixel, Google was seeking (for better or worse) to take a bite out of Apple's pie. They've largely been successful in that. Without Google entering the fray, it would only be Samsung left.
They've elevated the hardware expectations of Android devices. Pushed the envelope of software integration. Shown that a bloat free experience is preferable and possible for the consumer (even though many here on Lemmy want a Google free device, that is a different discussion).
Now they didn't merely match other OEMs, but exceeded their updated promises by years.
Android isn't going anywhere. This is a pillar of their company now, and Pixels are a key part of that strategy. If Google dumped making Pixels, the whole Android ecosystem would be in doubt, because who would make phones if the maker itself doesn't believe in them? Google, by jumping into the fray, has moved from a platform provider to a pillar of the hardware ecosystem.
So despite all the cynicism, which is justified for all but their core software, this promise has teeth. If they don't follow through on this, we're likely seeing the demise of Google as a company, not just the Pixel line.
The gating of a lot of the software features and UWB are really disappointing in the non-pro 8. I'd love a smaller phone, but they really do push you to the big one if you plan on keeping it for any length of time.
Even the pre-order bonuses are only for the larger phone.
Need more places calling them out on this.
Yes, it talks about ownership, because the original poster talked about ownership.
Google hosts files, and thus needs to have some semblance of control over what actually is hosted on it, or they become liable for the same content.
Pirated material? Child pornography? etc. It all needs to be scanned and determined if it violates rights/laws and be dealt with.
Google has always done this automatically, because the sheer scale of content they host is overwhelming.
I totally understand the 'own everything' mentality that some hold. That's fair -- then host it yourself, encrypt it, and you can hold the key to your little kingdom. For most people, that isn't a factor.
To get back to the original claim -- they don't claim rights over what you post. It is yours. You just can't host other people's stuff. The definition of that is incredibly broad and largely commercial. 99% of people will never, ever run into the issue. 99% of the remaining 1% will discover it innocently (such as another poster trying to back up office). The remaining will already be versed enough to encrypt their data locally before uploading.