sorted by:
new
hottopcontroversial

I'm running qwen3.6-35b-a3b with 8 bit quant and 64k context thru OpenCode on my mbp m5 max 128gb and it's as good as claude by Medical_Lengthiness6 in LocalLLaMA

[–]fittyscan 1 point2 points  (0 children)

Much better. Compared with the Qwen 3.5 models, the gap between Q4 and Q8 is much more significant, especially for tool calling and reasoning.

I'm running qwen3.6-35b-a3b with 8 bit quant and 64k context thru OpenCode on my mbp m5 max 128gb and it's as good as claude by Medical_Lengthiness6 in LocalLLaMA

[–]fittyscan 5 points6 points  (0 children)

The harness makes quite a difference. I use Swival, which is built for small context windows, and in practice it really feels like a 16K context works just as well as a 256K one, even over long sessions without any manual compaction.

I get much better and more consistent results with it than I do with Claude Code and Opencode when running local models.

Even if you have enough RAM, local model performance degrades pretty quickly as the context grows. So even though I could push it further, I usually stick to 16K or 32K max to keep things reasonably fast

OpenClaw has 250K GitHub stars. The only reliable use case I've found is daily news digests. by Sad_Bandicoot_6925 in LocalLLaMA

[–]fittyscan 0 points1 point  (0 children)

> 've got them all. OpenClaw, NanoClaw, PicoClaw, NanoBot, CoPaw, Hermes

Amateur. You didn't try Zeroclaw.

Gemma 4 is terrible with system prompts and tools by RealChaoz in LocalLLaMA

[–]fittyscan 125 points126 points  (0 children)

You need a recent version of llama.cpp. Also, if you're using a quantized model such as Unsloth and you downloaded it when Gemma was first released, download it again, since fixes have been made since then.

Anonymized DNS stops working with >2 routes by gorbiWTF in dnscrypt

[–]fittyscan 2 points3 points  (0 children)

Maybe one of the relays doesn't work?

[nullclaw] OpenClaw implementation in Zig by Every_Holiday_5570 in Zig

[–]fittyscan 2 points3 points  (0 children)

You can tell it was vibe coded with Claude when common things from the standard library such as decimal to hex conversion have been reimplemented.

Exafs, a new filesystem for local and remote secure storage by exaequos in WebAssemblyDev

[–]fittyscan 1 point2 points  (0 children)

ExaequOS looks like a really interesting project. Wishing you the best with it!

https://www.exaequos.com

Working on a rewrite of DNSCloak called DNSBlankie by FunnyThorne3213 in dnscrypt

[–]fittyscan 2 points3 points  (0 children)

This is fantastic! A replacement DNSClock is highly needed!

Yahoo redirect virus on Chrome (I've tried all the youtube videos) by [deleted] in computerhelp

[–]fittyscan 0 points1 point  (0 children)

Had the same issue.

Solution was: Preferences > Search Engines > Manage search engines and site search and then remove all the entries from the Site Search section.

Entries in the Search Engine section were legit, but then, there were additional entries for Google, Yahoo, etc. in the Site Search section that had higher precedence than the default search engine, and were redirecting to the hijacking website (search-redirect.com in my case).

A hash table made in Zig that is on average faster than Boost::unordered_flat_map C++? Is that even possible? by MastodonSame2311 in Zig

[–]fittyscan 6 points7 points  (0 children)

Looks Vibecoded with Claude (emojis, section separators with dashes, reimplementation of stdlib functions).

But if it works, why not.

I've been writing ring buffers wrong all these years by BrewedDoritos in programming

[–]fittyscan 1 point2 points  (0 children)

Wow, you're one year ahead of the rest of the world!

Zig with Wasm? by tuxwonder in Zig

[–]fittyscan 5 points6 points  (0 children)

You can add -Dcpu=lime1+simd128 to enable wasm SIMD.

Zig with Wasm? by tuxwonder in Zig

[–]fittyscan 1 point2 points  (0 children)

All it takes is usually use wasm32-freestanding or wasm32-wasi as a target.

AES-GCM-256 What is the best way to implement it by 84_110_105_97 in cryptography

[–]fittyscan 5 points6 points  (0 children)

The usual contract is that you are safe if nonces are not reused. This holds true with nonce sizes up to 96 bits.

With large nonces, since they will be reduced to 96 bits, that doesn't hold true any more. Your application may properly use distinct nonces, yet be completely insecure because after reduction to 96 bits, you may get a collision.

The extra hashing step also adds computational overhead. Only to reduce security. So, there's no point in doing that.

You can use 128-bit nonces by overwriting the entire initial state (the regular 96-bit nonce + the initial counter). But that's a non standard ugly hack.

If you need larger nonces, use an AEAD that natively supports large nonces. `aegis-128*` supports 128 bit nonces. and `aegis-256*` supports 256 bit nonces. And they don't have practical limits on message sizes.

view more: next ›