Hacker News: stefan_lec

New comment by stefan_lec in "DKIM2 and DMARCbis Have Landed"

stefan_lec — Wed, 08 Jul 2026 22:10:29 +0000

Sounds pretty cool! I wonder if it closes enough holes that we could finally stop using SPF at all?

New comment by stefan_lec in "98% isn't much"

stefan_lec — Wed, 08 Jul 2026 13:18:20 +0000

I’m a bit skeptical of the accuracy of the traffic data claimed in this article, 30% of users not being able to use baseline widely available features is a suspiciously large number. Unless this is a very unique set of users, I doubt that it is accurate. Maybe bot traffic messing up the data?

For context, baseline widely available requires that your browser have updated at some point in 2023, which happens automatically for almost all users. For mobile devices, any device that supports Android >= 7.0 or iOS >= 17 would meet this requirement. Chrome even supported Windows 7 through Feb 2023, too.

According to this: https://www.digitalapplied.com/blog/mobile-os-market-share-2...

* iOS >= 17.0 covers 95% of global active iOS devices

* Android >= 7.0 covers at least 99% of global active Android devices

It seems reasonable to me to drop support for Windows XP, IE, and phones that are a decade or more old (iPhone 8, Galaxy S5). And if you claim to be supporting stuff that old, but you don’t test your site on it, you’re just kidding yourself.

You have to draw the line somewhere.

New comment by stefan_lec in "Why are there so many canines in fine art?"

stefan_lec — Thu, 11 Jun 2026 01:36:17 +0000

Because they couldn’t get the cats to pose obediently for the artist?

New comment by stefan_lec in "SpaceX launches Starship v3 rocket"

stefan_lec — Sun, 24 May 2026 21:06:13 +0000

Biggest things changed are the plumbing inside the booster (much beefier, now supports starting all engines at once), and a new version of the engines, raptor v3 (more robust, and saves about 1 ton of mass per engine).

Cool image comparing the three versions of the engine. In addition to making the engine itself a bit lighter, moving all that stuff to the inside of the engine let them eliminate a whole bunch of heavy shielding in the engine bay.

https://ibb.co/pr0gx688

New comment by stefan_lec in "SpaceX launches Starship v3 rocket"

stefan_lec — Sun, 24 May 2026 20:54:59 +0000

Yeah, the new raptors and engine bay redesign for version 3 of ship seem a lot more robust than version 2, very impressed that the ship finished its mission so well.

Scott Manley goes into quite a bit of detail on analyzing superheavy’s failed boostback, it’s a good watch:

https://youtu.be/2kxanBYTAaY

TL;DR - seems like the hot staging kicked the booster out in the wrong direction, and the ship’s plume impacted one of the grid fins, which would’ve given it quite a big kick. The sloshing just from that could easily have caused the observed issues.

New comment by stefan_lec in "Moving away from Tailwind, and learning to structure my CSS"

stefan_lec — Sun, 17 May 2026 03:06:25 +0000

Details/summary had quirky/inconsistent handling by screen readers for quite a while after it reached full browser adoption, unfortunately. Not even sure if they’ve fixed it here in 2026, honestly.

https://www.scottohara.me/blog/2022/09/12/details-summary.ht...

While it’s good to use well-implemented semantic elements when possible, there are still plenty of places where either the built-in browser behavior isn’t actually very accessible (like native form validation), or where you just can’t avoid it (using aria-disabled instead of disabled for submit buttons, setting aria-pressed for toggle switches, setting aria-expanded for buttons that trigger modals, situations where you need aria-hidden/sr-only, etc).

Though once popovers and the invoker command api hit baseline widely available, we’ll be able to drop some of that.

New comment by stefan_lec in "Moving away from Tailwind, and learning to structure my CSS"

stefan_lec — Sun, 17 May 2026 02:34:28 +0000

This is nonsense, you can stick classes on semantic HTML elements just as easily as on a div.

And screen readers can handle elements nested inside a grouping div just fine, that’s how div’s are supposed to be used. The accessibility issues with div’s are when people repurpose them to take the place of existing semantic elements, because doing so requires handling a bunch of aria roles and attributes manually, and something invariably gets missed.

New comment by stefan_lec in "Moving away from Tailwind, and learning to structure my CSS"

stefan_lec — Sun, 17 May 2026 02:25:05 +0000

This is not true. Tailwind defaults to rem as the underlying length unit for almost everything. You have to go to extra effort in most cases to use px.