antonok

Earendil's own Gondolin tool is the best sandboxing model I've found so far. It just executes the toolcalls in a minimal ephemeral VM, unlike most others which run the whole harness inside the sandbox. It's a bit rough around the edges (doesn't play well with other plugins and doesn't work under Bun), but it's great if you're willing to put in some effort to tweak your setup. Much more comforting to fire off long-running parallel tasks when you know the blast radius is fully contained lol.

I've noticed that toggle sets a local storage entry, but the value of it doesn't appear to matter at all for new tab loads. I hoped it's "just" a UI bug, but some agent-driven reverse engineering of the page should reveal the answer, as well as how intentional it was.

OpenCode has been great in my experience. I still get the best results using it with Anthropic's models, but some of the open weights ones are catching up (GLM 5 works reasonably well for me).

I had the same thought too. It's probably not too difficult to fine-tune a small model for it using the "introduce a random mutation and describe the issue" workflow from TFA

rillian was also instrumental in helping to integrate Rust into Chromium at Brave. I worked with him for a few years; since getting to know him, I started noticing his handle in the contributors list across a surprisingly diverse range of other open source projects. RIP, Ralph.

fwiw, LEDs with higher CRI will generally be less power efficient, so the premium category has a 3-way tradeoff between brightness, power, and color quality. It's common for high efficiency LED lightbulbs to be much worse at illuminating red objects.

You're probably thinking of Adblock Plus? Acceptable Ads is their program; EasyList has no such policy or ties.

FlatBuffers was definitely the majority of the improvements here!

On 64-bit systems, pointers themselves can really start to take up a lot of memory (especially if you multiply them across 100k+ adblock filters). Switching to array indices instead of pointers saves a lot of memory that's otherwise wasted when you don't need to address the entire possible memory space.

I opened an issue based on the discussion here and it didn't take much time or effort.

(It was one of those form-based issue templates that requires you to explicitly list out Steps to Reproduce, Expected behavior, Actual behavior, OS version, etc. which IMO causes slightly more friction for anyone who knows how to put together a good bug report, but I've also seen enough poorly-specified issues to know that it's necessary sometimes)

I'm using a non-standard port (above 10000). Otherwise, nothing special about my configuration. Perhaps 51820 is blocked?

It is admittedly quite slow/intermittent though; I wouldn't be surprised if that's the reason it didn't look like it was working for you.

Funnily enough, I'm on a British Airways flight right this moment. I'm only using a basic Wireguard tunnel after enabling the free messaging plan. I get the sense they didn't design the firewall to block everything comprehensively.