LUKS header disk emergency destroy button? *boop!
LUKS header disk emergency destroy button? *boop!


Please, please make b/w mandatory by law


Potentially, searxng is running as vassal of uwsgi@emporer


IP/Name: 30p87.de
Key: YfXqz85PRidZ0NwMj3SAkFk5wypJPofTInbae9+mb1I=
All default setting, relay and server, free version.
Fuck all cults/“religions” anyway


I’m actively trying to move as far away from the desktop analogy as possible. Backwards.
Asked my ISP for a public IP, exposed all things that can handle that to the public. Custom Wireguard server for VPN


systemctl --user enable --now clicker.timer for a clicker sound every 15 minutes


just zoom out and go closer to the screen
When the server alone is idling at 200W
No wonder if you have three PMs at once


Well the really hard thing about SSL is sni maps, at least when working the first time with it and trying to debug it (especially with Thunderbird desktop which still wrongfully reports an invalid certificate 50% of the time. Click on refresh and it suddenly says it’s okie-dokie)
Friendly is useful in an application you use once a week. Anything you want to work with daily, like a text editor, needs to be efficient.
With worse you mean better


I have wasted weeks to months of time on postfix + dovecot, SSL, non-DUL IPs, spam, etc.
Yeah, with GECOS introducing the GECOS field, they normalized name verification, phone number verification, email address verification as well as location verification. So soon we should see those becoming mandatory and controlled.
Oh wait, that was 64 years ago, so by now we should already be in literally 1984, actually?! Or is it that no one actually gives a fuck about a handful of programs trying to read user data that no one set, and if they set it, set it to a nonsencial/false value without any component verifying anything?
The problem isn’t libraries adding more optional field to their capabilites, but management systems (such as a distros installer) making them mandatory against user will. That is what users should actually object to. No installer or component I know actually sets the location field. However, some are already planing to require the birth of date field, which is the actual start to pushing any boundaries. So start protesting there.
Or, if you actually think that simple standards for how user data is stored is already malicious verification, your only option is probably, unironically, TempleOS, as even DOS stores user information, Country + TZ, available for other programs to fetch.