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
Today i was watching some talks because of boring and Corona ( :c ) and found a talk where i wanted to skip through faster and thought it would be nice to have some timestamps in the videos. Timestamps for the questions at the End (where the question asked is a timestamp - because you can't see them in the preview) would be really nice.
In my opinion subtitles would be also a massive improvement. Maybe include some additional commentary from the speaker?
Maybe a kind of gamified backend UI with points and rewards to crowdsource it would be a thing.
The text was updated successfully, but these errors were encountered:
saerdnaer
changed the title
Feature request: Crowdsourced timestamps and subtitles
Feature request: Crowdsourced timestamps/chapters
Nov 10, 2024
Subtitles are a totally different topic which we already implemented, or are re-implementing right now. So let's focus this issue on Chapters/Timestamps:
I don't think that gamification would work for use, be cause we do not have the time to fine-tune such a system. In on of the other issues here in this repository we came to the conclusion we would need a way to manage the metadata of a individual item (aka Lecture/Talk/Event/Session) in a similar way like source code with Pull-Requests etc.
Today i was watching some talks because of boring and Corona ( :c ) and found a talk where i wanted to skip through faster and thought it would be nice to have some timestamps in the videos. Timestamps for the questions at the End (where the question asked is a timestamp - because you can't see them in the preview) would be really nice.
In my opinion subtitles would be also a massive improvement. Maybe include some additional commentary from the speaker?
Maybe a kind of gamified backend UI with points and rewards to crowdsource it would be a thing.
The text was updated successfully, but these errors were encountered: