Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Category for relevant sponsored segments #2177

Closed
jasondyoungberg opened this issue Dec 22, 2024 · 2 comments
Closed

Feature: Category for relevant sponsored segments #2177

jasondyoungberg opened this issue Dec 22, 2024 · 2 comments

Comments

@jasondyoungberg
Copy link

Sometimes I'm watching a video and I'll have to go back because a bunch of useful and relevant information was skipped over because there's a sponsorship. One example is this video, where he explains how gamma spectroscopy works, while also being sponsored by a device that does this. I would like to be able to see these parts of videos without having to manually rewind every time.

@ajayyy
Copy link
Owner

ajayyy commented Dec 22, 2024

If it's considered relevant, then it will not be marked. In this case, it's not considered relevant

@ajayyy ajayyy closed this as not planned Won't fix, can't repro, duplicate, stale Dec 22, 2024
@PatrickKennedy
Copy link

I don't think a new segment type is necessary, at least for that video, these segments entirely eliminate the "look at this product and all it's amazing features" aspect of the explanation:

11:27.197 - 11:47.479 Sponsor
12:25.041 - 12:27.473 Sponsor
12:39.367 - 13:04.178 Sponsor
13:16.239 - 13:22.727 Sponsor
13:34.577 - 13:46.820 Sponsor
14:29.881 - 14:35.243 Sponsor

If it's considered relevant, then it will not be marked. In this case, it's not considered relevant

Not really sure how we know it's not considered relevant given a locked segment eliminates the whole community driven aspect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants