diftraku
Merely losing the sun behind cloud cover for an extended period of time seems to have an effect if not the quite gradual but rapid shortening of available daylight. When the weather reports start including how gray it is today, you know it's the season again.
Increasing your vitamin D3/D6 dosage and being exposed to bright blue light daily helps most people to get through the winter.
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.
Works surprisingly well for my use-case (keep work stuff separate on Element) and even allows me to disconnect completely from work by simply turning off the profile.
[1]: https://github.com/PeterCxy/Shelter
Edit: added note about using Android
Using email as an example, having to transfer email with drag'n'drop in something like Thunderbird is clunky, slow but works to a degree.
Having direct access to the mailbox directory on the filesystem would make it easier to transfer out/in (assuming you already have your emails in the same format).
A quick google does suggest that at least one person has tried using ZeroSSL with Traefik: https://spad.uk/get-free-zerossl-certs-using-traefik/
- Rolling stock is owned by HRT
- Transport Infrastructure Agency (Väylävirasto) is responsible for the tracks and stations
Which means the bid is mainly for personnel operating the trains.
There were couple companies that placed bids for this, most of them withdrew before the end of the call, essentially leaving one competing bid along with VR's (then and now current operator).
In the end, nothing changed and VR still operates the trains using HRT's own rolling stock. The only real change going forward are the plans to have a dedicated maintenance depot for HRT's own stock, since VR does not want to have the burden of maintaining stock they don't directly own.
At least with freight, it's going to be different... right?
While not outright ads, the usability survey keeps pestering for feedback, I do not have much faith in Ubiquiti having any tact left to not pester for the recommendation feedback as well.
There's a good selection, it's pretty varied and there's no shortage of em (assuming you don't exceed 100-200 new systems in a 3 year period). This also has an accidental side-benefit of not being tasked to name new hosts at work, unless your really want to call the new database server Stufful, for example.
Another thing to keep in mind with more descriptive hostnames like `database`, is to serialize them from the start. It's a very minor thing but after you have three hosts with one of them missing the serialization, it's going to stand out like a sore thumb and it could be a major undertaking on changing that name where it's used.
When it comes to project names, there is a certain level of permanence that name (or codename) is going to have. Once chosen, that name will be thrown around in the codebase almost universally. The same does apply to the hostnames, at least in part when it comes to configuration files (and by extension, certain hard-coded hostnames that could linger around in the code years after the host in question has been decommissioned).
The major reason behind this is mainly due to how MobilePay integration was done with the card terminals over here in Finland: you need bluetooth (or in some cases, a camera to read a QR-code) to start the payment transaction. I believe this is primarily due to Apple restricting the use of NFC to Apple Pay (and other first-party apps).
Another big reason is that my bank has native support for adding cards to Google Pay through their own app.
I do still use MobilePay very often over my bank's own transfer app (Siirto). MobilePay was one of the first ones to the market (if you exclude the app/card scheme Elisa had a few years ago, currently owned by Aktia) and is still faster than asking for someone's IBAN.