I'm assuming you're referring to the VingCard vulnerability from 2018? (https://www.bbc.com/news/technology-43896360)

Digital locks aside, this is more applicable to any lock you buy and rely on (substitute US with your local region):

> lack of availability in the US

I wouldn't go out of my way to find something like Schlage here, when Abloy (Assa Abloy) locks are available in abundance with locksmiths able to duplicate usually all the key variants.

I can link my secondary bank account to my main bank's app so I can see the balance in one place, but the catch is that I need to refresh this authorization through the app every 90 days.

Ideally, you'd just use your banking credentials to authorise the API access and pull data through that. What this requires in practice, I have no idea but it probably involves a bit of bureucracy.

Micro/nanoplastics are a secondary consideration overall, primary was just to reduce my usage of plastics a bit, even how infinitesimal it really is. I only realized how much plastic packaging I go through once I moved to an apartment with plastic "recycling", I still separate out most plastics but not everything.

I personally am not really swayed towards ditching whatever plastics I still have, given how ubiquitous it is and I am already happy with my Ikea glassware.

I was taught the procedure of disconnecting a 10/20kV disconnect for an on-site transformer (alas, only an old one that had been decommissioned) and that thing scared the crap out of me when I first heard the spring loaded high voltage disconnect actuate.

Having a 3 meter fibreglass pole to actuate the thing, just incase, tells you there is a real risk of the thing blow up in your face, on a good day.

Calling out Flipper Zero for someone (ab)using the meter's remote control features cuts me the wrong way: you could've done the same with any other SDR, not just the Flipper Zero.

It's not even a surprise this happened, the cut-off is not meant to be operated constantly to cut heavy loads. Similarly you should not use a breaker to turn off heavy (or any, in that matter) loads as you're needlessly wearing down the protective device, instead of a separate cut-off switch that's designed to be replaceable. Especially since it can be positioned downstream from the protective device.

It all boils down to which part of the circuit you can easily repair in case of a fault, in this case the meter is by far the least accessible.

Incidentally, while testing on Windows (in both WSL and cmd.exe) with a Finnish layout: you do not need a space after typing out the tilde.

Sometimes the lane guidance also likes to pick up on the destinations from the overhead signs, trying to pronounce the Finnish and Swedish names with less than stellar results.

For me personally, Signal will turn into a messaging app among dozens of similar apps, of which I have enough already. SMS was why I stuck with Signal over the years I used it and now I have no real reason to stay on it.

* hajimari - https://github.com/toboshii/hajimari

Autodiscovery based on Kubernetes Ingress objects is a really nice feature: you configure the details using labels (name, icon etc.) in case the Ingress is not exactly what you want.

For more on Docker's built-in chains, see: https://docs.docker.com/network/iptables/#add-iptables-polic...

While hosted GitLab might make use of a transparent pull-through cache (as I've gathered from glancing at relevant parts of the docs), you can benefit a lot by using one with your own local GitLab instance (assuming it does not already provide it via container registry).

We ended up switching to Harbor[1] from the vanilla registry and almost by chance stumbled on the fact that it supported a pull-through cache from various other sources (including Docker Hub).

This was especially useful after we hit the rate-limit after one of our pipelines got out of hand and decided to rebuild every locally hosted Docker image (both internal and external).

[1]: https://goharbor.io/

Idea was that you could "grep" by specific text in the subtitles and automatically create a clip of every occurrence of the text (by looking at the subtitle timing and padding that in both directions).

The biggest source of my frustration was that I was unable to get the clipping to work exactly as I wanted, where the start or end of the clip would seemingly drift back and forth. That was until I realized it boiled down to how the different seek modes in ffmpeg handled keyframes.

I still haven't gotten the clipping to work exactly as I want but I figured doing two passes might be the way to go: first pass would do a fuzzy match and ensure there is enough extra on both ends of the desired clip and the second pass could re-encode the fuzzy-matched clip to shuffle the keyframes around, allowing more accurate clipping.