Hacker News: dleeftink

New comment by dleeftink in "Qite.js – Frontend framework for people who hate React and love HTML"

dleeftink — Tue, 24 Mar 2026 10:17:08 +0000

Think Xstate[0] machines are a little more intuitive than the conditional value structuring displayed here in the example, but it is an interesting idea indeed.

[0]: https://github.com/statelyai/xstate?tab=readme-ov-file#super...

New comment by dleeftink in "Do not apologize for replying late to my email"

dleeftink — Wed, 11 Feb 2026 15:02:03 +0000

And still, we apologised ('I hope this find you well' and so on). It's cruft, it's slack, and it's social. We need some anchors to hang our message on. We know when it's necessary and when it isn't, and by breaking conventions we relay intent ('sorry not sorry').

New comment by dleeftink in "Mermaid ASCII: Render Mermaid diagrams in your terminal"

dleeftink — Thu, 29 Jan 2026 03:11:16 +0000

Pair this with Unicode plots[0] and you're set!

[0]: https://github.com/JuliaPlots/UnicodePlots.jl

New comment by dleeftink in "Scientists identify brain waves that define the limits of 'you'"

dleeftink — Mon, 26 Jan 2026 05:02:20 +0000

It's waves all the way down!

New comment by dleeftink in "The No Fakes Act has a “fingerprinting” trap that kills open source?"

dleeftink — Fri, 09 Jan 2026 14:53:37 +0000

That is not what I said. It is about signalling risks to developers, not criminalising them. And in terms of encoders, I would say it relates more to digital 'form' than 'content' anyways, the container of a creative work vs the 'creative' (created) work itself.

While both can be misused, to me the latter category seems to afford a far larger set of tertiary/unintended uses.

New comment by dleeftink in "The No Fakes Act has a “fingerprinting” trap that kills open source?"

dleeftink — Fri, 09 Jan 2026 06:35:38 +0000

I would say a text-based model carries a different risk profile compared to video-based ones. At some point (now?) we'd probably need to have the difficult conversation of what level of media-impersonation we are comfortable with.

New comment by dleeftink in "The No Fakes Act has a “fingerprinting” trap that kills open source?"

dleeftink — Fri, 09 Jan 2026 06:24:46 +0000

Which in case of digital replicas that can feign real people, may be worth considering. Not a blanket legislation as proposed here, but something that signals the downstream risks to the developer to prevent undesired uses.

New comment by dleeftink in "The No Fakes Act has a “fingerprinting” trap that kills open source?"

dleeftink — Fri, 09 Jan 2026 06:22:17 +0000

And I am talking about user-facing app development specifically, which has a different risk profile compared to automative or civil engineering.

New comment by dleeftink in "The No Fakes Act has a “fingerprinting” trap that kills open source?"

dleeftink — Fri, 09 Jan 2026 06:00:37 +0000

Not saying this would be the right way to go about preventing undesirable uses, but shouldn't building 'risky' technologies signal some risk to the ones developing them? Safe harbor clauses have long allowed the risks to be externalised onto the user, fostering non-responsibility on the developers behalf.

New comment by dleeftink in "The Post-American Internet"

dleeftink — Tue, 06 Jan 2026 07:45:10 +0000

In case bricks will be thrown, the response from the receiving party will likely skew to the argument presented here--circumvention of technical locks.

You'd catch the brick, sand it and repurpose so it'll fit your home.

New comment by dleeftink in "Total monthly number of StackOverflow questions over time"

dleeftink — Sun, 04 Jan 2026 04:40:08 +0000

Instead of having chat-interfaces target single developers, moving towards multiplayer interfaces may bring back some of what has been lost--looping in experts or third-party knowledge when a problem is too though to tackle via agentic means.

Now all our interactions are neatly kept in personalised ledgers, bounded and isolated from one another. Whether by design or by technical infeasability, the issue remains that knowledge becomes increasingly bounded too instead of collaborative.

New comment by dleeftink in "The Most Popular Blogs of Hacker News in 2025"

dleeftink — Sat, 03 Jan 2026 18:18:50 +0000

