Google's tasks and reminders are seemingly two separate DBs.
Google Assistant, Keep, Inbox, and Calendar use the reminders DB. The new Gmail and Tasks use the other. Why in the holy hell these two are separate is maddening but as long they remain so it severely gimps both. Whatever Assistant defaults to should be what everything does.
Why the hell should a fish tank thermometer have any sort of network access to where customer data is stored? Their IT staff should be re-vetted for competence.
I know I know, it may sound really out there: don't form your voting decisions based on what you see on Facebook? It's an ad platform, not journalism.
First: Qubes OS. https://www.qubes-os.org/
Second: Regardless of IT staffs' intention, management makes the final decision to let the systems be locked down. In many cases, they don't.
I have clients who struggle filling positions. When I inquire, I find it's never that there aren't applicants, just not applicants of sufficient quality. And in those cases, when I ask how much more they're offering for the position above market rates, they all look at me with bewilderment.
Also that unemployment rate? Manufactured horesehit. http://www.shadowstats.com/alt...
If someone is smarter/stronger/faster/etc they are your superior by definition. Egalitarianism is a myth.
Using words to convey one's thoughts and emotions has become too challenging.
Outsourcing data storage is innovation? Client/server architectures are novel?
What could possibly go wrong?
I remember a militaristic superpower lying to its own citizens about hidden weapons, metal tubes, babies being pulled from incubators, etc all to start a $1T+ war. Same guys.
Show me proof or fuck off.
This isn't messing with your thermostat, it's interfering with remote access back to it when you're gone. Something I'm pretty sure 99% of us can't do now anyway and for the 1% who do, lack a substantial need.
We want companies to secure our data and face significant hardship when they fail.
No, this is still a huge fuckup.
- deploy OS updates w/root bug
- release 20017-01 security patch that fixes root bug but introduces Kerberos authentication bug
- release KB that provides instructions for manually fixing Kerberos bug by entering terminal command
- patch the 2017-01 security patch to not introduce Kerberos bug
And now...
A shit show.
And then within 24 hours Security Update 2017-001 is auto applied if not manually done so earlier.
Opportunities are usually disguised as hard work, so most people don't recognize them.
