Yeah, inductive charging is basically a must.
Especially because it eliminates the guesswork if the watch is correctly seated to charge
Yeah, inductive charging is basically a must.
Especially because it eliminates the guesswork if the watch is correctly seated to charge
No actual technical solution here, but it smells slightly of XY-Problems.
From what you described it seems the main issues are
Maybe you could look into solutions like setting a custom ringtone for important callers or having the phone announce caller names so your mother can decide if she wants to make the effort to get her phone.
I’m speculating a bit here but I can imagine that getting up and answering the phone is exhausting for your mother. Also if her mindset is " a ringing phone means it’s important" that could make it even more stressful.
Maybe you could find a way to let her silence all calls except caregivers and ICE contacts. (On Android DND exceptions could work for that)
That way she doesn’t feel pressured to answer the phone every time it rings and stays reachable.
If it’s actually just the physical issue of reaching the phone in time, does she have a convenient way to carry the phone indoors like a lanyard?
Hope some of this helps you
Ah, you “work” in “marketing”?
To a certain degree, yes. If someone at Google decides to wage all-out war against ad blockers they have a good chance. But if that costs more money than it generates, odds are that someone will stop it. Google / Alphabet is publicly traded after all and that means profit above all else.
Embedding ads into the stream would be hard to counter, but it’s far away. That would invalidate caches along the way and need extra performance to reencode the stream with the ads inserted.
That’s extra costs that are hopefully orders of magnitude above the lost ad revenue from ad blockers
I run a 2 node k3s cluster. There are a few small advantages over docker swarm, built-in network policies to lock down my VPN/Torrent pod being the main one.
Other than that writing kubernetes yaml files is a lot more verbose than docker-compose. Helm does make it bearable, though.
Due to real-life my migration to the cluster is real slow, but the goal is to move all my services over.
It’s not “better” than compose but I like it and it’s nice to have worked with it.
Very neat idea, but I’d explicitly add strong encryption to that method, cars do get broken into.
I’d encrypt every off-site backup, but a car is a bit more exposed than a rented safe box.
They should not be worried, they should be educated.
If you worry a new user enough they’ll go back to Windows or Apple because there’s less scary warnings there.
We need to make the transition as pain free as possible. Learning about the joys of kernel compilation and SELinux can come later.
The first step is "Hey, this is as usable as Windows, without stupid ads in the start menu.