Nathan Knowler

I'm the type of person who loves open source not because I can use it for something, but because I can learn something from it.

gosh, iCloud Mail is annoying… first as of recently supporting dark mode, I noticed it's sending all my emails with white text even in light mode… then when I try to resend something, it changes the email I'm sending with.

Pair that a shadow DOM template for the interest target, anchor positioning, and you've got a pretty powerful dynamic popover solution without using a framework.

A potentially useful pattern depending on the fate of Interest Invokers is using a single interest target for multiple interest sources, then leveraging `beforetoggle` to fill the content of the target based on the source.

My condolences to anyone with a windshield this morning.

I love how people who use X occasionally pop up in Bluesky/Fedi wanting people to act "normal" about AI, meanwhile they're totally acting normal about Nazis and CSAM.

album.link/ca/i/1876304...

*Dransfeldt

you should talk to Cory Dransfedlt www.coryd.dev

Here’s @kizu.dev’s article: kizu.dev/cyclic-toggl...

(I have used this technique in production for multiple jobs now)

This repo is very experimental, but this is the general idea:

Setting state custom property with selector: github.com/knowler/doom...

Applying styles based on state: github.com/knowler/doom...

What I like to do is set some “state” custom properties with the selectors that match that state (e.g. `--button-state`), then use something like @kizu.dev’s cyclic toggles or, eventually `if()`, to apply the styles.

😂 I’ve always set up my default search queries to filter it out of my results.

I wish I could filter the bullshit and slop web. I miss when I could look up something and find a web page that was genuinely architected to share careful acquired knowledge and not for SEO.

too dim?

inset: unset

Not yet… 😏

No Problem Mail eXchange

Anyway, I might drop a blog post about my involvement later… today or this week. I hope I didn't jinx it.

There's a lot of work to do—more than I can do alone—and I've been very grateful for a whole bunch of people who have helped push code when I couldn't or who have taken the initiative to improve the accessibility themselves. The only way to do this is as a community.

Trying to manage accessibility on a project like this has been kinda like drinking water out of a firehose. 😅 Luckily, it's slowing down as we have a clearer understanding of what it is that we're building. And I don't have a job anymore so I've got a lot more time (sponsor me, maybe?).

npmx - Package Browser for the npm Registry a fast, modern browser for the npm registry. Search, browse, and explore packages with a modern interface.

I've had a whirlwind of a morning and totally missed all of the npmx alpha launch stuff, but, uh ya, come check out what we're building and maybe get involved if you feel inclined. I've joined as a maintainer with a focus on accessibility.

npmx.dev

The boulder is easier to push up the mountain with others at your side. Community education seems to be a good way to do it, though I think the fruits of that have yet to be realized in this situation. Nevertheless, I’m glad there is optimism about it.

I do want to be completely transparent that there are accessibility issues and some more glaring than others (e.g. non-text contrast, default search behaviour on input, a number of incorrectly coded controls), but it is refreshing to not constantly feel like Sisyphus.

“Bob and 835 of your other colleagues are playing Zip. Join in on the fun.”

A row of square arches made of snow on a frozen river under a blue sky.

It's fair to say that I should not be made responsible of code formatting. Every extra space or new line, missing quotes in attributes is a reminder of the unforgiving future that could have been (XHTML). Let the grace of HTML embrace you(r code).

Thank you, Stephen!

Light theme… that’s what my sunglasses are for /j