wky

5 ms·

1.
by wky 6d ago
This reminded me of such good memories of playing with http://weavesilk.com/ . Nice to see someone with a similar concept.
2.
by wky 6d ago
A mentally simpler, though slightly biased algorithm is for each item, randomly generate a uint64 (arbitrary bit size) and switch to the new item if and only if the number generated is greater than or equal to all previously seen numbers. T
3.
by wky 9d ago
Is there an advantage over just --guest?
4.
by wky 12d ago
What I find strange about RFC2119 is technically RFC8174 amends it, yet the amended text never seems to be used.
5.
by wky 14d ago
It wouldn’t surprise me if AISLE uses many different providers’ models, and what’s holding back OpenAI and Anthropic is only using first-party models. Just because OpenAI and Anthropic have arguably the strongest models overall doesn’t mean
6.
by wky 16d ago
> 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
7.
by wky 17d ago
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
8.
by wky 17d ago
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 pr
9.
by wky 17d ago
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.
10.
by wky 17d ago
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 st
11.
by wky 1mo ago
Specifying units seems to be unreliable; I tried adding a description to the set_thermostat temperature: "temperature": { "type": "number", "description": "degrees Fahrenheit&qu
12.
by wky 1mo ago
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
13.
by wky 1mo ago
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 Advan
14.
by wky 2mo ago
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.
15.
by wky 3mo ago
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/E
16.
by wky 3mo ago
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%.
17.
by wky 3mo ago
From the comparison image it looks like the goal is functional compatibility, not render compatibility. The table borders change and the layout changes.
18.
by wky 3mo ago
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
19.
by wky 3mo ago
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/presenta
20.
by wky 3mo ago
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 ve
21.
by wky 4mo ago
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.
22.
by wky 4mo ago
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.
23.
by wky 4mo ago
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
24.
Nationwide security breach involving Canvas(ucnet.universityofcalifornia.edu)
5 points by wky 4mo ago|1 comments
25.
by wky 5mo ago
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.
26.
by wky 5mo ago
This post has managed to “confuse” Google about the reverse question as well (“who named teresa t whale”): The humpback whale known as "Teresa T" was named by Simon Willison in September 2024. Background: The juvenile humpback wh
27.
by wky 5mo ago
There’s a relatively obvious constraint to check here: compositing the layers back together should produce a (near) identical image. Would it not be preferable to throw an error if the model fails to faithfully segment the image?
28.
by wky 5mo ago
Interesting that it’s paying to remove features. Seems reasonable considering it’s paying to get an officially supported build, and if you’d rather not there’s probably a fork doing the same out there. Edit: That it’s free (as in WinRAR?)
29.
by wky 5mo ago
Relatedly, scrolling time pickers are also a toss up on mobile. Sometimes a single swipe on the minutes gets you from 12:00pm to 11:50am, sometimes it doesn’t. I wish the analog clock picker where two quick taps set the hours and minutes (a