celld v0.5.1 is released~ - Dynamic Workers can enforce CPU time and subrequest limits from WorkerCode.limits - Support for Tail Workers - KV accepts a ReadableStream value in put() - Compaction can read retained LTX bundles after their segments leave the in-memory index, so a slow cell can continue draining its history. - The /evict/ operator route reports a refusal, cancellation, or failure instead of returning success before the eviction completes. - Node.js compatibility improvements

i feel like people do not grok how important celld is. it's scalable applications of arbitrary complexity. the only dependency is s3. once you see it, you'll realize there's no point to traditional javascript runtimes in serving applications - only for build processes (eg bundling) and scripting. the networking and scaleability are deeply rooted not only in the distributed runtime (celld), but in the programming model itself (largely kenton's design) I wasn't quite sure when I started celld how well this could be made to work, but we've been running it in bigger capacities and getting user reports over the last months. Actually handles load surprisingly well. (any experience in the comments to share?) because the programming model does not expose the underlying linux system, you can actually think of celld as a distributed operating system - running in user space of linux. it only runs one program / doesn't support multi-tenant, but it has system services like an operating system. it's all about networking - i like to think of it as the practical modern version of plan9 or even erlang beam.

Does @OpenAI have an OSS program that will let me use the Daybreak models? Somehow while investigating a possible issue with celld I'm getting flagged. cc @rough__sea @kevinwhinnery