Hacker News: wky

New comment by wky in "P99 0 ms* autocomplete for 240M domain names"

wky — Mon, 31 Aug 2026 15:02:22 +0000

> If supported by a user agent, this event MUST be dispatched when a key is pressed down [...]

https://w3c.github.io/uievents/#event-type-keypress

New comment by wky in "P99 0 ms* autocomplete for 240M domain names"

wky — Mon, 31 Aug 2026 06:31:17 +0000

This raises the question of why real life buttons and virtual buttons behave differently. My unsubstantiated guess is that clicks act on release to give the opportunity to slide off the button to abort, and/or because the button would disappear while pressing if it ex. submits a form.

New comment by wky in "P99 0 ms* autocomplete for 240M domain names"

wky — Mon, 31 Aug 2026 06:18:05 +0000

Holding a key would indeed require both on key down and up. I'd still argue that handling rerender on key down (or to fully match whatever OS/browser semantics, oninput) makes more sense than key up. Pressing Ctrl+V for example produces feedback as soon as "V" is pressed, not when Ctrl and/or V is released.

Interestingly Ctrl+V on OP's website does update immediately when Ctrl+V is pressed.

New comment by wky in "P99 0 ms* autocomplete for 240M domain names"

wky — Mon, 31 Aug 2026 05:01:12 +0000

They do that, yet proceed to kneecap the perceived latency by delaying the render.

> And on keyUp (the user releases the key), we render the suggestions.

New comment by wky in "P99 0 ms* autocomplete for 240M domain names"

wky — Mon, 31 Aug 2026 04:34:18 +0000

The perceived latency starts from keydown, not keyup. Redefining latency to start at keyup reduces measured latency, not perceived latency, and delaying the visual display to keyup makes perceived latency strictly worse, not better. Even sticking with the keyup definition, just displaying the result as soon as it is available gives the possibility of negative (defined) latency.

New comment by wky in "Show HN: Needle2: 14MB agentic LLM for phones, wearables, smart home and robots"

wky — Tue, 11 Aug 2026 15:02:55 +0000

Specifying units seems to be unreliable; I tried adding a description to the set_thermostat temperature:

    "temperature": {
      "type": "number",
      "description": "degrees Fahrenheit"
    },

Set the living room temperature to 70 degrees Celsius

    {
      "function_calls": [
        {
          "name": "set_thermostat",
          "arguments": {
            "room": "living room",
            "temperature": 70,
            "mode": "cool"
          }
        }
      ],
      "confidence": 0.6045
    }

Set the living room temperature to 70 degrees Fahrenheit

    {
      "function_calls": [
        {
          "name": "set_thermostat",
          "arguments": {
            "room": "living room",
            "temperature": 70,
            "mode": "heat"
          }
        }
      ],
      "confidence": 0.4536
    }

Set the living room temperature to 70 degrees

    {
      "function_calls": [
        {
          "name": "set_thermostat",
          "arguments": {
            "room": "living room",
            "temperature": 70
          }
        }
      ],
      "confidence": 0.8517
    }

Trying "in degrees Fahrenheit" for the tool description had similarly counterintuitive confidences.

Edit: to be clear, the counterintuitive behavior is that the confidence ended up higher for the wrong units.

New comment by wky in "Show HN: Needle2: 14MB agentic LLM for phones, wearables, smart home and robots"

wky — Tue, 11 Aug 2026 14:50:08 +0000

Considering it as a classification problem, you could use a representative set of example queries, feed them to this model, then ask a "smart" language model to assess each query + result for whether the result is actually correct. Then you have a dataset you can compute FPR and FNR for any given threshold, and score based on the context, ex. turning the lights on or off is a lot less important if it is right compared to whether your door is locked. You could even pick it based on the tool call itself: Low threshold for locking the door, high threshold for unlocking the door.

New comment by wky in "How Blackwing Pencils are Made [video]"

wky — Mon, 10 Aug 2026 14:43:47 +0000

The main thing that helps with lead breakage is a mechanical pencil with a sliding nose cone/tip. Even finer lead becomes fairly reliable as long as it is protected against sideways pressure. My personal favorite is the Kuru Toga Advance 0.3mm, though a larger lead size and a model purpose-built for break-resistance would be better if tip breakage is the main concern.

New comment by wky in "The Difference Between a Button and a Link"

wky — Wed, 29 Jul 2026 01:48:04 +0000

Additionally, the proposal of button actions is for the opposite purpose, when you want to avoid sending the form data when the button is pressed.

New comment by wky in "Lore – Open source version control system designed for scalability"

wky — Wed, 17 Jun 2026 15:48:43 +0000

The link to Architectural Decision Records is empty, but they're present in the repo to look at[0]. Curiously the decision with the most deciders is the implementation of JavaScript bindings[1].

