You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 10, 2021. It is now read-only.
Recordings of semi-formal sessions (workshop talks, Q&A sessions, etc.) are a very requested feature. The main reason they are hard to provide is that (a) recordings are public and (b) distributing a public recording of somebody requires that they sign a release form.
If we could distribute recordings privately -- by capturing Zoom or Twilio streams and making them available only within the conference site -- we could make a lot of useful content available asynchronously that is just not feasible now or that takes too long to be very useful.
The text was updated successfully, but these errors were encountered:
At least in the UK, that would still require consent from every participant, just to take the recording in the first place. This is not something you can get around just by keeping the recording 'private'. Also, people may not like asking questions when they know they're being recorded.
At least in the UK, that would still require consent from every participant, just to take the recording in the first place. This is not something you can get around just by kelping the recording 'private’.
The registration site does require that people give consent for recording. But there seems to be a perception (from ACM, maybe) that making recordings really public requires a heavier-weight consent form with a real signature.
Also, people may not like asking questions when they know they're being recorded.
True — there are tradeoffs to consider here. But at least doing it for workshop talks would clearly be good.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Recordings of semi-formal sessions (workshop talks, Q&A sessions, etc.) are a very requested feature. The main reason they are hard to provide is that (a) recordings are public and (b) distributing a public recording of somebody requires that they sign a release form.
If we could distribute recordings privately -- by capturing Zoom or Twilio streams and making them available only within the conference site -- we could make a lot of useful content available asynchronously that is just not feasible now or that takes too long to be very useful.
The text was updated successfully, but these errors were encountered: