That's what I am doing too, though I did have to drill out some wall to fit it, in some cases.
There is another option that I don't think many people are aware of: You can put a battery powered relay downstream of the (dumb) switch, and have it broadcast events when power comes on and off, to control other smart devices, which just have to listen for the events (via a broker like HA).
Yeah, I don't think it bears out that DOM operation invocations constitute a major bottleneck for a lot of web applications. Certainly the execution of those operations (like layout invalidation and calculation) can be expensive, but those would not benefit. I can't think of applications with a massive amount of DOM calls that would benefit from lower latency.
The difference is if you are actively filming, or the camera is set up to film by itself. Security cameras are in the latter category and therefore can only be used on your own property (you can allow someone else to do it on your own property, such as a security firm).
An important distinction is that you are allowed to film/photograph when you are actively doing it (so the glasses do belong in that category). You're not allowed to set up a camera to autonomously film/photograph outside of your own private property.
Besides that there is the issue of publishing said footage, as others point out.
> you are allowed to film/photograph when you are actively doing it
Does it really count as "actively doing it" when the glasses are constantly filming while you do other stuff.
With a phone/camera people can see you are filming or taking pictures.
In many countries the shutter needs to make a sound when taking pictures.
For video surveilance cameras a noticeable sign or sticker is needed.
If Motorola releases a flip phone with GrapheneOS I'll order it on day one. I wanted one the last time I upgraded but I wanted GrapheneOS and there's no flip Pixel (only a foldable).
Same one for five years (Samsung Flip 3). It does have a crack down the middle. It's not enough to bother me, but you're right, early gens do have that problem (believe it is fixed by now).
Also, current tech could be useful as a shopping assistant, to carry the groceries for people who can't, for one reason or another. Though the other post about tipping safety does have a point.
Well, it may consume the AI environment. Maybe even the internet. It's not going to consume a PC with g++, though (at least if the PC doesn't update g++ any more once g++ starts accepting AI contributions).
There may come a point where having a "survivor machine" with auto-update turned off may be a really good idea.
I already do this, in the form of survivor machines made to do initial coding on a retro platform so the result will translate across all possible platforms. Got to, as I'm an Apple coder primarily, so if I want to target older machines I can only do it through a survivor machine: support is always pruned out of Xcode and it would be insane to try and patch it to keep everything in scope.
There is another option that I don't think many people are aware of: You can put a battery powered relay downstream of the (dumb) switch, and have it broadcast events when power comes on and off, to control other smart devices, which just have to listen for the events (via a broker like HA).
reply