Arcuru

So did Brave stop that crypto thing that was clearly designed to steal money from content creators?

Yes I know, it's a tired complaint years after the fact, but if you launch a browser with that system as a core value prop then it should probably taint the leadership team for a good long while.

Over on /r/LocalLLaMA there's a group that's been getting popular doing the same thing for the Qwen 27B (and other) models. - https://huggingface.co/ukisai

Great. Now let me use the subscription outside Claude Code.

Just .gitignore CLAUDE.md and handle it locally. Checking in a symlink would be weird.

It's the scale that's the problem. I've been saying for a while, the value of any individual piece of work is not terribly valuable for an LLM, but the aggregate value of all human work is obviously very valuable. I think this line of thinking can be the argument for why we should heavily tax these AI companies above and beyond how we tax other industries.

Also that if you're going to use these things to write software, you should make it as virally copyleft as possible https://jackson.dev/post/moral-ai-licensing/

I can't find the reference right now, but I'm certain that Anthropic has been asking for a coordinated slowdown for at least 4 or 5 months. I think it was around their Mythos/Fable releases this spring.

Has the code quality in that repo gotten to a good point then? I haven't followed it much, but last I looked[1] (which was a few years ago) almost every tool I looked at in detail had pretty bad performance or correctness issues.

[1] https://jackson.dev/post/rust-coreutils-dd/

demonstrate != explain?

Thanks! And from the Technical Report linked in there it looks like their Large unreleased model is a trained Qwen3.5-397B

> starting from a strong open-source foundation and investing $40 million to train Thomson

Sounds like they spent $40 million finetuning an open weight model on their own data? I wonder what they built on.

Be nice, maybe this person isn't very tech-savvy and doesn't know how to setup their own blog?

It's not like they are the highly technical founder of a very successful, privacy-focused messaging app....

I think it's a design mockup, they didn't implement it yet.

So this is a new design, but it's at the design proposal stage and not yet implemented?

They've been talking about redesigning Thunderbird for years now, but I'm honestly not sure I've noticed any difference at all in my actual use.

Since I don't see it mentioned yet, https://blessed.rs seems to be pretty popular for finding common/recommended crates in the Rust ecosystem.

Awesome! I've been waiting for them to start scaling ternary models for over a year[1]. Excited to try it out, typical Qwen 27B is too heavy for me to run on my local hardware at reasonable speeds.

[1] https://jackson.dev/post/dont-sleep-on-bitnet/

I've continued working on Eidetica, my decentralized database project. I recently added support for a client/server architecture so that it can be transparently run as a local daemon for background sync and sharing the local storage with multiple users. I've been making progress on integrating blob storage next, as well as scoping out WASM based "lenses" for handling decentralized version/schema updates. https://github.com/arcuru/eidetica

I've primarily been testing it by building out my AI tool chaz into an Eidetica-native AI Agent framework for decentralized Agent sessions. It's working surprisingly well, it maps pretty well onto the storage model and it's uncovering issues with Eidetica I need to fix (which was always my primary reason for building it anyways). https://github.com/arcuru/chaz

Separately I'm building OptiMap, a SIMD-accelerated hashmap repo that explores the design space for hashmaps and benchmarks different approaches. This is mostly for my own learning but I'll eventually turn into a blog post. https://github.com/arcuru/optimap

I'm not so sure that Blacksmith is making the right choice around how to handle this signup flow, but I have very little sympathy for the person in this post. $1000 in CI is a lot of usage.

> rsync (remote sync) is a utility for transferring and synchronizing files between a computer and a storage drive and across networked computers by comparing the modification times and sizes of files.

https://wikipedia.org/wiki/Rsync

It's even weirder that their long post doesn't mention it's Mac only.

I am very happy with DSv4 for their price/performance but neither of them are comparable to Opus.

You can always go join your condo board meetings though. In my experience most HOA boards are filled with people who have seen horror stories of HOAs and don't want to live in a place with a bad one.

Sure sometimes they do make bad decisions, but you're welcome to just show up to their board meeting and give them some advice.

It's actually even cheaper when you look at the cache read costs. Those costs can dominate in agent workflows and DeepSeek's cost for cache reads is insanely low comparatively. At $.003626/M tokens, the cheapest other thing on your list is >$.2/M tokens. That's on the scale of 100x cheaper.

> What changed with Mythos Preview is that a model can now take those low-severity bugs (which would traditionally sit invisible in a backlog) and chain them into a single, more severe exploit.

I think this statement seems to align with some of the other independent tests of Mythos[1]. It did very well on long agentic work which I expect is what they trained it for, and that requires being able to find these tangential links between loosely related topics in the context window.

[1] I'm mainly referring to https://www.aisi.gov.uk/blog/our-evaluation-of-claude-mythos...

I run a home-grown 'Agent' by just making a local user on my linux box. I treat it like an untrusted local user, I only give it scoped API keys, and manage permissions just like any other thing. I have a NixOS machine and I have the Agent setup to just use home-manager to manage itself and its timers and deps and stuff inside its own config.

It would be insane to run a full fledged Agent from your own accounts, with the same access as yourself. At the same time running it fully scoped inside a container/VM seemed a little bit too heavy handed to me and the Agent-as-user seems like a better fit for me right now. (I did run my coding agents inside a microVM for a while but ran into a few too many annoyances)

But there's probably not encryption either, so the sqlite database file probably has a lot of duplicated data inside it that's visible externally. I'm also curious how well it compresses by just running the sqlite file through a compression tool. I don't know enough about sqlite storage internals to guess.

The Anthropic researchers have said their flow is as simple as:

1. Pick a file to seed as a starting place.

2. Ask the LLM (in an agent harness) to find a vulnerability by starting there.

3. If it claims to have found something, ask another one to create an exploit/verify it/prove it or whatever.

4. If both conclude there is a vuln, then with the latest models you almost certainly found something real.

Just run it against every file in a repo, or select a subset, or have an LLM select files with a simple "what X files look likely to have vulns?".

So basically yes, it is that simple. It's just a matter of having the money to pay for the tokens.

It's because they:

1. Forked an existing app that has all the features you listed.

2. Admit they don't really know the language and tech it uses.

3. Said upstream was too slow, but I don't see any(?) PRs from them on upstream besides the 2 that they list in the post. Their fork appears to have an extra 3,000 commits.

I'm not super against them doing this, but it's pretty easy to see why people don't like it. Hell, this is the same group that upgraded one of my side-projects from a few years ago and improved it into their 'baibot' matrix bot, so I wish them all the best. I like people making money from OSS, more power to them.

Personally, I think that the human directing the agent owns the copyright for whatever is produced, but the ability for the agent to build it in the first place is based off of stolen IP.

I'm concerned about the copyright 'washing' this enables though, especially in OSS, and I think the right thing for OSS devs to do is to try to publish resulting code with the strongest copyleft licensing that they are comfortable with - https://jackson.dev/post/moral-ai-licensing/

Reminder to all OSS projects: it is extraordinarily easy to setup a simple CI job to keep your code in sync between multiple Forges. And getting email notifications from a second Forge is 0 extra effort.

At least give people the option to start moving away from GitHub to contribute to your project. It will, ultimately, be better for the ecosystem.