ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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
Goal Determine whether SurrealDB can apply server-side filtering to real-time change notifications so that WebSocket and HTTP clients receive only actionable live-query events without alert noise. SurrealDB supports LIVE SELECT and CHANGES over persistent WebSocket connections, while the HTTP REST interface is primarily request/response and is not the docume
Selenium BiDi Protocol Event Listener Registration The Selenium 4.x BiDi (Bidirectional) implementation enables real-time event listening through WebSocket connections, supporting features like network interception and console log monitoring without the need for constant polling. A primary challenge involves the inconsistency of BiDi support across different
Goal: Determine whether Stackblitz imposes a limit on the number of simultaneous Live Preview WebSocket connections that can be opened for a single project, and whether this limit can be adjusted. Constraints: The Live Preview documentation states that a session is created per browser tab but does not specify a hard maximum or provide a user‑configurable set
waku
web3js
surrealdb
stackblitz