ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal: Determine whether the increase in broadcast latency observed in Supabase Realtime is caused by connection‑pool exhaustion, PgBouncer backpressure, or Node.js event‑loop lag when many clients open WebSocket connections simultaneously. Constraints: The threshold at which latency becomes noticeable is unknown and may differ between free and paid project t
In a Vite (v4/v5) dev-server setup where many browser tabs or team members trigger hot-module updates at once, I see HMR latency grow once many updates queue up at the same time. My understanding is that the server batches pending updates before broadcasting them over the WebSocket, and that server.hmr.interval controls how frequently those batches flush. My
Goal Enable per‑session origin whitelisting for Vaadin Push WebSocket connections so that a single server can safely serve Push to multiple hostnames in a multi‑tenant environment. Vaadin Push currently relies on the browser same‑origin policy and validates the TLS certificate only against the server hostname; there is no documented API or server‑side config
Context Socket.IO v3 reversed the default client transport priority to ["websocket", "polling"] , making WebSocket the first attempt and only falling back to long-polling after a handshake failure. When corporate proxies block the WebSocket upgrade, the client enters a reconnect loop that emits repeated socket.io:transport debug entries. Problem No dedicated
Opera Sync Integration Across Network Environments The goal is to maintain end‑to‑end encrypted synchronization of local profile data with Opera’s cloud service when moving from an unrestricted local network to a production environment that may enforce corporate firewall policies. Opera Sync derives its encryption key from the user’s password, caches data in
I'm planning a configuration change for a node running Waku v2: the bootstrap path currently relies on EIP-1459 DNS discovery (enrtree TXT records) to find fleet peers, and I want to require secure websockets (WSS) for those connections instead of plain WS. The uncertainty is where trust is actually anchored in each step. My understanding is that the enrtree
Ktor Server ↔ Ktor Client: Content Negotiation Interoperability When a Ktor Server and a Ktor Client are deployed together, both sides must agree on how JSON payloads are serialized. The current ContentNegotiation plug‑in allows separate registration of kotlinx.serialization or gson , but the API does not provide a single, unified configuration path. This fr
In web3.js v1.5.x the WebSocketProvider keeps event listeners after an unsubscribe call, leading to incremental memory growth when newBlockHeaders subscriptions are created repeatedly. The documented fix is to call subscription.unsubscribe() followed by provider.disconnect() before process exit, which releases listeners and closes the socket. However, the de
The web3.js v4 release restructured the provider abstraction to comply with EIP-1193 and support modular transports, including WebSocket. The migration guide marks the legacy WebSocketProvider deprecated, but the new Provider interface does not specify whether built-in WebSocket reconnection is retained or fully delegated to applications. This ambiguity affe
socketio
waku
web3js
supabase