It makes sense for security cameras to be secure. Hacked security cameras are a big issue. Motorola investing in partnering with a more secure OS seems aligned.
Same question. Electricity and logistics are really the only physical barriers. With solar and a single mini split couldn't you essentially prevent heat death with some very high probability?
Freezing to death in winter should be a harder problem at this point right?
Electricity and logistics solve the heating just as well. You can use the same device if you want to. Heat pump is just an AC run in reverse, literally all you need is a little valve to reverse the flow.
They work just fine until -25C or so. (COP around 3). After they they still do work you just fine but work effectively as resistive heaters as you approach COP of 1.
Obviously you need a model they is made for which winters but people use them all over Finland including Lapland without any issues. If you want to save some money on the coldest days you burn some wood in the oven/fireplace if you have one.
edit: heat pumps (both air and ground) have been very popular in the nordics for quite some time now. One big reason is that we have cheap electricity and very expensive oil/gas. Lately also municipal level central heating networks have been slowly moving to heat pumps as their source of heat.
"It includes claims that Hof was sentenced in 2012 by the Amsterdam magistrates court to community service and a fine for assaulting Caroline’s oldest son, then 18. The Amsterdam court confirmed that Hof went before the magistrates court in 2012 and was given a sentence of 40 hours of community service and fined €350.
Enahm Hof said the domestic violence conviction related to “a single incident involving Caroline’s son, adult at the time, for which Wim Hof expressed regret and offered an apology. Wim clarifies that no physical violence occurred, but a struggle, which nonetheless should not have happened.”
that "no physical violence occurred, but a struggle" is an oxymoron for me. maybe no physical injury...
I'm currently looking to piece together a kubernetes native "forge" and there are major gaps in the ecosystem. Why do we need everything in one application like every single "forge" claims to be? What about when I want something that's not supported.
How about Forge compatible components? Or forgeables? Naming is hard but hopefully you get the point...
I'm an expert, I'll go to harbor freight and weld some stuff together. It will still break down in 5-10 years but maybe I will at the very least have some control over the way I pivot.
Honestly I think I am already sold on AI, who is the first company that is going to show us all how much it really costs and start enshitification? First to market wins right?
> patched an Encrypted DNS Server to store the original TTL of a response, defined as the minimum TTL of its records, for each incoming query
The article seems to be based on capturing live dns data from some real network. While it may be true that persistent connections help reduce ttl it certainly seems like the article is accounting for that unless their network is only using http1.0 for some reason.
I agree that low TTL could help during an outage if you actually wanted to move your workload somewhere else, and I didn't see it mentioned in the article, but I've never actually seen this done in my experience, setting TTL extremely low for some sort of extreme DR scenario smells like an anti pattern to me.
Consider the counterpoint, having high TTL can prevent your service going down if the dns server crashes or loses connectivity.
This article does a good job of calling attention to the pattern.
If you work in powershell you can start out in the terminal, then when you've got whatever you need working you can grab the history (get-history) and write it to a file, which I've always referred to as a `sample`. Then when it becomes important enough that other people ask me about it regularly I refactor the `sample` into a true production grade `script`. It often doesn't start out with a clear direction and creating a separate file is just unnecessary ceremony when you can just tinker and export later when the `up-enter' pattern actually appears.
I had the same thought but unfortunately even if that translation is accurate it could still be bidirectional hallucinating and would not really be sufficient evidence...
It's another reformulation rather than a true proof. Now, instead of wanting a proof of a theorem, now we just need to prove that this proof is actually proving the theorem. The proof itself being so incomprehensible that it can't on its own be trusted, but if it can be shown that it can be trusted then the theorem must be true.
Well I think this is a great step forward but it would be great if we could mix aspect ratios even better...
Consider a similar layout to OP but the landscape images will span multiple columns as well as everything it already does.
The thing about masonry is that it adapts to the size of the images. You could already do masonry using flexbox if you know the image sizes (https://github.com/hannasm/masonflexjs). Doing it as a true mosaic layout would be a step above current capabilities. At that point it's probably pretty easy to create configurations that don't fit perfectly/ require lots of empty space to layout nicely though.
You could always interpret a variable from the perspective of it's memory address. It is clearly variable in the sense that it can and will change between allocations of that address, however an immutable variable is intended to remain constant as long as the current allocation of it remains.
