[InventivetalentDev]

Summary

This PR replaces the Socket.IO dependency with a lightweight custom WebSocket client implementation called RemoteSlideSocket. The new client is designed to work across multiple environments (website, Chrome extension, bookmarklet) without requiring a module system.

Key Changes

• New file: rs-socket.js - A standalone WebSocket client (~264 lines) that implements:

  • Event-based API matching the previous Socket.IO interface (on, off, emit)
  • Automatic reconnection with exponential backoff
  • Built-in heartbeat mechanism with latency tracking
  • Proper handling of server-side rejections (4xxx WebSocket codes)
  • No external dependencies; ships as a plain script

• pageController.js updates:

  • Replaced Socket.IO initialization with new RemoteSlideSocket()
  • Removed the manual init event handshake; connection is now opened directly via socket.connect()
  • Added handler for the new rejected event to detect when another page takes over the session
  • Simplified event emissions: changed from socket.emit("_forward", {event: "...", data: {...}}) to direct socket.emit("eventName", {data: {...}})
  • Removed manual latency tracking code; the socket now handles heartbeats internally and reports latency via the latency event

Notable Implementation Details

• The RemoteSlideSocket exposes a global variable (no module system) to support injection into different execution contexts
• Heartbeat frames are sent every 2 seconds with a 10-second timeout to detect dead connections
• Server rejections (4xxx codes) are distinguished from disconnections and are not retried
• The socket automatically cleans up timers and event handlers on disconnect
• All handler errors are caught and logged to prevent one failing handler from affecting others

https://claude.ai/code/session_01GfhNPpQzAKM2dMhYp66gLk