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
AISBF - a personal AI proxy! Tired of API limits? Free accounts eating your tokens? OpenClaw needs snacks? This Python proxy handles OpenAI, Anthropic, Gemini, Ollama, and compatible endpoints with smart load balancing, rate limiting, and context-aware model selection with context condensation. Install with pip install aisbf - check it out at https://pypi.org/project/aisbf/
The name "devuan" has been selected cause it's a merge of "debian" and "VUA" where "VUA" stand for "Veteran Unix Admins", the name of the group that started the fork.
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.
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.
( anyway, for sure fix those issues in a compositor is easier and consume less resources than on X11, and then the wayland world is better from this point of view. But i don't think it's yet enough mature, and many WM/DE doesn't yet support it or support it only partially )
I know it is very immature (basically unusable in most cases), but my understanding was that it would be easier to fix these issues moving forward because of the design decisions taken in Wayland. You response seems like a tentative affirmation of that, which is encouraging to me (for whenever I can actually used it).
ok, you readed it and awhere of the -paranoid with xpra. Great. anyway, there is no way to obtain perfect security, this is just a little improvements as I explained.
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
reply