gapple

Feeling pretty vindicated in holding onto those old USB cables now that I'm building some microcontroller projects

@shane@hachyderm.io about as far away as you can get within the same country

I was worried my neighbours might think I'm too weird, but one of them has now befriended and named a family of crows

Should I have known that dereferencing a Pinia store getter unwraps computed refs and you lose reactivity? 🤷

A problem I cause myself with learning is that I start with something fairly ambitious, and then when things break I'm not sure if I fucked up something basic because I skimmed over that part

"adjusts regex patterns for clarity and security"

I tried out the LLM commit message feature added to my IDE to see what it would generate, and it always adds something like "Did [X] to improve features and maintainability"

So I think it's pretty clear that it doesn't actually understand the code.

I really hadn't expected to ever use that fluid dynamics course, that I took just for credit requirements in university, ever again

the parts for a different project arrived first, where I'm instead *detecting* a blinking LED

Learning how to make an LED blink

(Really fast - prototyping a controller for some PWM fans before I get the rest of the parts)

To the six people immediately installing the latest, pre-release, version of my #drupal module:
ILYSM 💙

🤞 no bug reports so far

Yesterday's bug was properly determining when morning routines should start based on my usual wakeup time, or an alarm if one is set. Except that apparently (months ago) I didn't account for going to bed before midnight, which caused my morning and evening routines to cycle, flickering all my lights 🤦

Home automation is fun, because I get to experience what it's like to be haunted by a ghost.

Except the ghost is my past self writing bugs in my Home Assistant templates.

Maybe the most exciting feature to me since release 1.6 in 2019? It's something I've wanted for a long time, but wasn't actually sure it would be possible until a few months ago when the pieces came together - while looking at how Big Pipe handles caching with placeholders to make sure it could work with nonces safely, it also showed how to work around core's strictness for what can be added to attached properties.

Attaching policy directly to render elements should make it a lot easier for many use-cases than implementing an alter event subscriber, and will limit changes to the policy header to only pages where they're needed.

New feature for #drupal Content Security Policy module 2.1 that I'm so excited about:

Attaching policy to render elements!
https://www.drupal.org/docs/extending-drupal/contributed-modules/contributed-module-documentation/content-security-policy/altering-a-sites-policy#s-attaching-to-render-elements

Currently in beta release, stable will happen soon.

@hankgreen 🤞hopefully it helps your new favourite coffee shop thrive from a larger local community to support it