7,006 karma · joined December 12, 2014
https://mattkeeter.com
Right now, I'm targeting everything (native / Firefox / Chrome / Safari), so minimizing use of extensions; this also means I get to run head-long into fun cross-platform behavior differences [1][2][3]
[1] https://github.com/gfx-rs/wgpu/issues/8785
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1870699
[3] https://github.com/mkeeter/halfspace/issues/1#issuecomment-3...
[1] https://doc.rust-lang.org/reference/dynamically-sized-types....
(This also happens at the SSD level: burst writes can be very fast as data is buffered in the SSD's own RAM, then performance steady-states at the true write speed once that's saturated)
At the time, they posted "Flowise isn’t going anywhere, we’re doubling down. In fact, we’re only just getting started!" [2]
I wonder if "keep the platform running for >= 1 year post-acquisition" was part of the terms! Ah well, another one for Our Incredible Journey [3]...
[1] https://newsroom.workday.com/2025-08-14-Workday-Acquires-Flo...
[2] https://www.linkedin.com/posts/flowiseai_were-thrilled-to-sh...
oh hi Claude
https://github.com/search?q=A%20Mini%20Shai-Hulud%20has%20Ap...
edit: For what it's worth, I also just tested the Gettysburg Address (using the "Bliss Copy" from [1]), and got a "100% Human" score.
[1] https://www.abrahamlincolnonline.org/lincoln/speeches/gettys...
GPTZero gives it a 100% chance of being AI generated, and I've found that these tools may give false negatives from a well-prompted model, but false positives are rare.
If you are looking to tune your intuition for AI-written text, here's an interesting list of their quirks (ironically provided as a Claude skill for removing those quirks from emitted text):
https://github.com/stephenturner/skill-deslop/blob/main/refe...
[1] https://stateofutopia.com/papers/2/intermediate-report.pdf
(We had one back in December; you’re in for a fun ride!)
It also seems to have a physics engine, a slicer for 3D printing, an embroidery mode, and a entire ecosystem of math crates (https://tang.toys/).
Whether any of that works – or whether it's pure LLM slop – is less clear. I tried to import a trivial STEP file, and it crashed my browser tab [1]. Every commit is co-authored by Claude.
https://news.ycombinator.com/item?id=47110801 (13:23:08)
This is an absolute clown show.
Edit: whoops, this was incorrect! I had received over 1,000 Zendesk emails, 168 of which made it into my inbox.
The giveaway is that LLMs love bulleted lists with a bolded attention-grabbing phrase to start each line. Copy-pasting directly to HN has stripped the bold formatting and bullets from the list, so the attention-grabbing phrase is fused into the next sentence, e.g. “Potential for abuse Attestation enables blacklisting”
Lots of projects, ranging from embedded systems to DIY CAD software and GPU algorithms.
Is there any reason to believe this isn’t an AI-assisted crank publication?
For what it's worth, this changed in v0.33.0:
> jj undo is now sequential: invoking it multiple times in sequence repeatedly undoes actions in the operation log.
(release notes: https://github.com/jj-vcs/jj/releases/tag/v0.33.0)
It's at least partially a matter of timing: Oxide was picking its initial hardware in roughly 2020, and the RP2040 wasn't released until 2021.
A handful of people have done ports, e.g. https://github.com/oxidecomputer/hubris/pull/2210, but I expect to stick with STM32s for the foreseeable future – we've got a lot to do, and they're working well enough!
"No manual overrides, no exceptions."
"Our VDP isn't just a bug bounty—it's a security partnership"
The "secret sauce management layer" is available at https://github.com/oxidecomputer/omicron, released under the MPLv2 license.
(I work at Oxide)
https://artemis.sh/2022/03/14/propolis-oxide-at-home-pt1.htm...
(The author of this blog post now works for Oxide!)
This is taken directly from the paper's introduction, which admittedly uses the more specific terminology of "1-Lipschitz signed distance bounds".
The paper cites the original Hart '96 paper on sphere tracing; quoth Hart, "a function is Lipschitz if and only if the magnitude of its derivative remains bounded".
https://graphics.stanford.edu/courses/cs348b-20-spring-conte...
I wonder if there's a terminology schism here between computer graphics and numerical analysis folks.
You may also enjoy "Spelunking the Deep: Guaranteed Queries on General Neural Implicit Surfaces via Range Analysis", which uses interval arithmetic (ish) to raymarch neural implicit surfaces:
By analogy, you wouldn't program in LLVM IR, but it's a useful intermediate representation for a bunch of higher-level languages. Higher-level tools can target this representation, and then they all get to use a standard set of optimizations and algorithms (fast evaluation, rendering, etc).
(I gave a recent talk that's a broad overview of this research: https://www.youtube.com/watch?v=UxGxsGnbyJ4)
> My next thought would be to evaluate the program at a low resolution to create a low res SDF texture for the shader to draw at a higher resolution.
Glad you're enjoying the challenge! You may also be interested in