nextime

The meaning for that sentence is that litellm just route requests, it doesn't execute a model.

and you are confusing a demo with a "commercial project". Look at the moon, not at the finger. Have a good life and if and when you will have any relevant comment or real critique, i will listen to you. PLONK.

You know when they say "when i point the moon you are looking at the finger"?

• Hosted demo (no setup): https://aisbf.cloud (https://aisbf.cloud/) • Self‑host: pip install aisbf • Source code: https://git.nexlab.net/nexlab/aisbf.git

We’d love feedback from the community—especially anyone juggling multiple LLM APIs who wants to simplify routing and reduce costs.

AISBF 0.99.18 released! In this version:

fix a LOT of bug full support without installing the cli and complete with Oauth2 initialization: claude subscriptions with oauth2 or api token codex cli subscription with oauth2 or api token qwen-code cli subscription with oauth2 or api token kilo is supported both with oauth2 or token kiro-cli full support any anthropic, gemini, openai, ollama compatible endpoints

AIsbf ( AI Should Be Frtee ) is a API proxy/router with intelligent ai driven router which exposes an openai compatible api to the clients making available to them in a unified interface different protocols and AI endpoint/services, offering various optimization aiming to make the costs of using LLMs more accessible to everyone.

It is multiuser, and can run from small setup or scale to big infrastructure.

In this last release: - support for cache on redis, sqlite, mysql, file - more context condensation method - native prompt caching and request caching support - faster and better semantic prompt based routing for autoselections - full support for Claude.ai subscribers with OAUTH2 - full support for Amazon Kiro-cli subscribers with OAUTH2 - full support for OpenAI codex subscribers OAUTH2 - full support for Kilo.ai subscribers using token or OAUTH2 - many bugfixes and new minor features

It has to be pronounced as this: http://danex.nexlab.it/devuan.wav

The first release has been named "jessie" cause it's a 1:1 replacement of debian jessie, and for our luck jessie is also a name of a minor planet, so, it match our nomenclature and reflect that is a very close path to switch from debian jessie, as Devuan consider itself the "real" continuation of debian after wheezy.

http://danex.nexlab.it/devuan.wav

Wayland have some advantages but also some disadvantages, and it isn't yet really mature.

Also, wayland, on the sandbox side, doesn't do anything special. As it's just a lot simple than X and does pretty anything except copy a buffer on the screen, it just delegate all IPC and rendering to the compositor, then, in the wayland world, the security issues of X11 are moved on the compositor instead to stay on the X server, but the issue are the same and the compositor must consider them.

Yes, X11 has no separation, but you can use multiple X11 isolated sessions, like i do in this config i'm explaining in this post.