Hacker News: kaelwd

New comment by kaelwd in "A new spam policy for "back button hijacking""

kaelwd — Tue, 14 Apr 2026 06:02:53 +0000

And if the tab was unloaded then you press back it changes the URL but not the actual contents of the page.

New comment by kaelwd in "A new spam policy for “back button hijacking”"

kaelwd — Tue, 14 Apr 2026 05:47:00 +0000

Can I preventDefault on mouse5? What about the physical back button on Android?

New comment by kaelwd in "Why Switzerland has 25 Gbit internet and America doesn't"

kaelwd — Mon, 06 Apr 2026 11:25:07 +0000

Australia did that but also paid out the telecom companies a gazillion dollars for infrastructure that had only been privatised like a decade earlier.

New comment by kaelwd in "The Appalling Stupidity of Spotify's AI DJ"

kaelwd — Sun, 15 Mar 2026 10:42:57 +0000

What would you add to MP3 tags? ID3v2 already has separate fields for section/title/performer/conductor/composer/lyricist, it isn't the spec's fault Spotify doesn't use them.

New comment by kaelwd in "Mozilla is working on a big Firefox redesign, here is what it looks like"

kaelwd — Fri, 06 Mar 2026 12:35:43 +0000

Looks kinda like https://github.com/nuclearcodecat/shimmer

New comment by kaelwd in "Coding assistants are solving the wrong problem"

kaelwd — Thu, 05 Feb 2026 09:12:35 +0000

"Make all the tests pass"

"Ok, I've deleted all the failing tests"

New comment by kaelwd in "The Overcomplexity of the Shadcn Radio Button"

kaelwd — Wed, 21 Jan 2026 06:42:13 +0000

Straight up doesn't even register clicks or keyboard focus for me in firefox.

New comment by kaelwd in "Databases in 2025: A Year in Review"

kaelwd — Mon, 05 Jan 2026 11:15:43 +0000

From discord:

> There has been a ton of interest expressed this week about potential community maintenance of Gel moving forward. To help organize and channel these hopes, I'm putting out a call for volunteers to join a Gel Community Fork Working Group (...GCFWG??). We are looking for 3-5 enthusiastic, trustworthy, and competent engineers to form a working group to create a "blessed" community-maintained fork of Gel. I would be available as an advisor to the WG, on a limited basis, in the beginning.

> The goal would be to produce a fork with its own build and distribution infrastructure and a credible commitment to maintainership. If successful, we will link to the project from the old Gel repos before archiving them, and potentially make the final CLI release support upgrading to the community fork.

> Applications accepted here: https://forms.gle/GcooC6ZDTjNRen939

> I'll be reaching out to people about applications in January.

New comment by kaelwd in "PNG in Chrome shows a different image than in Safari or any desktop app"

kaelwd — Sat, 27 Dec 2025 17:23:20 +0000

GIMP asks if I want to keep or convert the color profile but both options look washed out. The only thing that opens it "correctly" for me is MPV.

New comment by kaelwd in "Using Git add -p for fun (and profit)"

kaelwd — Sun, 14 Dec 2025 15:30:31 +0000

You get light grey? The headings are #101828 and body text #364153 on #0a0a0a for me.

New comment by kaelwd in "Valve: HDMI Forum Continues to Block HDMI 2.1 for Linux"

kaelwd — Thu, 11 Dec 2025 03:25:17 +0000

That's only 60Hz though. Are there any dumb TVs with 120+ Hz VRR and HDR?

New comment by kaelwd in "CSS now has an if() conditional function"

kaelwd — Sat, 06 Dec 2025 11:39:23 +0000

That's the same as regular css variables unfortunately

    padding: 1em;
    padding: var(--padding);

With no fallback value that resolves to padding: unset if the variable is not defined. The only ways I know of to work around this are style queries:

    padding: 1em;
    @container style(--padding) {
      padding: var(--padding);
    }

Or cascade layers:

    @layer base {
      padding: 1em;
    }
    @layer override {
      padding: var(--padding, revert-layer);
    }

New comment by kaelwd in "Shai-Hulud Returns: Over 300 NPM Packages Infected"

kaelwd — Mon, 24 Nov 2025 11:05:13 +0000

Everyone needs to switch to pnpm and enable https://pnpm.io/settings#minimumreleaseage

Pnpm also blocks preinstall scripts by default.

New comment by kaelwd in "Nearly all UK drivers say headlights are too bright"

kaelwd — Tue, 18 Nov 2025 14:44:46 +0000

Luckily that's illegal in my country, instead we have the opposite problem where new cars have LED taillights that are just as blindingly bright as their headlights.

New comment by kaelwd in "Drawing Text Isn't Simple: Benchmarking Console vs. Graphical Rendering"

kaelwd — Wed, 12 Nov 2025 04:31:42 +0000

The author of that issue has a whole video series about it: https://www.youtube.com/watch?v=hxM8QmyZXtg

A way faster terminal emulator demo: https://github.com/cmuratori/refterm

And a terminal rendering benchmark tool: https://github.com/cmuratori/termbench

New comment by kaelwd in "Trump pardons convicted Binance founder"

kaelwd — Fri, 24 Oct 2025 16:27:46 +0000

California would have to split into 68 separate states to have the same representation as Wyoming.

New comment by kaelwd in "Why do we need MAC addresses?"

kaelwd — Wed, 08 Oct 2025 13:11:46 +0000

> Can we not just have a UUID that the device generates?

They kinda are already, your phone probably uses a random MAC address for each network it connects to.

New comment by kaelwd in "Pnpm has a new setting to stave off supply chain attacks"

kaelwd — Fri, 19 Sep 2025 08:40:13 +0000

The chalk+debug+error-ex maintainer probably would have noticed a few hours later when they got home and saw a bunch of "Successfully published" emails from npm that they didn't trigger.

New comment by kaelwd in "DuckDB NPM packages 1.3.3 and 1.29.2 compromised with malware"

kaelwd — Tue, 09 Sep 2025 15:15:03 +0000

NPM could also flag releases that don't have a corresponding github tag (for packages that are hosted on github), most of these attacks are publishing directly to NPM without any git changes.

New comment by kaelwd in "DuckDB NPM packages 1.3.3 and 1.29.2 compromised with malware"

kaelwd — Tue, 09 Sep 2025 15:10:52 +0000

Versions with a serious vulnerability should be deprecated by the maintainer which then warns you to use a newer version when installing. Yes if a npm account is compromised the attacker could deprecate everything except their malicious version but it would still significantly reduce the attack surface by requiring manual intervention vs the current npm install foo@latest -> you're fucked.