Network effect gaming or true interest? Which blogs have been overshadowed by the lucky few?

New comment by dleeftink in "Show HN: Dealta – A game-theoretic decentralized trading protocol"

dleeftink — Fri, 02 Jan 2026 19:49:50 +0000

If A could gain sufficient funds through expertise in one area (by way of validating contracts), could it feign/game expertise in area B by having enough funds to recoup the losses from disputes? Or would such a situation be prevented?

New comment by dleeftink in "Show HN: Dealta – A game-theoretic decentralized trading protocol"

dleeftink — Fri, 02 Jan 2026 16:22:56 +0000

> ensuring that only those with the right expertise remain

How will this ensure waning/gaining expertise is accurately represented/fostered? Wouldn't you rather attract a steady-stream of experts indefinitely?

New comment by dleeftink in "Google Opal"

dleeftink — Wed, 31 Dec 2025 05:51:38 +0000

If they store both the generated content and the eventual indexed location, they could now filter search results more comprehensively based on content hashes.

New comment by dleeftink in "Developing a Beautiful and Performant Block Editor in Qt C++ and QML"

dleeftink — Mon, 29 Dec 2025 09:33:05 +0000

Great write-up! It would be useful if various PKMs would settle on a similar format for recording (nested) tasks, dates and metadata, as it seems to have become the standard way to store kanban boards and similar 'enhanced' views. Currently there exist various strategies ranging from embedding JSON as comments to esoteric (non-markdown) formats, often trailing at the end of each task. This makes the source look cluttered and difficult to edit/navigate.

IMO, metadata (such as date ranges) could instead be stored as empty links leading each task (or by showing a custom placeholder symbol such as '@'), paving the way for a 'linked' data format while resulting in a same-width list for easy lookups and editing:

  - [x] [@](/2025/12/30..31.md (15:30:21)) task 1
  - [ ] [@](/2025/12/29..30.md (16:20:31)) task 2
  - [ ] [@](/2025/12/28..28.md (14:20:31)) same day task
    - [ ] undated nested task

For instance, the above tasks would link to the virtual '30..31.md' and '29..30.md' files which collect all backlinked tasks for the provided daterange (akin to Obisidan/Logseq/etc).

In an ideal world, the task marker could hold a custom symbol and linked metadata itself, but would result in non-standard (GFM) markdown:

  - [@](/2025/12/30..31.md (15:30:21)) task 1
  - [ ](/2025/12/29..30.md (16:20:31)) task 2
    - [ ] undated nested task

It would be up to the editor to render this metadata accordingly.

New comment by dleeftink in "You can make up HTML tags"

dleeftink — Mon, 29 Dec 2025 04:54:11 +0000

Good use case for @container, @scope and :has(), where you forgo class definitions and use --custom-properties on the parent scope/container which are inherited downwards based on the existence of a scoped DOM pattern/container query, or 'upwards' by using a :has(child-selector) on the parent.

Although be sure to avoid too many :has(:nth-child(n of complex selector)) in case of frequent DOM updates.

New comment by dleeftink in "Plugins case study: mdBook preprocessors"

dleeftink — Sun, 28 Dec 2025 10:18:30 +0000

For those in the JS/CSS/HTML ecosystem, paged.js[0] provides a comprehensive plugin or custom 'hooks' system to enhance CSS to print functionality. The maintainers have recently gone through a new round of FOSS funding and have also been more actively updating their journal in regards to the CSS @media print spec and their upcoming '2.0' polyfill[1].

[0]: https://pagedjs.org/en/documentation/10-handlers-hooks-and-c...

[1]: https://pagedjs.org/en/journal/

New comment by dleeftink in "Remove Black Color with Shaders"

dleeftink — Tue, 23 Dec 2025 07:54:41 +0000

Why not svg filters to create alpha channels? Seems to be supported by the library too (very useful btw!).

New comment by dleeftink in "Our new SAM audio model transforms audio editing"

dleeftink — Tue, 23 Dec 2025 05:56:39 +0000

I might misremember, but iZotope RX and Melodyne were pretty useful in this regard.