I wish I'd heard about it when it was first published, it is super cool! Especially the timeline, given that it predates things like ts_zip/LLMZip (which is why I figured someone had already worked on something in the area), while being fundamentally the same mechanism. Makes sense why compression ended up being a more compelling use case though.
Whether you disagree with whether it truly aligns with their stated values, in their partnership with Palantir (making Claude available within their AI platform) they requested consistent restrictions:
> “[We will] tailor use restrictions to the mission and legal authorities of a government entity” based on factors such as “the extent of the agency’s willingness to engage in ongoing dialogue,” Anthropic says in its terms. The terms, it notes, do not apply to AI systems it considers to “substantially increase the risk of catastrophic misuse,” show “low-level autonomous capabilities,” or that can be used for disinformation campaigns, the design or deployment of weapons, censorship, domestic surveillance, and malicious cyber operations.
Anyone else having issues exporting their data from ChatGPT? I started my export in the morning, still have yet to receive an email for the download. Wanted to make sure my deleted account was included in the beans when they count them on Monday.
Typical SV/ Scam Altman tactics : technically trying to keep people from moving out of their walled prison-garden. It exemplifies how important open-standards and data export laws are.
Kinda the wrong venue for “fighting,” no? Congress is the place we decided for that, and we all abide by its laws. If Uncle Sam comes knocking, a fight just means you’re the enemy.
Absolutely not, and it's tragic that Trump has twisted your understanding of the American government so much. It's your patriotic duty to oppose even the highest ranking government officials when they want to do bad things, and neither Congress nor the Secretary of Defense have any lawful power to stop you.
Forgive the uninformed questions, but given that `workerd` (https://github.com/cloudflare/workerd) is "open-source" (in terms of the runtime itself, less so the deployment model), is the main distinction here that OpenWorkers provides a complete environment? Any notable differences between the respective runtimes themselves? Is the intention to ever provide a managed offering for scalability/enterprise features, or primarily focus on enabling self-hosting for DIYers?
Thanks! Main differences:
1. Complete stack: workerd is just the runtime. OpenWorkers includes the full platform – dashboard, API, scheduler, logs, and self-hostable bindings (KV, S3/R2, Postgres).
2. Runtime: workerd uses Cloudflare's C++ codebase, OpenWorkers is Rust + rusty_v8. Simpler, easier to hack on.
3. Managed offering: Yes, there's already one at dash.openworkers.com – free tier available. But self-hosting is a first-class citizen.
Question: Do you support WASM workers? How does the deployment experience compared to Wrangler? If I have a wasm worker and only use KV, how identical will be the deployed worker to that of Cloudflare?
WASM is supported, V8 handles it natively. Tested it briefly, works, but not user-friendly at all yet.
OpenWorkers CLI is in development. We're at the pre-wrangler stage honestly. Dashboard or API for now, wrangler-style DX with Github/GitLab integration is the goal.
reply