[ my public key: https://keybase.io/sigio; my proof: https://keybase.io/sigio/sigs/W-Ro0IScNveaQpMbvTlIuVZPOO8mUKYX6KwW60eXx-0 ]
meet.hn/city/51.9966792,4.5597397/South-Holland
Yup, instant nope here (That and not having a browser addon, passwords in the browser is 99% of my password-use).
All other stuff is mostly SSH keys / ssh-agent.
Yes, I admit, this is 100% vibecoded, but it scratches an itch i've had for a while. Seems to work for my usecases at this time, but might add some more features in the future.
I've bought 14kwh of anker solix max ac for €3900, and added 2 zendure 800 plus's for €320 each (1.9kwh + 2 solar mppt ports each).
It's all connected and managed through homeassistant.
In the Netherlands (and the rest of western europe), we have hourly and quarterly energy pricing (opt-in), next to pricing plans that have one or two fixed tariffs during the day/year.
I quite like the quarterly pricing, for example today the home-battery charged for 3 hours during the cheapest time (13:00 - 16:00), and discharged again for the most expensive hours (19:00 to 21:00), and kept my house's grid-input at zero for the rest of the day.
Feeding back a few kwh's during the most expensive hours gives me a big kickback, making electricity use for the rest of the day mostly free. (Since there is usually a 150-250% price difference between cheap and expensive timeslots).
So, this won't work on any regular bike that has a fender, which is most 'regular' bikes people would use for city-driving/daily commutes. (At least in area's that get rain occasionally.
Why do people even install 'drivers' for things like monitors. (Or usb devices running 'standard' protocols). The OS handles these just fine by itself.
You can even put it in a seperate zone (which I do) by using a CNAME for _acme-challenge.domain.tld.
I have it to a seperate subdomain, which is served by a seperate desec.io account, which is only used for this specific subdomain.
My setup is having a wildcard DNS record and a wildcard certificate for my 'home' domain. It has a fixed IP from my ISP, so you always end up on haproxy, which then forwards to individual ports/ip's in the internal network.
I can do filtering based on source-ip from there, so traffic from myself/internal will be allowed, and outside traffic (not from some allowlisted ip's) will get blocked.
ACME validation is done via DNS, so nothing needs to be accessable for that to issue certificates. Internally I will usually also use the public IP for services, so no need for a split-dns.
I'd love to see more OpenWRT hardware that was capable of 2x2.5, 2x5 or 2x10gbit without any wifi, preferably in a case that can be rackmounted without too much trouble (so keeping it under 1U height). I'm currently running a stack of Zyxel T5600's, which are quite capable arm64 openwrt boxes. Those in a rackmount but with sodimm support or in 8+GB ram versions (and some sata/nvme storage, USB3) would be amazing.
That, or the massive lightning that's going through the region, (due to the heatwave). Since it's quite late at night, heat wouldn't be my first guess.
Don't know if this is a regression from before, since in the RHEL 5/6 days I used XFS filesystems as my default filesystem on large storage-pools. Since XFS doesn't have a shrink option, I would create filesystems of a few gigabytes in size, and grow them whenever needed. I mostly used them for monthly archiving of uploads to a customer's website, so there would be a YYYY-MM lvm volume with an XFS filesystem, and during the month it would be grown automatically from a cronjob if space got tight.
I'm quite sure I must have had a bunch of full filesystems there, and never ran into any crashing issues with full XFS filesystems (though these were not the 'root' filesystem). But even on my current laptop (with debian 12/13) I'm running XFS on all filesystems (besides /boot and /efi), and they report being full often enough without any crashes/reboots.
While it would be nice, I think this would instantly write-off the car in UK and western europe, as various connected features not working on cars that came with them, or are 'new enough' to require them, cause mandatory yearly tests (MOT / APK(NL)) to fail, meaning you can't legally drive the car again until these are fixed and re-tested.
Yeah, my main reason to stay away from Keepass, everything is in a single versioned binary file. I like 'passwordstore.org', where every secret is it's own gpg-encrypted textfile in a git repo. Every change is a commit, easy to see history, easy to revert or know which version is newest. And easy to selfhost, you just need a place to git push/pull from.