[0] https://github.com/EpicGames/lore/tree/main/docs/developing/...

[1] https://github.com/EpicGames/lore/blob/main/docs/developing/...

New comment by wky in "A greyscale iPhone setup that works in everyday life"

wky — Sun, 14 Jun 2026 06:16:43 +0000

Zoom's filter applies before Color Filters, so a workaround is to toggle on zoom, set it to greyscale, then use the 3 finger gesture to zoom out to 100%.

New comment by wky in "Show HN: Verso – A $14.99 Mac word processor with no subscription"

wky — Sat, 13 Jun 2026 18:22:00 +0000

From the comparison image it looks like the goal is functional compatibility, not render compatibility. The table borders change and the layout changes.

New comment by wky in "A low-carbon computing platform from your retired phones"

wky — Sat, 13 Jun 2026 16:55:38 +0000

There are countries that require published material to be submitted to a national archive[0]. A similar system could be done for software source code and made public on expiry.

[0] https://youtu.be/ZNVuIU6UUiM

New comment by wky in "A low-carbon computing platform from your retired phones"

wky — Sat, 13 Jun 2026 14:25:18 +0000

The closest thing would be our showcase poster[0], at some point I might write about the thought/development process (both for my sake and whoever picks up the project in the future)

[0] https://docs.google.com/presentation/d/1jsJ5euZ4VXcwL4fbgJKM...

New comment by wky in "A low-carbon computing platform from your retired phones"

wky — Sat, 13 Jun 2026 13:38:48 +0000

This is neat. This group’s approach of treating the devices as many weaker servers (basically a raspberry pi cluster) sounds like the most realistic way to reuse phone hardware at scale, especially with the backing of the actual hardware vendor.

It’s a genuine shame how locked down iPhones are compared to even Android. Hypothetically you could run Linux inside UTM[0] but outside the EU Apple makes it intentionally difficult, and there’s still memory restrictions and performance penalties.

My group’s senior year project was a computing cluster on phones (specifically targetting LLM inference) [1]. Instead of installing a new OS we built separate apps per OS. Our devices were older, so the Android phones had worse hardware and the iPhones had more software restraints.

[0] https://getutm.app/ [1] https://github.com/orgs/rmcluster/repositories

New comment by wky in "Should you normalize RGB values by 255 or 256?"

wky — Mon, 01 Jun 2026 22:38:50 +0000

It doesn't even need to represent intervals. A 13 inch ruler with 13 markings at 0.5, 1.5, etc inches is still a valid ruler, albeit an odd construction.

New comment by wky in "Ruby vs. Java vs. TypeScript: my experience on building a Cowork DOCX plugin"

wky — Thu, 28 May 2026 15:35:54 +0000

Golang has the golang.org/x packages, which avoids too much stdlib bloat while still providing the niceties of “pre-vetted” packages that don’t pull in a massive dependency tree.

New comment by wky in "Canvas is down as ShinyHunters threatens to leak schools’ data"

wky — Thu, 07 May 2026 22:31:05 +0000

It's possible that Instructure's servers got compromised:

dig canvas.ucdavis.edu

    [...]
    
    ;; ANSWER SECTION:
    canvas.ucdavis.edu. 1974 IN CNAME ucdavis-vanity.instructure.com.
    ucdavis-vanity.instructure.com. 60 IN A 18.173.121.125
    ucdavis-vanity.instructure.com. 60 IN A 18.173.121.103
    ucdavis-vanity.instructure.com. 60 IN A 18.173.121.15
    ucdavis-vanity.instructure.com. 60 IN A 18.173.121.18

dig canvas.duke.edu

    ;; ANSWER SECTION:
    canvas.duke.edu. 300 IN CNAME duke-vanity.instructure.com.
    duke-vanity.instructure.com. 60 IN A 18.173.121.125
    duke-vanity.instructure.com. 60 IN A 18.173.121.18
    duke-vanity.instructure.com. 60 IN A 18.173.121.103
    duke-vanity.instructure.com. 60 IN A 18.173.121.15

Nationwide security breach involving Canvas

wky — Thu, 07 May 2026 20:25:10 +0000

Article URL: https://ucnet.universityofcalifornia.edu/employee-news/nationwide-security-breach-involving-canvas/

Comments URL: https://news.ycombinator.com/item?id=48054449

Points: 5

# Comments: 1

New comment by wky in "Texico: Learn the principles of programming without even touching a computer"

wky — Mon, 04 May 2026 15:28:50 +0000

As a heads up, NHK tends to remove videos from their site, probably due to contract stuff. It seems Texico starts expiring next year. Sometimes they “rebroadcast,” but for peace of mind make sure to download a personal copy.