I’m in this comment and I don’t like it.
I just finished up a ~700 line PowerShell script to send input/keep a login session from timing out due to inactivity, and prior to that was a Python script to format LetsEncrypt SSL certs in a way haproxy likes + an accompanying Bash script to make sure those certs are correct, check in the current good haproxy config to a git repo, and then restart it if there are new certs.
The only thing that I know is that I know nothing.
Before I replace it with something that won’t catastrophically collapse when the wind blows the wrong way, I get some sort of sick satisfaction out of doing autopsies on the house-built-of-matchsticks “solutions” that users come up with and I don’t know why. Some of them are truly fascinating and make you wonder how someone could possibly arrive at that conclusion based on what they were actually try to achieve.
It’s also why if I’m asked to implement something, my first question isn’t “When does this need to be done?,” it’s “What exactly is the problem you’re trying to solve?”
What a user asks for and what they actually need very rarely intersect.
Seriously, it feels like 1999 internet. And I’m loving it!
56K modem handshake sound intensifies
They really don’t, though. Inclusion/exclusion operators work most of the time, but it’ll still return results with explicitly-excluded keywords. It also fucks up results by returning entries with similar words to your query, even when you double-quote a part of the search term. Advanced queries that use booleans and logical AND/OR don’t work at all anymore, that functionality has been completely removed. It returns what it thinks you want, not what you actually want, even when explicitly crafting a query to be as specific as possible.
I use Kagi for search now and it’s 1000x better, especially when researching technical issues; it’s like when Google actually respected your search terms and query as a whole.
Don’t fuck with me, I know a Dodongo when I see it.
BTW, any authenticator app works when it tells you to use one. They all use a standard, so it doesn’t matter which one you use.
Eh, it’s a little more nuanced than that, there’re more standards for MFA code generation than just TOTP.
And even within the TOTP standard, there are options to adjust the code generation (timing, hash algorithm, # of characters in the generated code, etc.) that not all clients are going to support or will be user-configureable. Blizzard’s Battle.net MFA is a good example of that.
If the code is just your basic 6-digit HMAC/SHA1 30-second code, yeah, odds are almost 100% that your client of choice will support it, but anything other than that I wouldn’t automatically assume that it’s going to work.
I was on reddit before the digg exodus
Man, I remember when that shitshow happened. It was like reddit’s version of Eternal September.
Hockey is definitely the sport helped the most by HD video.
D. All of the above
You know, it’s surprisingly vague even in the official documentation.
You just described literally all of Lemmy’s documentation.
I had to read the source code for Lemmy to find out what API endpoint to hit, how it worked, and what to expect on return for a script that I was writing. You need to do that for some documented API endpoints as well. Calling it “vague” is a nice way to put it.
Exactly. Freedom of speech != Freedom from social consequences
Sorry, I missed this comment. I actually love doing that kind of shit, I get some sort of weird pleasure out of fixing chaotic stuff like that. That tends to be my role almost all the time; I’ll come in, stay a few years, fix everything and get bored, and then move on somewhere else to do it again.
My current job is the only place that I haven’t done that, because it’s probably the best company that I’ve ever worked for.