This adds some consistency to where the layout puts webcall frames,
instead of it just being in order of go-live time. For general hangout
meeting/screenshare stuff it doesn't matter, but for event production
purposes, having the frames in a predictable order is helpful.
Closes#11
This is same-session only. We still don't store any session data or
cookies. We dump mute and volume settings to an object when a webcall
stream is reaped, then restore them if the stream comes back.
This should address hardship in a lossy connection or someone
"quickly restarting OBS" needing to re-unmute the player.
Closes#5
10,000 hours mucking with `git filter-repo` and no reasonable use-case
found. On the plus side, anyone looking at this and curious what I nuked
isn't missing much. This lived in a monorepo up until about a week ago.
