If we had an ASIC for Kimi K3 right now we could get so much done!

Apps are live now! Just deployed my own Buzz relay and migrated all my agents there!

Ye, unless you run a buzz relay, its streamlined flow atm

Sure will let you know, current setup is quite secure but not bullet proof Kimi K3 review: The codebase is unusually well hardened for a multi-tenant app platform — PSS restricted/baseline per namespace, read-only root FS, drop: ALL, capped emptyDir scratch, no SA tokens in tenant pods, encrypted config at rest, fail-closed billing gate

It could be better, but we have the most restrictive permissions we can have for now, but we will continuously review this. Also we only allow installing apps from the catalog so there is very low risk atm. Later we plan to allow running any arbitrary image but we need a few more security layers first.

Not quite, this looks like managed VPS for your own dedicated apps, LNVPS apps are deployed on shared kubernetes cluster

If you are running Buzz ACP on remote machines you can add this dashboard layer in the middle to get better visibility of what your agents are up to. Its generic ACP tap service so it can work anywhere you use ACP. https://github.com/v0l/acp-tap

Yea we can add more apps, we built a docker compose like structure so its pretty familiar and can run most apps, for now we are limited to apps serving over HTTP only, but on the roadmap we plan to support other generic TCP/UDP services

Not sure what you're asking?

Not everybody is going to run their own relays, more relays is always better as long as you dont have like 1000+ relays to pull from then its fine

Now android build pls?

The zap.stream chat widget alrrady supports this

Deployed the latest build of zap-stream-core with HLS-LL output and CMAF. What does that mean? 3s stream latency! Efficient, shared audio stream, between variants (resolutions)

Wen android