pleroma.debian.social

pleroma.debian.social

Right now, on the morning after #FOSDEM, if you started watching now and wanted to see all the currently available videos of talks that were held at the @fosdem that just finished, you have nearly 4 days ahead of you.

See https://review.video.fosdem.org/overview and https://dashboard.fosdem.org (the 'SReview stats' dashboard) to follow along at home.
replies
3
announces
27
likes
30

@fosdem On a side note, if your favourite talk is still listed as "preview" on https://review.video.fosdem.org/overview, please reach out to the speaker or devroom manager. They can review the talk and release it for viewing.

@wouter @fosdem really awesome you're this quick in releasing video's. woohoo!

@joostvb
You're welcome!

Combination of crowdsourcing the bits that can't be automated and automating everything else means things do go fast 😉
@fosdem

@wouter @fosdem if you don’t mind me asking, how does the publishing step work? Is it bottlenecked on rsync pull frequency of individual mirrors and/or a periodic crawler completed transfers? The shape of the ‘publishing’ curve for the last 24 hours on the ‘ReviewState’ graph made me curious.
(Ie. https://dashboard.fosdem.org/d/febvgsg30muioa/sreview-stats?orgId=2&from=now-24h&to=now&timezone=browser&refresh=30s)

@maarten
The dispatcher does a HEAD request for a single file of every talk that is in the publishing state, then inspects the returned data. If that indicates that the video is public, it moves to the next state.

Exact code at https://salsa.debian.org/debconf-video-team/sreview/-/blob/main/scripts/sreview-dispatch?ref_type=heads#L182-219
@fosdem

@maarten
The FOSDEM server team runs mirrorbrainz on video.fosdem.org, I don't know how that decides that the video is available on at least one mirror, but what causes the spikes in availability of videos must be in there somewhere.
@fosdem