https://ungovernable.tech/ Got the clankers to mine my internal knowledge base (that agents have been collecting for a long time) to update the ungovernable.tech directory to a more comprehensive place for all kinds of technologies one might need in their quest for freedom.
It is a lot of text and research so not all of it has been manually checked yet, if you find any issues/mistakes lmk (or open a PR)
Permissionless aggregation is an interesting phenomenon. Most new models are by default available on the Routstr network because different nodes serve models from different sources.
You fetch Nostr events, you pay with sats.
Models become automatically available on Routstr when any of upstreams start offering them: 1. OpenRouter 2. Venice 3. PPQ 4. Tinfoil 5. Fireworks 6. Deepseek 7. OpenAI/Anthropic of course 8. And more. (We hope to see more diversity of upstream providers)
Similarly, these Abliterated models are now available from various routes. Your client -> Venice Your client -> PPQ -> Venice
LiteLLM was compromised again, your Routstr node is not affected.
A malicious build of litellm 1.107.0 shipped last week with a credential stealer and remote-code loader in all seven wheels. It's the second litellm hijack this year.
Routstr is unaffected. We pin litellm >=1.101.2,<1.102 with an exact lockfile, so 1.107.0 can't resolve in a Routstr deployment, and we found none of the published indicators in our environments.
If you are running your own venv as a developer, check "pip show litellm". If it says 1.107.0, remove cook.pth, cook.py, and sitecustomize.py from site-packages before running pip again, startup re-triggers the payload, then treat every secret on that host as compromised and rebuild.
We're removing litellm. We only use it as a translation layer, and two hijacks in one year is not a good sign.
My @npub130mzn...7ql29s node serves Muse Spark Open and Muse Wonder. Spark Open is not on Meta infrastructure and it's in "Private" mode through Venice (a pinky promise, but better than not even a promise).
Node is routstr.cypherpunk.today
You can use them through routstr-confidential where my node does not see the prompts or responses and can't alter it.
With this new release, any client can specify the exact upstream inference provider they want to use for a particular model. Including all the inference providers on OpenRouter.
Second Major Feature: Upstream Provider Test Suite
You can test if everything is good with an upstream inference provider you just added.
Other changes in: 1. Intelligence: • /v1/systemone — typed AI decisions, paid per call (Jev) • /v1/decisions — OpenAI's new Decisions API, proxied • native Venice + DeepSeek
2. Money: • Lightning refunds + payouts in tx history • crash-safe refund claims
3. Ops: • one-command private node onboarding and llms.txt for agent powered onboarding • faster requests, provider cooldowns, never strand a reservation
