• The client's local "user" var has to be updated when they are chosen to be the new controller

• begins at player.js, will start a lifecycle async thread that will loop every (interval) seconds which sends updated player information to background.js
• background.js will send this information through websocket back to the server to update that client's data in lobby
• server will broadcast the updated lobby to all connected clients

just do something with it (reset background.js or something)

• player_state_update
• client_update (everything)
• player_time_update

• Initiated by Popup#connectClicked
• Call a function in LDNClient to send the WebSocket request

Right now it uses
Date.now() + Math.random()
which is pretty silly but would probably work, even in production

• If the controller is watching, the connected user must receive the correct state info about the controller in the connect_lobby_ack response

1. The master will send a start_control to the server
2. The server starts a timer interval in which it pings that lobby's users for state information + calculate latency
3. Server sends back an acknowledgement to the master indicating the control state has changed
4. When the timer interval hits, we send a lobby.emit() ping message that recalculates an average latency for each user
5. If a slave deviates from the master too much, the server sends the next ping with calibration data

There are a ton, especially in background.js

Right now the objective is for everything to WORK, so once I do that, I'll refactor the codebase and make it prettier/less cluttered and less hacky.

do this after the demo is working

Tried doing this in the executeScript callback, but it sends the message before the script is ready. I think you might be able to set a delay, but that seems hacky so I'll wait on this one.

I'm thinking in register_DOM_listeners(), I'll send a message from player.js to background.js to send a time_update to the player. That'll seek() to the correct position.

• If the client given user ID is null, return one

loader.js is only run when you reload on a /watch page. We need it to run so maybe execute loader.js from TabListener rather than the manifest?

It needs to destroy the previous script and execute a new one in background.js on url change

When sent over websocket

https://www.stephanboyer.com/post/105/netflix-party-synchronize-netflix-video-playback

Right now there is a timeout system based on average elapsed time, but this can be expanded on/revised

• Button is clicked -> Popup#startLobbyClicked
• Trace from there, no response is ever returned to popup.js

Right now all the lobby data is sent between server and each client. Condense this!

• If the controller is removed, a new user is assigned
• If there are no players, make sure to cleanup the Lobby instance (it might still be referenced in server.js)

• Use lobby.removeUser()

also its just not working

It returns undefined... what do

Right now it hangs as if doing nothing

Right now it tries to send a connect_ack, which doesn't make sense.

The session ID is just a 16 bit hash string generated with crypto and RNG.

• The controller will initiate a request to the server containing the new tab url parameters
• The server receives the request and sends an update to each slave in the lobby
• The slave receives the update request from the server and updates the local state in ldn.js, changes the url

• There's a handler function for the button in popup.js
• Should send a message in the chrome runtime to the background script, which holds the socket connection
• The background script sends a message to the server start_lobby, and the server returns the lobby ID
• The background scripts sends the lobby ID back to the popup script an displays it, updating ViewState

• look at startLobbyClicked for reference
• should call a function in LDNClient (can change this in future maybe)

Caused by some conflict when setting the playhead (CTRL+F look for player_update in player.js), conflicts with Netflix for some odd reason...

• Client sends register_client GET request with client_id, url, and lobby_name as params
• Server receives GET request, checks for conflicts, and creates the lobby with given name
• Client will change UI to read "Stop broadcasting"

A way to indicate that you are the controller, perhaps just an icon displayed

• Located in popup.html and popup.js

• Not sure how I'm gonna do this yet but I'll use this issue discuss it

On second thought, the browser performs a reload so I don't think this is necessary.

• The popup script must be stateless because it is destroyed when removed

• Not sure how to fix this yet

Ya should've done this before but oh well

User should not be able to pause/play when in session with server