HNHacker News
TopNewBestAskShowJobs

190n

30 karma · joined January 20, 2026

submissionscomments
190n··on Neki – Sharded Postgres
They removed that line from the blog post:

https://web.archive.org/web/20260516145550/https://planetsca...

https://web.archive.org/web/20260910204345/https://planetsca...

190n··on A safe MySQL upgrade that wasn't so safe
I don't understand why this issue only appeared after the upgrade, not immediately after the migration to add the column?
190n··on Anthropic's ‘watermark’ text adulteration in Claude is a perversion of writing
> And if you copy-paste the answers from LLF, I think it's only fair the end result gets flagged. You're not writing it yourself.

I wonder if it would even get flagged in that case, because wouldn't the probability distribution of a token when the LLM is suggesting an edit to your writing be different than the distribution of that token once it is in the context of the text it's editing?

190n··on Bun.Image
> It's not like image manipulation is a poorly understood problem

You would think, but the initial implementation of this stripped ICC profiles (https://github.com/oven-sh/bun/issues/30197), and while that was fixed in time for the release, it still currently doesn't understand EXIF rotation metadata (https://github.com/oven-sh/bun/issues/30235) or high-bit-depth images (https://github.com/oven-sh/bun/issues/30462)

190n··on Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc
Almost all of Bun's tests are written in JavaScript run in Bun itself.
190n··on Darkbloom – Private inference on idle Macs
> PT_DENY_ATTACH

All you have to do is attach to the process before it does that, and then prevent this call from going through.

190n··on Claude Code's source code has been leaked via a map file in their NPM registry
It could be because of a Bun bug, but I don't think it's because of that one. It's a duplicate of a year-old issue, and it's specific to Bun.serve.
190n··on Flash-MoE: Running a 397B Parameter Model on a Laptop
> *2-bit quantization produces \name\ instead of "name" in JSON output, making tool calling unreliable.

I was wondering about that statement. Shouldn't it restrict sampling to only tokens that produce valid JSON matching the schema during a tool call? On the other hand, I have heard a lot about how even production LLM providers don't always call tools accurately, so I suppose either it's hard to implement what I described or there's something I haven't thought of that makes it impossible.

190n··on Our commitment to Windows quality
Later in the post they expand on that point:

> More direct control over updates, including the ability to pause updates for as long as you need

So it does sound like you'll be able to pause updates forever and also therefore not automatically reboot.

190n··on 10% of Firefox crashes are caused by bitflips
Operating systems use less RAM than Firefox.
190n··on The fix for a segfault that never shipped
I thought I had read this story before, and it seems like a similar account was published to this company's blog in 2023 but since taken down: https://web.archive.org/web/20250624191934/https://www.recal...

Still a good read though.