Joel @cincodenada@cybre.space

Also we all make our own risk calculations, but for the record here's what I looked like in this masked + vax/tested show, because COVID continues to exist.

Since I do my fair share of complaining about software design on here, here's a standout example of thoughtfully-designed software to balance things out.

BetterTouchTool is, among many other things, a hotkey manger/remapper, and is central to my effort to bend MacOS to my will and make it as Linux-y as possible.

One feature it has is changing how hotkeys are mapped depending on what application is focused. You do this by specifying various filters on several available window attributes, but knowing exactly what the values of those attributes are can be tricky.

So, when you have that configuration dialog open, there is a section at the bottom of the dialog that shows the value of all the available attributes for the window that is focused /at that moment/!

Today's #Semantle was pretty fun. Only had six of the top 100 (and nothing above 963) when I stepped back and triangulated a bit and hit on the answer

So I was closing tabs and realized I meant to post this chart in this thread about musical keys but forgot, so gonna post it here because it's a delightful "tag yourself" image on its own.

Still really enjoing #Semantle, enough that I polished up my little #userscript I've been toying with and threw it up on GreasyFork: https://greasyfork.org/en/scripts/441586-semantle-enhancements

So far it adds a cute little chart of your guesses for the day, and starts keeping history for your guesses in case you want to look back in the future.

We'll see how long it keeps my attention, but it does useful things now, so check it out if you're also playing. If you're not familiar with Userscripts, they're worth knowing about! I use TamperMonkey in Firefox to manage them, there are a few options out there, the homepage of GreasyFork (which is a place to share UserScripts) will point you in the right direction: https://greasyfork.org/en

As an example, here's the chart of my 51 guesses for today. Higher is closer, blue dots are guesses, green dotted line is the closest guess up to that point.

Just, ya know, making me some charts

Today was tricky, but I got lucky and had just enough information to stare at that third row for a bit and come up with the answer - and some post-game dictionary searching confirms that it is indeed the only possible word that would fit in the slot!

A fun one to puzzle out :D

Not every day you get to put up a PR with numbers like this. Here's to fixing the things that annoy you: https://github.com/sinonjs/sinon/pull/2426

A bit of a journey today, but delighted by my third guess, both for the word and what it got me

Tougher go of it today, and made my accessible Wordle renderer render an actual image because it wasn't working on my phone.

I should probably add a URL to the image but for now it works slightly better now at https://wordle.c9a.dev

Apparently I've done something to offend the chaos gods in charge of datestrings, because today I have to deal with DataDog's datestring parsing, which is significantly better, but has a glaring omission:

https://docs.datadoghq.com/dashboards/guide/custom_time_frames/#supported-syntaxes

I'm searching my logs in DataDog and went to paste in an ISO8601 datetime into their time range control, and was met with an angry red box.

For those not familiar, ISO8601 is the most straightforward datetime format, and is basically universally used in logfiles.

If you had to pick only one datetime format to use, it's probably this one! See also xkcd: https://xkcd.com/1179/

And yet, not only do they not have ISO8601, they accept no year-month-day formats at all, but do accept numeric month-day-year.

However, if you want to supply a specific time, your only options are a Unix epoch timestamp, or supplying the name of the month. You can't even say "1-1-2022 11:22 pm", it's gotta be "Jan 1, 2022 11:22pm".

Just...why!!

Trying out the first iteration of my Wordle image + description generator, because of course I couldn't leave well enough alone.

I went to post this and then spent another hour tweaking it, and now it is 3am and way past my bedtime. If you wanna play with it yourself, it's over at https://wordle.c9a.dev/

Anyway, this game is fun and I did good today (well, yesterday now, ssh)

Welp, @avocatto couldn't just let this one lie, and observed that with two-digit years, you've got Y2K problems, right?

You sure do. So I dug in: I figured they probably implemented the solution you use if for some reason HAVE to deal with two-digit dates (which they don't, but chose to anyway).

You just pick a number, and assume any dates before that number are 20xx, and after are 19xx. For something like JIRA where you're not really recording historical data, you can probably get away with this. You're not gonna have tickets opened before, like, 1980, maybe pick 1970 cause it's the epoch, there, you're future proof for 50 years.

So I went to test, and was surprised when 50 was interpreted as 1950...and a few astonished trials later: jimminy cricket on a bobsled, they chose nineteen-FORTY-TWO as the first year to assume is 19xx

I really, really wish I were making this up because I am at a loss as to how you even begin to end up here. Stumped.

Update: it gets worse!!

The placeholder text uses hyphens as separators, but the calendar control inserts slashes.

So what happens if you literally type in the suggested placeholder text? Surely they wouldn't suggest an invalid format?

If you guessed "of course they would" congratulations! You have the correct amount of faith in Atlassian's quality control! Blisteringly cursed software design, stratospheric levels of dgaf.

Bonus: yes, the placeholder dates are in January *2012*, and I would not be surprised in the least if that means this code hasn't been updated in over a decade.

Okay so I thought I had realistic expectations of Atlassian products, but they just keep finding new and appalling ways to surprise me.

At least the error message tells you exactly what kind of ass-backwards decisions they've made so you can adjust, I guess.

Okay fine I jumped on this bandwagon and yes it is good

Wordle 213 4/6

I had seen a couple folks' grids and knew this was gonna be a tough one, so I took some gambles early, and it paid off. Spent a long time staring at that last row, so pretty happy that it paid off!

A successful launch! Bon voyage, JWST! Save travels on your next million miles, may your unfurling proceed apace.

Have you ever wanted something so bad you just...took it?

#hardware #motherboard

I'm a little annoyed at the fact that https://www.npmjs.com/package/logitall exists in the first place, but I'm even more annoyed that I am using it because there's good reason for it to exist. I shouldn't have to be glad this exists!!

I know async is hard and good backtraces are hard, and phew stepping through async code in #javascript can just be an exercise in futility sometimes.

So yeah, sometimes the literal best thing to do is just log a message to the console for every damn line of code you run.

*rubs hands together, cackling maniacally*

Haha yes....YES!!!!