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
Meetecho is bringing back the hosted video recordings that have a syncronized view of the entire session experience. We should add a link to them from the agenda - we can either derive the link to the Meetecho resource by parsing a token out of the YouTube URL that Meetecho currently posts or add an API to let Meetecho tell the datatracker about the URL explicitly. If we add an API, it would be easier for Meetecho to tell the datatracker when the recording stops being available.
Issue migrated from trac:3454 at 2022-03-04 09:18:48 +0000
The text was updated successfully, but these errors were encountered:
Well, not really. We're still providing those recordings. At the moment the agenda shows generic link to https://www.meetecho.com/ietfXX/recordings + an anchor. E.g. https://www.meetecho.com/ietf115/recordings/#IPPM. We're parsing that on our side and redirecting to the right place. Having an API to tell the Datatracker the right url directly would be handy, as there are edge cases where automatic redirection doesn't work (e.g., for wgs that meet multiple times over the week).
rjsparks
changed the title
Point to Meetecho hosted video recordings
Build API to capture URLs to Meetecho hosted video recordings for a Session
Mar 26, 2023
type_defect
| by rjsparks@nostrum.comMeetecho is bringing back the hosted video recordings that have a syncronized view of the entire session experience. We should add a link to them from the agenda - we can either derive the link to the Meetecho resource by parsing a token out of the YouTube URL that Meetecho currently posts or add an API to let Meetecho tell the datatracker about the URL explicitly. If we add an API, it would be easier for Meetecho to tell the datatracker when the recording stops being available.
Issue migrated from trac:3454 at 2022-03-04 09:18:48 +0000
The text was updated successfully, but these errors were encountered: