Dev Update #2 for smista․ai is out. This dev update follows our second milestone, which was about building smista-storage, the crate that gives user sessions a proper home. An #AI session is not just a chat history: it is a graph of messages, routing decisions, tool calls, approvals, plans, diffs, and much more. That made the choice of database more interesting than usual. We have to be able to run locally, by embedding the engine, without asking users to spin up local services. But we also have to be ready for a future SaaS version in which the database is deployed on a dedicated cluster. That's why we opted for SurrealDB: embedded inside the #Rust router, runs in memory for unit tests, and standalone for SaaS architectures. Once again, focusing on our core principle: Local-first, but not local-only. Read the full update: smista.ai/blog/dev-update-2-…

Yesterday, #Ladybird announced they will no longer accept public pull requests. This has sparked debate about how AI is affecting (and afflicting) the open-source software community. Was that the only viable option? And what does this choice mean for the community around open-source software? My two cents on my blog: blog.veeso.dev/blog/en/ladyb… #opensource #ai #aislop

People and companies give #AI agents access to our APIs, our inboxes, our data, and then basically trust them with everything they do. With the guys at Firma-AI we've been building OpenFirma: you write Cedar policies for what your agent is allowed to do, and every outbound call gets checked against them before it leaves. Deterministically, not "the model promised". Rust, open source, almost ready for release. Check it out at github.com/firma-ai/openfirm… #rustlang #ai #aiagents #infosec #opensource

Today I read that #Uber reportedly capped employee spending on agentic coding tools at $1,500 per month, per tool. And honestly, this feels like the beginning of a much bigger problem. Companies want developers to use AI. Developers are using AI. But then the bill arrives. The usual reaction is to add spending caps. That may control the damage, but it does not improve the workflow. It does not help developers choose the right model. It does not prevent expensive models from being used for simple tasks. It does not keep sensitive code local. It just says: "stop here". I think the better answer is routing. Planning can go to a stronger reasoning model. Simple edits can be handled by a faster coding model. Security-sensitive code can stay local. Documentation can use a cheaper model. Company policies can be versioned instead of improvised. That is what smista #ai is about: a local-first routing layer for AI developer workflows. I explain this better in the new article on the Smista AI blog: smista.ai/blog/your-companys… #llm #ai #opensource

Dev Update #1 is out. Only 10 days after the first line of code, smista #ai completed its first milestone. The core library now defines the shared types used by the CLI and router, including the policy model, routing rules, intent classification, config validation, and SDK foundations. This milestone is about one principle: Model routing should be deterministic. Not hidden behind another LLM call. Not guessed every time. Not dependent on whether the model "understood" the task correctly. Routing should be explicit configuration: readable, reviewable, reproducible, and safe. That is what smista #ai is building. Read the full update: smista.ai/blog/dev-update-1-… #ai #opensource #rust #devupdate #llm

Your boarding pass should be boring. Yet some airlines still make you choose between downloading their app and printing a paper ticket, instead of simply adding the ticket to Apple Wallet or Google Wallet. That’s not just bad #UX. It’s an upselling machine. I wrote about it: blog.veeso.dev/blog/en/why-a… #darkpatterns #airtravel #travel

I spent the last weekend writing almost 100 pages of specifications for a project that has been on my mind for the past month. As #LLMs become more expensive, developers need to be more intentional about which model they use for each task. Choosing the right model is not only about saving tokens. It is also about keeping workflows fast, avoiding unnecessary overthinking, and making local models usable without giving up the developer experience we are used to. That is why I’m building smista #ai. smista #ai is a local-first router and CLI for AI developer workflows. Instead of manually choosing the model, provider, and effort level every time, you define deterministic policies once and then dispatch the job. Planning can go to a stronger reasoning model. Simple edits can be handled by a faster or cheaper model. Sensitive tasks can stay local. Documentation can use a different provider entirely. The goal is not to hide model selection behind magic. The goal is to make it explicit, configurable, traceable, and boring. smista.ai/blog/i-dont-want-t… #rust #rustlang #opensource #ai #llm

Bitcoin was supposedly invented to be a decentralized, third-party payment system designed to evade government control. But if you look at who’s speaking at the Bitcoin conference, you can quickly see how the community has been hijacked by those same nefarious players. The speakers include the FBI Director, the Acting AG, the SEC Chair, and the CFTC Chair. The event has had nothing but politicians, govt agents, bankers, and suits running the show. Oh, the irony.

Hello #rustaceans After 3 years of stand-by I've finally resumed working on tui-feed. tui-feed 0.4.1 is OUT now 🔥 github.com/veeso/tuifeed

📝 Hey #Rustaceans: I've managed to bundle shared objects in rust crates. Come see how I achieved this in my new article on my blog blog.veeso.dev/blog/en/embed… #Rust

📝 Hey #Rustaceans: This week I've suffered for you 😰! But finally, we have a guide for Vendoring C/C dependencies in #Rust blog.veeso.dev/blog/en/vendo…

📝 Hey #Rustaceans: Have you ever wondered whether you could extend Future in Rust? Probably not, but my new article Extending Future in Rust is Out! #Rust blog.veeso.dev/blog/en/exten…

📝Hey #Rustaceans: My new article on my blog has just been published! Async Rust for Dummies #Rust blog.veeso.dev/blog/en/async…

There are only two kinds of people: those who keep dependencies alphabetically sorted and psychos.

Not long ago, I used to have a more optimistic impression of Rust users. I would not have guessed that so many otherwise-judicious people would go for blatantly AI-"maintained" Rust libraries. The `serde_yml` crate is a fork of a high-quality but unmaintained library. In the fork, the AI has taken initiative to add a big heap of stuff that is variously complete nonsense (docs.rs/serde_yml/0.0.11/ser…, docs.rs/serde_yml/0.0.11/src…) or unsound (docs.rs/serde_yml/0.0.11/ser…). On top of this, the crate's documentation has been broken in docs·rs for the last 5 months because AI hallucinated a nonexistent rustdoc flag into the crate's configuration. And yet 134 other published packages have chosen to adopt this? Including high-profile competently maintained projects like Jiff (for tests only), axodotdev, Wasmer, MiniJinja, and Holochain. This does not bode well. The bar for someone to do better at a YAML library is so low.

Italiani quando viene introdotto lo studio della #Bibbia nelle scuole, libro cardine della cultura occidentale e super interessante ANCHE per un ateo 🤬🤬🤬 Italiani quando da sempre c'è "I promessi Sposi" nel programma delle superiori; un libro infarcito di espedienti Deus Ex Machina tramite Provvidenza Divina ogni due righe 😍😍😍 #Valditara

On #thisweekinrust you can find my brand new article blog.veeso.dev/blog/en/a-jou…. The full story about my huge remotefs-rs project, from the origin to the brand new FUSE library for remote file systems. #rust #rustlang #rustdev #opensource #developers

Yet another #Bitcoin article on my blog "Why Bitcoin is not decentralized - in any way" 🔥 blog.veeso.dev/blog/en/why-b…

I've just discovered that placekittens.com exists. From now on, my life won't be the same again.