Cloudflare Worker y-sweet server is causing huge runtime cost.

[timeswind]

The y-sweet Cloudflare worker is using Cloudflare Durable Object WebSocket connection feature. But since y-sweet server is build on rust, the rust porting api for Cloudflare worker Durable Object doesn't have a the latest Hibernatable WebSockets API which use a custom acceptWebsocket to replace the origin accept function.

The origin accept function of WebSocket feature would causing long-span Cloudflare durable object runtime fee and is not suitable for large-scale usage(actually even single WebSocket connection would cause large runtime fees, which I tested on my personal Cloudflare account, triggering the next-tier pricing charge very easy)

https://developers.cloudflare.com/durable-objects/api/websockets/#acceptwebsocket