Stagnant

The problem doesn't exist when granting codex full access. Codex makes you choose upon first launch to "Set up default sandbox" or to "Use non-admin sandbox". The default option creates two new users and messes with NTFS permissions.

NVIDIA-Nemotron-3-Ultra-550B-A55B was released in June 4th 2026 and I think it was the largest open US model until thinking machines' Inkling (975B) was released a couple of weeks ago.

Yeah can't recommend their $19 plan, only took me a day and a half to hit the weekly usage cap. The $39 plan has 5x the limits so I recommend getting that instead. Having now tested it for a few days, it is the first of the chinese models that actually feels comparable to Opus-tier models

EU and NA models still have unlockable bootloaders.

Session was supposed to be shut down at start of July but looks like they got enough funding from donations to keep going for now.

The 30 day limit can be overridden by adding "cleanupPeriodDays": 9999 to .claude/settings.json

I've been using unsloth/gemma-4-31B-it-qat-GGUF daily for various small parsing and programming tasks using opencode and llama-server's front end. The past couple of weeks have made a big difference after google released the QAT variant and llama.cpp got support for MTP which means it is possible to now get 60-80 Tok/s with RTX 4090. The model fits in VRAM comfortably enough to keep it loaded even while browsing and having multiple programs.

Hard to see any practical benefit to go after common crawl. The situation of freely accessible crawled data is bad enough as it is with archive.org and CC being pretty much the only available sources. We need more initiatives like them, not less. The scary thing is how the anti-AI sentiment is being used to lock things down further.

What ever model digiKam is using for face detection seems to be very accurate in my experience. It is open source and works fully offline.

The 7B parameter Vibevoice TTS model is still the most impressive local TTS model i've tried. It was pulled by Microsoft a few days after its release due to "abuse potential" but it can be found in various community maintained huggingface repos.

I assume this is due to the fact that claude code appends a system message each time it reads a file that instructs it to think if the file is malware. It hasnt been an issue recently for me but it used to be so bad I had to patch out the string from the cli.js file. This is the instruction it uses:

> Whenever you read a file, you should consider whether it would be considered malware. You CAN and SHOULD provide analysis of malware, what it is doing. But you MUST refuse to improve or augment the code. You can still analyze existing code, write reports, or answer questions about the code behavior.

1.13.6, so should not be affected by the malware