SponsorBlock - User contributions [en-ca]

Tangents/Jokes

2026-04-05T18:48:28Z

AcesFullOfKings: add "previously known as filler"

{{Message box|type=caution|mini=1
|title=This is an aggressive category.
|text=Tangents is a category meant for when you aren't in the mood for “fun”.
}}
'''{{Category|Tangents / jokes}}''' is for tangential scenes or jokes that are not required to understand the main topics or narrative of the video.

This category was previously known as "Filler Tangents/Jokes", but was renamed without changing the definition.

== Description ==
This includes:
* Time-lapses / B-roll
* Fake sponsors
* Slow motion clips that do not provide any context or are used as replays or B-roll footage
* Bloopers
* Irrelevant / tangential parts
** Video author being distracted by something unrelated to the video
** Unrelated highlight clips that don't provide any context, are not elaborated on and don't fit into {{Category|preview}} or {{Category|hook}}.

== Exceptions / Edge Cases ==
* If any other category can be applied (mute or skip), choose them instead. Tangent is the lowest priority category.
* In most cases, tangents should not be mute. Mute tangents should mostly be used for chaining to a skip.
* This category is not for censoring content such as jumpscares, bright flashing, or distressing moments.<ref>[[FAQ/New categories#Not protecting a user's mental or physical health]]</ref>

Not included:
* Similar to other categories, '''do not''' mark entire videos.
* Useful information:
*# Provides context.
*# Useful explanations or analogies.
*# Excerpts from sources.
*# Background details.
* Segments that are referenced later.
{{Disclaimers}}

== Examples ==
{| class="wikitable" style="width: 80%"
|-
! style="width: 3%" | Description !! style="width: 1%" | Video link
|-
! colspan="2" |Positive examples
|-
| Joke tangent from 18:15 - 18:58.
|[https://youtu.be/088Ti7MgkOg?t=1095 DIY curbed wheel fix - was it worth it?]
|-
| Unrelated tangent: 10:03 - 10:37 - Distracted by a caterpillar.
|[https://youtu.be/pAOCiNhQW2Y?t=602 1,074 mph baseball vs. 1 gallon of mayonnaise]
|-
|
|[https://www.youtube.com/watch?v=wbbH77rYaa8 The birth of photography: Drawing with light (and silver iodide)]
|-
|
|[https://www.youtube.com/watch?v=a5YAGYyuA0U Food theory: I quit Diet Coke!]
|-
|
|[https://www.youtube.com/watch?v=1MkrNVic7pw Auto-aiming bow vs. flying targets]
|-
! colspan="2" |Negative examples
|-
| This is quoting a song, which is relevant to the point they are making. || [https://www.youtube.com/watch?v=1MRAo-hwVhQ&t=272s The man who loved an abortion ban]
|-
| None of the examples in this video should be marked since they provide context.
|[https://www.youtube.com/watch?v=QR5MFQnZM3k Nvidia’s stretchy simulation: super quick]
|}
{| class="wikitable"
|+[https://www.youtube.com/watch?v=IZEaYjo4ZJU VFX artist reveals how many solar panels are needed to power the entire world]
!Verdict
!Reason
!Timestamp
!Link
|-
|✅
|Joke analogy that provides no actual information .
|5:33 - 5:36
|[https://www.youtube.com/watch?v=IZEaYjo4ZJU&t=317s Watch from 5:17]
|-
|✅
|Unrelated joke in the middle of content.
|6:40 - 6:50
|[https://www.youtube.com/watch?v=IZEaYjo4ZJU&t=394s Watch from 6:34]
|-
|✅
|Unrelated tangent / joke that is based in fantasy.
|16:33 - 16:39
|[https://www.youtube.com/watch?v=IZEaYjo4ZJU&t=988s Watch from 16:28]
|-
|❌
| On-topic elaboration that provides context and information.
|17:28 - 18:01
|[https://www.youtube.com/watch?v=IZEaYjo4ZJU&t=1047s Watch from 17:27]
|}
{| class="wikitable"
|+[https://www.youtube.com/watch?v=6yur4w0Cfpw Pac-Man World Speedruns Deserve More Love | [https://www.youtube.com/watch?v=6yur4w0Cfpw Pac-Man World speedruns deserve more love]
!Verdict
!Reason
!Timestamp
!Link
|-
|❌
| The clip is too short to clip cleanly.
|0:00 - 0:02
|[https://www.youtube.com/watch?v=6yur4w0Cfpw&t=0s Watch from 0:00]
|-
|✅
| Collection of gameplay clips that do not appear later in the video.
|0:40 - 1:40
|[https://www.youtube.com/watch?v=6yur4w0Cfpw&t=40s Watch from 0:40]
|-
|❌
| The upcoming scene is narrated and a follow-up to earlier content.
|9:52 - 10:07
|[https://www.youtube.com/watch?v=6yur4w0Cfpw&t=588s Watch from 9:48]
|-
|✅
| Unrelated tangent / fun fact.
|10:24 - 10:40
|[https://www.youtube.com/watch?v=6yur4w0Cfpw&t=617s Watch from 10:17]
|}
{| class="wikitable"
|+[https://www.youtube.com/watch?v=YvR7LAsk6tk "Unsafe at any Speed" : The Truth about RECALLS | [https://www.youtube.com/watch?v=YvR7LAsk6tk "Unsafe at any speed": The truth about recalls]
!Verdict
!Reason
!Timestamp
!Link
|-
|✅
| Clip used for humor.
|1:14 - 1:18
|[https://www.youtube.com/watch?v=YvR7LAsk6tk&t=65s Watch from 1:05]
|-
|✅
| Clip used as reference, but ultimately just repetition.
|2:05 - 2:11
|[https://www.youtube.com/watch?v=YvR7LAsk6tk&t=119s Watch from 1:59]
|-
|❌
| Direct quote & used for context.
|3:10 - 3:19
|[https://www.youtube.com/watch?v=YvR7LAsk6tk&t=189s Watch from 3:09]
|-
|✅
| Clip used to accentuate point.
|5:33 - 5:41
|[https://www.youtube.com/watch?v=YvR7LAsk6tk&t=328s Watch from 5:28]
|-
|✅
| Song reference to accentuate point.
|5:45 - 5:49
|[https://www.youtube.com/watch?v=YvR7LAsk6tk&t=341s Watch from 5:41]
|}
{| class="wikitable"
|+[https://www.youtube.com/watch?v=D9u7JDCT47Y The quest to beat Portal glitchless in under 15 minutes]
!Verdict
!Reason
!Timestamp
!Link
|-
|✅
| Gameplay clips that are not built upon, elaborated or used for context.
|0:59 - 1:27
|[https://www.youtube.com/watch?v=D9u7JDCT47Y&t=57s Watch from 0:57]
|-
|✅
| Gameplay clips that are not built upon, elaborated or used for context.
|4:49 - 6:02
|[https://www.youtube.com/watch?v=D9u7JDCT47Y&t=267 Watch from 4:27]
|-
|❌
| Short clip showing the end of the run.
|14:14 - 14:25
|[https://www.youtube.com/watch?v=D9u7JDCT47Y&t=847s Watch from 14:08]
|-
|✅
| Unrelated highlights that don't provide any context or information.
|16:53 - 17:59
|[https://www.youtube.com/watch?v=D9u7JDCT47Y&t=1004s Watch from 16:44]
|}
{| class="wikitable"
|+[https://www.youtube.com/watch?v=S1CDiebvzRM Ratchet & Clank's Amazing Movement Tech | [https://www.youtube.com/watch?v=S1CDiebvzRM Ratchet & Clank's amazing movement tech]
!Verdict
!Reason
!Timestamp
!Link
|-
|✅
| Animation and tangent that isn't required for any context.
|0:19 - 0:37
|[https://www.youtube.com/watch?v=S1CDiebvzRM&t=18s Watch from 0:18]
|-
|✅
| Tangent and clip about Xem as a person and unrelated clip metaphor.
|0:50 - 1:24
|[https://www.youtube.com/watch?v=S1CDiebvzRM&t=39s Watch from 0:39]
|-
|❌
| Cannot be cut cleanly, part of explanation of tech.
|1:34 - 1:41
|[https://www.youtube.com/watch?v=S1CDiebvzRM&t=88s Watch from 1:28]
|-
|❌
| Provides context for movement tech.
|3:00 - 3:12
|[https://www.youtube.com/watch?v=S1CDiebvzRM&t=180s Watch from 3:00]
|-
|✅
| Clip used to accentuate a point.
|3:40 - 3:45
|[https://www.youtube.com/watch?v=S1CDiebvzRM&t=216s Watch from 3:36]
|-
|❌
| Explanation of concept.
|3:45 - 5:03
|[https://www.youtube.com/watch?v=S1CDiebvzRM&t=224s Watch from 3:44]
|-
|✅
| Tangential wordplay.
|5:09 - 5:13
|[https://www.youtube.com/watch?v=S1CDiebvzRM&t=304s Watch from 5:04]
|}

==References==
<references />

[[Category:Segment categories]]

FAQ/New categories

2025-09-15T17:43:51Z

AcesFullOfKings: fancy unicode apostrophes are stupid

{{Message box|mini=1|type=notice
|title=Can you add a segment category for X?
|text=Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases.
}}
New category suggestions may be considered, but they must account for all of the following requirements.

== Necessity ==
Does your suggested category address a widespread need? It's not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

== Commonly-occurring ==
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

== Well-defined ==
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a particular segment should be marked.

== Not protecting a user's mental or physical health ==
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience's health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

== Use of chapters ==
Consider whether a {{Category|chapter}} could be used instead – labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.

== Use of Tangents/Jokes ==
Consider whether a {{Category|tangent}} segment could be used instead – this category is for tangential scenes or jokes which are not required to understand the main content of the video. This is a broad and slightly subjective category, but should not be used simply for scenes that you aren't personally interested in. This category could be used in situations where people who have enabled the category may want to skip an irrelevant section of video.

== Rejected suggestions ==
Below are examples of frequently-suggested categories and the reasons they are not implemented:

=== Epilepsy ===
* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': Although this is an appealing idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than nothing, since it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. It's up to channels to be mindful of epileptics in their audience.

=== Fear or phobia ===
* '''Suggestion''': Skip segments which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.
* '''Reason''': This category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia, then they should avoid videos which may contain spiders. It's up to the channel to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental well-being, which as above is out of scope due to the inherently incomplete/inaccurate database.

=== NSFW / profanity ===
* '''Suggestion''': Skip segments that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate videos in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

=== Jumpscares ===
* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds.
* '''Reason''': This is out of scope as it could fall under protecting users' health – again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider avoiding channels who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc., if they don't want to see jumpscares.

=== AI-generated video ===
* '''Suggestion''': Apply a full-video label to AI-generated videos, or allow skipping or labelling of AI-generated segments.
* '''Reason''': This won't be added in SponsorBlock, but maybe in a future extension if there's interest.

User:AcesFullOfKings/draft

2025-03-28T22:01:33Z

AcesFullOfKings: overhaul page

== Why Your Category Idea is Wrong and Bad ==
So, you think you’ve got a genius new idea for a SponsorBlock category? Wow. Incredible. Truly revolutionary. Unfortunately, it’s also completely unnecessary, totally impractical, and we are here to ruin your dreams with cold, hard logic.

Look, we get it. You’re tired of watching parts of videos you don’t like. But before you race to the suggestion box with your bold new idea, let’s go over why it’s probably already been rejected.

=== Does the World Actually Need This? ===
A new category needs to solve a problem that a LOT of people have, not just you and three of your friends. If your idea isn’t addressing a widespread issue, then congrats! You’ve invented a personal inconvenience, not a useful category. Just... use the fast-forward button like a normal person.

=== Is This a Thing That Happens More Than Twice? ===
A new category should cover something that happens in a large number of videos, not just in that one video that traumatized you in 2017. If it’s something that occurs once in a blue moon, sorry, but that’s what chapters are for.

=== Can You Even Define It? ===
Your category needs to have clear, objective rules, because “uh, I know it when I see it” is not how we run things here. If people are going to argue over whether something belongs in the category, we’d rather not open that can of worms.

=== We Are Not Your Therapist ===
SponsorBlock is not here to protect your fragile psyche. If you’re looking for an automated system to shield you from all distressing content, well, bad news: we are powered by random internet people, and they are unreliable at best. If something is truly upsetting for you, maybe… don’t watch videos that contain it? Just a thought.

=== Chapters and Tangents Exist, Y'know ===
Before suggesting a new category, ask yourself: “Am I just reinventing chapters?” Because if the answer is yes, then congratulations, you’ve wasted everyone’s time. We already have a way to label content without making up an entirely new category for every minor inconvenience.

Now, Let’s Roast Some Common Bad Ideas

=== Epilepsy ===

'''Your Idea''': Mark all the flashy flashy lights so people with epilepsy don’t have a bad time.

'''Why It’s Bad''': This sounds great until you realize it would never, ever be complete. Imagine trusting SponsorBlock to protect you, only to get hit with unmarked strobe lights because—surprise!—some segments were never flagged. False security is worse than no security. The responsibility is on the content creators, not us.

=== Phobias ===

'''Your Idea''': Skip all the spooky things I don’t like, please.

'''Why It’s Bad''': So what do we do, make a category for every possible fear? “Skip-the-Spider,” “Skip-the-Clown,” “Skip-the-Wet-Socks?” There are too many possible phobias to make this viable. Plus, avoiding scary stuff is a personal responsibility. If you’re terrified of spiders, maybe don’t watch "World’s Biggest Spider Compilation" in the first place.

=== NSFW/Profanity ===

'''Your Idea''': Keep my innocent ears safe from bad words and scandalous content.

'''Why It’s Bad''': NSFW means different things to different people. Some folks are fine with mild swearing, others faint at a single “heck.” If you need absolute purity, consider YouTube Kids. Or, hear me out: don’t watch videos with swear words in them?

=== Jumpscares ===

'''Your Idea''': Save me from the scary loud noises.

'''Why It’s Bad''': Okay, jumpscares suck. We get it. But you know what else sucks? Relying on strangers to catch every single one. Also, jumpscares are surprisingly rare outside of horror content, so if you’re getting scared regularly… maybe stop watching horror games and ghost videos? Wild suggestion, I know.

=== AI-Generated Videos ===

'''Your Idea''': Let’s label all the AI trash!

'''Why It’s Bad''': First, defining "AI-generated" is a mess. Second, some AI-generated content is painfully obvious, while other stuff is sneaky good. Third, SponsorBlock isn’t here to tell you what’s low-quality garbage—if you don’t like AI videos, just block those channels and move on with your life.

=== In Conclusion ===
Most new category suggestions fall into one of three categories:

* Something that doesn’t happen enough to matter.

* Something so subjective that it would cause endless debates.

* Something you should just deal with yourself.

So, before you suggest another category, ask yourself: “Am I about to waste everyone’s time?” If the answer is yes… congrats, you’re officially part of the problem. :D

User:AcesFullOfKings/draft

2025-03-28T21:56:01Z

AcesFullOfKings: Initial commit

== Why Your Category Idea is Wrong and Bad ==
So, you think you’ve got a genius new idea for a SponsorBlock category? Wow. Incredible. Truly revolutionary. Unfortunately, it’s also completely unnecessary, totally impractical, and we are here to ruin your dreams with cold, hard logic.

Look, we get it. You’re tired of watching parts of videos you don’t like. But before you race to the suggestion box with your bold new idea, let’s go over why it’s probably already been rejected.

=== Does the World Actually Need This? ===
A new category needs to solve a problem that a LOT of people have, not just you and three of your friends. If your idea isn’t addressing a widespread issue, then congrats! You’ve invented a personal inconvenience, not a useful category. Just... use the fast-forward button like a normal person.

=== Is This a Thing That Happens More Than Twice? ===
A new category should cover something that happens in a large number of videos, not just in that one video that traumatized you in 2017. If it’s something that occurs once in a blue moon, sorry, but that’s what chapters are for.

=== Can You Even Define It? ===
Your category needs to have clear, objective rules, because “uh, I know it when I see it” is not how we run things here. If people are going to argue over whether something belongs in the category, we’d rather not open that can of worms.

=== We Are Not Your Therapist ===
SponsorBlock is not here to protect your fragile psyche. If you’re looking for an automated system to shield you from all distressing content, well, bad news: we are powered by random internet people, and they are unreliable at best. If something is truly upsetting for you, maybe… don’t watch videos that contain it? Just a thought.

=== Chapters and Tangents Exist, Y'know ===
Before suggesting a new category, ask yourself: “Am I just reinventing chapters?” Because if the answer is yes, then congratulations, you’ve wasted everyone’s time. We already have a way to label content without making up an entirely new category for every minor inconvenience.

Now, Let’s Roast Some Common Bad Ideas

=== Epilepsy ===

'''Your Idea''': Mark all the flashy flashy lights so people with epilepsy don’t have a bad time.

'''Why It’s Bad''': This sounds great until you realize it would never, ever be complete. Imagine trusting SponsorBlock to protect you, only to get hit with unmarked strobe lights because—surprise!—some segments were never flagged. False security is worse than no security. The responsibility is on the content creators, not us.

=== Phobias ===

'''Your Idea''': Skip all the spooky things I don’t like, please.

'''Why It’s Bad''': So what do we do, make a category for every possible fear? “Skip-the-Spider,” “Skip-the-Clown,” “Skip-the-Wet-Socks?” There are too many possible phobias to make this viable. Plus, avoiding scary stuff is a personal responsibility. If you’re terrified of spiders, maybe don’t watch "World’s Biggest Spider Compilation" in the first place.

=== NSFW/Profanity ===

'''Your Idea''': Keep my innocent ears safe from bad words and scandalous content.

'''Why It’s Bad''': NSFW means different things to different people. Some folks are fine with mild swearing, others faint at a single “heck.” If you need absolute purity, consider YouTube Kids. Or, hear me out: don’t watch videos with swear words in them?

=== Jumpscares ===

'''Your Idea''': Save me from the scary loud noises.

'''Why It’s Bad''': Okay, jumpscares suck. We get it. But you know what else sucks? Relying on strangers to catch every single one. Also, jumpscares are surprisingly rare outside of horror content, so if you’re getting scared regularly… maybe stop watching horror games and ghost videos? Wild suggestion, I know.

=== AI-Generated Videos ===

'''Your Idea''': Let’s label all the AI trash!

'''Why It’s Bad''': First, defining "AI-generated" is a mess. Second, some AI-generated content is painfully obvious, while other stuff is sneaky good. Third, SponsorBlock isn’t here to tell you what’s low-quality garbage—if you don’t like AI videos, just block those channels and move on with your life.

In Conclusion

Most new category suggestions fall into one of three categories:

Something that doesn’t happen enough to matter.

Something so subjective that it would cause endless debates.

Something you should just deal with yourself.

So, before you suggest another category, ask yourself: “Am I about to waste everyone’s time?” If the answer is yes… congrats, you’re officially part of the problem. :D

Reporting incorrect submissions

2025-03-16T10:47:21Z

AcesFullOfKings: Add emoji reactions

To report an incorrect SponsorBlock segment, you can send a message in the [https://discord.com/channels/603643120093233162/655247785561554945 #incorrect-submissions] channel on Discord or Matrix.

You can copy the template text below and add the appropriate information. Once you send the report, a VIP will check it and take action as necessary.

<pre>
YouTube URL:

Segment type and timestamp:

Brief description of the issue (1-2 sentences):
</pre>

== Actioning reported submissions ==
A VIP may decide to remove the reported segments, and submitters who repeatedly ignore the guidelines may receive a warning or a ban.

The YouTube URL in your report message will generate an embedded thumbnail in the channel. '''Don't remove the embed!''' The embed will be removed automatically once a VIP has actioned the report, so embeds are used as a glanceable way to see which reports have already been handled.

==Use of Emoji Reactions==

Once the VIP has actioned the report, they will react to your message with either the ✅ or ❌ emoji to signify whether the report was correct. These reactions will remove the embedded thumbnail in your original message.

Other emoji may be used as follows:

⏲️ - the report is currently being investigated

✅ - report handled and was correct (hides the embed)

❌ - report handled and was incorrect (hides the embed)

🔒 - video/segment locked

⚠️ - a warning was issued

🔨 - user was banned

🗑️ - video purged (all segments hidden)

[[Category:User guides]]

User:AcesFullOfKings/todo

2025-03-10T19:07:37Z

AcesFullOfKings: tick off completed

List of pages that I will totally definitely get around to writing one day:

* Why SB can never support podcasts

Reporting incorrect submissions

2025-03-10T18:57:45Z

AcesFullOfKings: First commit

== Reporting Incorrect Submissions ==

To report an incorrect SponsorBlock segment, you can send a message in the [https://discord.com/channels/603643120093233162/655247785561554945 #incorrect-submissions] channel in the Discord.

You can copy the below template text and add the appropriate information. Once you send the report a VIP will check it and take action as necessary.

<blockquote>
Youtube url:

Segment type and timestamp:

Brief description of the issue (1-2 sentences):
</blockquote>

== Actioning Reported Submissions ==

A VIP may decide to remove the segment(s), and submitters who repeatedly ignore the guidelines may receive a warning or a ban.

The YouTube url in your report message will generate an embedded thumbnail in the discord channel. '''Don't remove the embed!''' The embed will be removed automatically once the VIP has actioned the report, so embeds are used as a glanceable way to see which reports have already been actioned.

Once the VIP has actioned the report, they will react to your message with either the ✅ or ❌ emoji to signify whether the report was correct. This reaction will trigger the bot to remove the embed.

User:AcesFullOfKings/draft/Reporting Incorrect Submissions

2025-03-10T18:52:47Z

AcesFullOfKings: add the actual template..

== Reporting Incorrect Submissions ==

You can copy the below and add the appropriate information to create a report about an incorrect submission. If you send this report as a message in [https://discord.com/channels/603643120093233162/655247785561554945 #incorrect-submissions] then a VIP will check it and take action as necessary.

<blockquote>
Youtube url:

Segment type and timestamp:

Brief description of the issue (1-2 sentences):
</blockquote>
== Actioning Reported Submissions ==

A VIP may decide to remove the segment(s), and submitters who repeatedly ignore the guidelines may receive a warning or a ban.

The YouTube url in your report message will generate an embedded thumbnail in the discord channel. '''Don't remove the embed!''' The embed will be removed automatically once the VIP has actioned the report, so embeds are used as a glanceable way to see which reports have already been actioned.

Once the VIP has actioned the report, they will react to your message with either the ✅ or ❌ emoji to signify whether the report was correct. This reaction will trigger the bot to remove the embed.

User:AcesFullOfKings/draft

2025-03-10T18:48:59Z

AcesFullOfKings: Blanked the page

User:AcesFullOfKings/draft/Reporting Incorrect Submissions

2025-03-10T18:34:19Z

AcesFullOfKings: Created page with "== Reporting Incorrect Submissions == You can copy the below and add the appropriate information to create a report about an incorrect submission. If you send this report as a message in [https://discord.com/channels/603643120093233162/655247785561554945 #incorrect-submissions] then a VIP will check it and take action as necessary. == Actioning Reported Submissions == A VIP may decide to remove the segment(s), and submitters who repeatedly ignore the guidelines may re..."

== Reporting Incorrect Submissions ==

You can copy the below and add the appropriate information to create a report about an incorrect submission. If you send this report as a message in [https://discord.com/channels/603643120093233162/655247785561554945 #incorrect-submissions] then a VIP will check it and take action as necessary.

== Actioning Reported Submissions ==

A VIP may decide to remove the segment(s), and submitters who repeatedly ignore the guidelines may receive a warning or a ban.

The YouTube url in your report message will generate an embedded thumbnail in the discord channel. '''Don't remove the embed!''' The embed will be removed automatically once the VIP has actioned the report, so embeds are used as a glanceable way to see which reports have already been actioned.

Once the VIP has actioned the report, they will react to your message with either the ✅ or ❌ emoji to signify whether the report was correct. This reaction will trigger the bot to remove the embed.

User:AcesFullOfKings/draft

2025-03-10T18:11:03Z

AcesFullOfKings: first draft

== Reporting Incorrect Submissions ==

You can copy the below and add the appropriate information to create a report about an incorrect submission. If you send this report as a message in [https://discord.com/channels/603643120093233162/655247785561554945 #incorrect-submissions] then a VIP will check it and take action as necessary.

== Actioning Reported Submissions ==

A VIP may decide to remove the segment(s), and submitters who repeatedly ignore the guidelines may receive a warning or a ban.

The YouTube url in your report message will generate an embedded thumbnail in the discord channel. '''Don't remove the embed!''' The embed will be removed automatically once the VIP has actioned the report, so embeds are used as a glanceable way to see which reports have already been actioned.

Once the VIP has actioned the report, they will react to your message with either the ✅ or ❌ emoji to signify whether the report was correct. This reaction will trigger the bot to remove the embed.

User:AcesFullOfKings/todo

2025-03-10T17:55:03Z

AcesFullOfKings:

List of pages that I will totally definitely get around to writing one day:

* Why SB can never support podcasts
* Why users who go into settings and then turn on the "please skip jokes" setting and then complain about jokes being skipped are wrong
* A template for reports in #incorrect-submissions

User:AcesFullOfKings/todo

2025-03-07T18:46:54Z

AcesFullOfKings: Created page with "List of pages that I will totally definitely get around to writing one day: * Why SB can never support podcasts * Why users who go into settings and then turn on the "please skip jokes" setting and then complain about jokes being skipped are wrong"

FAQ/New categories

2025-02-10T01:20:54Z

AcesFullOfKings:

{{Message box|mini=1|type=notice
|title=Can you add a segment category for X?
|text=Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases.
}}
New category suggestions may be considered, but they must account for all of the following requirements.

== Necessity ==
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

== Commonly-occurring ==
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

== Well-defined ==
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a particular segment should be marked.

== Not protecting a user's mental or physical health ==
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

== Use of chapters ==
Consider whether a {{Category|chapter}} could be used instead – labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.

== Use of Tangents/Jokes ==
Consider whether a {{Category|tangent}} segment could be used instead – this category is for tangential scenes or jokes which are not required to understand the main content of the video. This is a broad and slightly subjective category, but should not be used simply for scenes that you aren't personally interested in. This category could be used in situations where people who have enabled the category may want to skip an irrelevant section of video.

== Rejected suggestions ==
Below are examples of frequently-suggested categories and the reasons they are not implemented:

=== Epilepsy ===
* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': although this is an appealing idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than nothing, since it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. It's up to creators to be mindful of epileptics in their audience.

=== Fear or phobia ===
* '''Suggestion''': skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.
* '''Reason''': this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia, then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

=== NSFW content / profanity ===
* '''Suggestion''': skip content that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

=== Jumpscares ===
* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds
* '''Reason''': this is out of scope as it could fall under protecting users' health - again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider avoiding creators who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc if they don't want to see jumpscares.

=== AI-generated Video ===
* '''Suggestion''': Apply a full-video label to AI-generated videos, or allow skipping or labelling of AI-generated segments.
* '''Reason''': this may be difficult to moderate, is not easy to define, and is arguably not necessary. AI-generated content is sometimes obvious but can be deceptively realistic, so identifying it may be difficult. In addition, there's a potential blurry line between skillful video editing by a competent human, vs low-effort generative AI. SponsorBlock is not intended to make a subjective statement about whether content is "good"/worth watching: it's up to the user to not watch channels which publish low-quality content, and to block the channel from their recommendations.

VIP

2025-02-04T19:01:51Z

AcesFullOfKings: /* How can I become a VIP? */ fix formatting

VIP permission allows a user to have moderation-like powers in SponsorBlock. In the [https://sb.ltn.fi/ database explorer] you can recognize them by the 👑 (crown) next to their votes. On the [https://discord.gg/QnmVMpU discord] you can recognize them by their VIP role and maybe a green or light-green colored username.

== Moderating segments ==
VIP downvotes and upvotes have more power. Downvotes will remove segments immediately.

VIP submitted or upvoted segments will be locked by default. These segments will always be shown instead of similarly timed but unlocked segments and can only be removed by other VIPs. In the [https://sb.ltn.fi/ database explorer], locked segments can be identified by a 🔒 (lock) icon next to the number of votes.

VIPs can also lock categories on videos to prevent future submissions for one or more categories and action types. This is typically done to prevent future submissions if there are no missing segments for that category and all existing segments are perfectly timed. Usually, Highlights and Filler are not locked as those categories are more subjective.

If you think a VIP has made a mistake, send a link to the video along with a brief explanation to the #incorrect-submissions channel in the [https://discord.gg/QnmVMpU discord].

== Moderating users ==
Users can be moderated in two ways: bans and warnings.

Warnings are issued to users who make common mistakes when submitting segments. Upon trying to submit their next segment or voting on a segment they will receive a popup prompting them to ask about their warning on [https://discord.gg/QnmVMpU discord] or [https://matrix.to/#/+sponsorblock:ajay.app Matrix].

A ban is always approved by at least two VIPs. The ban may also entail the removal of all submissions.

Behavior that will result in a ban consists of but is not limited to:
*Malicious segments such as:
**Censoring certain people regardless of what they did or who they are.
**Censoring a part of a video containing information which is not a sponsor or other valid segment. (Politics, Religion, etc).
**Submitting segments to stop people from viewing creators.
**Vandalizing a video by submitting many incorrect segments, making the video hard to watch.
*Submitting segments that are consistently badly timed. If the segment degrades the [[Guidelines#Reduces_viewer_experience |viewer experience]] because it is badly timed, it shouldn't be there in the first place.
*Submitting segments for sponsors, intros, self-promos, etc. that do not exist.
*Submitting incorrect segments that are absurdly long to try and farm saved time and skips.

== How can I become a VIP? ==
You should have been making consistently good segments for at least a few months. You should have a good grasp on any categories you've made a submission in, and you should not have any major mistakes that we would normally issue warnings for (See Guidelines).

Pick up the <code>Requesting To be a VIP</code> role in [https://discord.com/channels/603643120093233162/660516334018494489/660516691637305374 #get-roles] on Discord

Create a new thread in #vip-request with your publicID.

Expect that your recent submissions will be scrutinised, and if you've been making consistent, high quality contributions then your application may be considered.

== I am a new VIP. How does stuff work? ==
Check [[VIP_Guide|this article]] out.

[[Category:User guides]]

VIP

2025-02-04T18:28:01Z

AcesFullOfKings: /* How can I become a VIP? */ revert vandalism

VIP permission allows a user to have moderation-like powers in SponsorBlock. In the [https://sb.ltn.fi/ database explorer] you can recognize them by the 👑 (crown) next to their votes. On the [https://discord.gg/QnmVMpU discord] you can recognize them by their VIP role and maybe a green or light-green colored username.

== Moderating segments ==
VIP downvotes and upvotes have more power. Downvotes will remove segments immediately.

VIP submitted or upvoted segments will be locked by default. These segments will always be shown instead of similarly timed but unlocked segments and can only be removed by other VIPs. In the [https://sb.ltn.fi/ database explorer], locked segments can be identified by a 🔒 (lock) icon next to the number of votes.

VIPs can also lock categories on videos to prevent future submissions for one or more categories and action types. This is typically done to prevent future submissions if there are no missing segments for that category and all existing segments are perfectly timed. Usually, Highlights and Filler are not locked as those categories are more subjective.

If you think a VIP has made a mistake, send a link to the video along with a brief explanation to the #incorrect-submissions channel in the [https://discord.gg/QnmVMpU discord].

== Moderating users ==
Users can be moderated in two ways: bans and warnings.

Warnings are issued to users who make common mistakes when submitting segments. Upon trying to submit their next segment or voting on a segment they will receive a popup prompting them to ask about their warning on [https://discord.gg/QnmVMpU discord] or [https://matrix.to/#/+sponsorblock:ajay.app Matrix].

A ban is always approved by at least two VIPs. The ban may also entail the removal of all submissions.

Behavior that will result in a ban consists of but is not limited to:
*Malicious segments such as:
**Censoring certain people regardless of what they did or who they are.
**Censoring a part of a video containing information which is not a sponsor or other valid segment. (Politics, Religion, etc).
**Submitting segments to stop people from viewing creators.
**Vandalizing a video by submitting many incorrect segments, making the video hard to watch.
*Submitting segments that are consistently badly timed. If the segment degrades the [[Guidelines#Reduces_viewer_experience |viewer experience]] because it is badly timed, it shouldn't be there in the first place.
*Submitting segments for sponsors, intros, self-promos, etc. that do not exist.
*Submitting incorrect segments that are absurdly long to try and farm saved time and skips.

== How can I become a VIP? ==
You should have been making consistently good segments for at least a few months. You should have a good grasp on any categories you've made a submission in, and you should not have any major mistakes that we would normally issue warnings for (See Guidelines).

Pick up the `Requesting To be a VIP` role in #help-out on Discord Create a new thread in #vip-request with your publicID. Expect that your recent submissions will be scrutinised, and if you've been making consistent, high quality contributions then your application may be considered. 

== I am a new VIP. How does stuff work? ==
Check [[VIP_Guide|this article]] out.

[[Category:User guides]]

FAQ

2024-12-16T10:26:40Z

AcesFullOfKings: Add new category link

==What are the most frequent mistakes when submitting segments?==
*Not including the segue (smooth verbal transition to the [[Sponsor | sponsor]])
*Submitting [[Sponsor | sponsor]] segments on videos that are either solely about the sponsor '''or''' could show bias towards it (e.g. when using the sponsored product is an essential part of the video's content and the creator voices their opinion, viewers need to be aware of the sponsor disclosure)
*Mistaking [[Unpaid/Self_Promotion | self promotion]] for a sponsorship
*Segments at the very beginning not starting precisely at 0:00, but rather something like 0.0314159 seconds into the video. Similarly, segments not sticking to the exact end of the video when they should.
*Misunderstanding of the [[Intermission/Intro_Animation | intermission]] category. More often than not, it should not contain any spoken words, and it's not meant for just about anything that users find insignificant, like the creator saying "hello."
Please check out [[Advice_for_submitting | this page]] for more tips.

==I noticed an incorrect submission. What should I do?==
The first thing you can do is simply downvote it in the pop-up. If it's just the wrong category but correctly timed, you can select "Wrong Category" after clicking the pencil icon. Additionally, when the timing of an existing segment could be better, submitting your own correct segment in its place may reduce the amount of times the faulty one appears.

If you're on SponsorBlock [https://discord.gg/QnmVMpU Discord server], feel free to report it in the #incorrect-submissions channel, where a [[VIP]] can take a look at it. Even if the video is not in English, you can still give it a shot. Especially if you believe it’s a purposefully malicious spam, we would really like to be notified.

==Why am I getting an error when trying to submit a segment?==
400: Bad Request (Your inputs are wrong/impossible)
*Your segment is maybe 0 seconds long
*There is a minimum length for Sponsor segments
*If the message says "no valid userID", you might not have a valid private userID set - sometimes it might fail to generate on installation. See [https://github.com/ajayyy/SponsorBlock/issues/1606 issue #1606] for more information.
403: Rejected by auto moderator:
*A human moderator has locked the category or the complete video, all the segments that are needed are there and timed perfectly. If there isn't already a segment where you want to add one, try reloading the video. Make sure that you have activated all categories, as the segment you want to add is maybe in the wrong category. The video is locked to prevent spamming of bad segments that need to be removed later.
409: Duplicate: You already submitted this segment, delete the one you can still add and all should be good

==How is “non-music” supposed to co-exist with other categories?==
[[Music:_Non-Music_Section | Non-music]] exists separately from other categories and may overlap with them. In the end, the video should resemble the Spotify or any other mix version as close as possible.

==What are advanced tips for submitting?==
You can find many tips in [[Advice_for_submitting | this article]].


==How to browse the database and view all my submissions with details?==
*You can view the database and all submissions on this website: https://sb.ltn.fi/ (this should update every 5 minutes)
*You can download the entire database [https://sponsor.ajay.app/database here].
Note: Your public userID in the database is different than your private one in the SponsorBlock options tab.

==Can I edit/remove the segment that I uploaded?==
Once your segment is uploaded, you can still easily remove it or change its category by clicking thumbs down on the skip notice and choosing "Incorrect/Wrong Timing" or "Wrong Category" respectively. In case of your own submissions, your votes will have an immediate effect.

Editing timestamps of submitted segments is not possible, so in order to correct a segment downvote it and submit a new one.
==I think my segment might have been deleted. Why?==
One possibility is that other users downvoted it. If it was removed by a moderator however, possible reasons include:
*Some other submission in that place was a bit better (even if it’s just a fraction of a second, it does make a difference)
*It was against the [[Guidelines]]
*Any mistake mentioned in [[FAQ#What_are_the_most_frequent_mistakes_when_submitting_segments.3F | answer #1]]

==How does voting work and what do certain amounts of votes mean?==
Overlapping segments of the same category don't get shown all at once, but instead compete with each other, appearing to users one at a time. The amount of votes determines how likely your submission is to be shown over the other ones. You can read more about the algorithm and grouping similar segments [https://blog.ajay.app/voting-and-pseudo-randomness-or-sponsorblock-or-youtube-sponsorship-segment-blocker here].

When a submission reaches the score of -2 or lower, it gets removed and will not appear anymore for users, but can still be found in the database. It also takes two votes to change the category of someone else's segment. If you downvote your own segment, it will be immediately removed and you won't lose any reputation.

If a segment has a padlock next to it, it means it has been locked and will be prioritized over any other segment. [[VIP |VIPs']] segments are always locked, due to them being trusted.

==Are there any moderators?==
People with the [[VIP]] permission can moderate submissions. You can recognize them in Discord by their [[VIP]] tag. Learn more [[VIP | here]].

==Can I use SponsorBlock on platforms other than PC?==
Yes. Aside from the web browser extension, there are various third-party ports, including mobile. See the list [https://github.com/ajayyy/SponsorBlock/wiki/3rd-Party-Ports here].

==How can I transfer my Vanced userID to the desktop extension?==
Warning: You can only keep one userID, so decide if you want to keep the your extension userID or your Vanced userID. Keep a backup of your private userID in a secure location. If you want to transfer your extension user to Vanced, you will have to reverse the process.

To transfer your userID from Vanced to the extension:
*In Vanced click on your user icon -> settings -> SponsorBlock settings -> "your unique userID"
*Copy this string and save it somewhere
*In your browser, click on the SponsorBlock icon in your toolbar and click on options
*Scroll down to "Import/Export your UserID"
*Back up the current userID and save it somewhere safe in case you want to switch back to it
*Paste your userID there and confirm the changes
*Your userID is now transferred. The popup will show stats based on what you have submitted from Vanced.

Some data cannot be transferred, like segments you've skipped and time you saved others, because it is only saved anonymized.

== What is the mute option when submitting? ==
Normally a segment would just skip to the end. The [[Mute_Segment |mute segment]] will mute the video and play the segment. Once you have reached the end of the segment, the video will be unmuted.

==Can I create skip segments just for myself?==
Yes. If you wish to have skip segments for your personal use, not caring about the rules, just select the timestamps and close the editing box. Make sure not to click "submit". They will be stored locally in your browser and skipped automatically. You can also export them with your options.

== What is considered content?==
Content is any part of the video which someone could find valuable to watch. Finding something a waste of time personally does not mean that someone else wants to skip it.
==Is there any AI involved?==
[https://github.com/andrewzlee/NeuralBlock NeuralBlock] is a neural network that detects in-video YouTube sponsorships, though current implementation within SponsorBlock is limited to a moderation tool which detects incorrect sponsor segments on English videos. Every SponsorBlock segment you see on YouTube has been made by a human (as far as we know).

== Can you add a segment category for X? ==
If you have a suggestion for a new category, please review the considerations and common suggestions in [[FAQ/New categories|this article]].
[[Category:SponsorBlock User Guides]]

FAQ/New categories

2024-12-16T09:24:04Z

AcesFullOfKings: /* Jumpscares */ remove suggestion to leave a dislike

== Can you add a segment category for X? ==
Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases. New category suggestions may be considered, but must account for the following:

=== Considerations ===

==== Necessity ====
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

==== Commonly-occurring ====
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

==== Well-defined ====
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a partucular segment should be marked.

==== Not protecting a user's mental or physical health ====
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

==== Use of Chapters ====
Consider whether a [[chapter]] could be used instead - labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.

==== Use of Filler ====
Consider whether a [[Filler Tangent/Jokes|filler]] segment could be used instead - filler is for tangential scenes which are added only for filler or humour and are not required to understand the main content of the video. This is a broad and slightly subjective category, but should not be used simply for scenes that you aren't personally interested in. This category could be used in situations where people who have enabled filler may want to skip an irrelevant section of video.

=== Rejected suggestions ===
Below are examples of frequently-suggested categories and the reasons they are not implemented:

==== Epilepsy ====

* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': although this is an appealing idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than nothing since it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. It's up to creators to be mindful of epileptics in their audience.

==== Fear/Phobia ====

* '''Suggestion''': skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.

* '''Reason''': this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

==== NSFW content / profanity ====
* '''Suggestion''': skip content that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

==== Jumpscares ====
* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds
* '''Reason''': this is out of scope as it could fall under protecting users' health - again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider avoiding creators who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc if they don't want to see jumpscares.

==== AI-generated Video ====
* '''Suggestion''': Apply a full-video label to AI-generated videos, or allow skipping or labelling of AI-generated segments.
* '''Reason''': this may be difficult to moderate, is not easy to define, and is arguably not necessary. AI-generated content is sometimes obvious but can be deceptively realistic, so identifying it may be difficult. In addition, there's a potential blurry line between skillful video editing by a competent human, vs low-effort generative AI. SponsorBlock is not intended to make a subjectve statement about whether content is "good"/worth watching: it's up to the user to not watch channels which publish low-quality content, and to block the channel from their recommendations.

FAQ/New categories

2024-12-14T21:16:27Z

AcesFullOfKings: Initial commit

== Can you add a segment category for X? ==
Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases. New category suggestions may be considered, but must account for the following:

=== Considerations ===

==== Necessity ====
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

==== Commonly-occurring ====
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

==== Well-defined ====
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a partucular segment should be marked.

==== Not protecting a user's mental or physical health ====
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

==== Use of Chapters ====
Consider whether a [[chapter]] could be used instead - labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.

==== Use of Filler ====
Consider whether a [[Filler Tangent/Jokes|filler]] segment could be used instead - filler is for tangential scenes which are added only for filler or humour and are not required to understand the main content of the video. This is a broad and slightly subjective category, but should not be used simply for scenes that you aren't personally interested in. This category could be used in situations where people who have enabled filler may want to skip an irrelevant section of video.

=== Rejected suggestions ===
Below are examples of frequently-suggested categories and the reasons they are not implemented:

==== Epilepsy ====

* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': although this is an appealing idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than nothing since it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. It's up to creators to be mindful of epileptics in their audience.

==== Fear/Phobia ====

* '''Suggestion''': skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.

* '''Reason''': this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

==== NSFW content / profanity ====
* '''Suggestion''': skip content that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

==== Jumpscares ====
* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds
* '''Reason''': this is out of scope as it could fall under protecting users' health - again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider leaving a dislike and avoiding creators who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc if they don't want to see jumpscares.

==== AI-generated Video ====
* '''Suggestion''': Apply a full-video label to AI-generated videos, or allow skipping or labelling of AI-generated segments.
* '''Reason''': this may be difficult to moderate, is not easy to define, and is arguably not necessary. AI-generated content is sometimes obvious but can be deceptively realistic, so identifying it may be difficult. In addition, there's a potential blurry line between skillful video editing by a competent human, vs low-effort generative AI. SponsorBlock is not intended to make a subjectve statement about whether content is "good"/worth watching: it's up to the user to not watch channels which publish low-quality content, and to block the channel from their recommendations.

User:AcesFullOfKings/draft

2024-12-14T17:15:14Z

AcesFullOfKings: /* Rejected suggestions */

== Can you add a segment category for X? ==
Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases. New category suggestions may be considered, but must account for the following:

=== Considerations ===

==== Necessity ====
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

==== Commonly-occurring ====
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

==== Well-defined ====
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a partucular segment should be marked.

==== Not protecting a user's mental or physical health ====
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

==== Use of Chapters ====
Consider whether a [[chapter]] could be used instead - labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.

==== Use of Filler ====
Consider whether a [[Filler Tangent/Jokes|filler]] segment could be used instead - filler is for tangential scenes which are added only for filler or humour and are not required to understand the main content of the video. This is a broad and slightly subjective category, but should not be used simply for scenes that you aren't personally interested in. This category could be used in situations where people who have enabled filler may want to skip an irrelevant section of video.

=== Rejected suggestions ===
Below are examples of frequently-suggested categories and the reasons they are not implemented:

==== Epilepsy ====

* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': although this is an appealing idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than nothing since it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. It's up to creators to be mindful of epileptics in their audience.

==== Fear/Phobia ====

* '''Suggestion''': skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.

* '''Reason''': this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

==== NSFW content / profanity ====
* '''Suggestion''': skip content that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

==== Jumpscares ====
* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds
* '''Reason''': this is out of scope as it could fall under protecting users' health - again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider leaving a dislike and avoiding creators who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc if they don't want to see jumpscares.

==== AI-generated Video ====
* '''Suggestion''': Apply a full-video label to AI-generated videos, or allow skipping or labelling of AI-generated segments.
* '''Reason''': this may be difficult to moderate, is not easy to define, and is arguably not necessary. AI-generated content is sometimes obvious but can be deceptively realistic, so identifying it may be difficult. In addition, there's a potential blurry line between skillful video editing by a competent human, vs low-effort generative AI. SponsorBlock is not intended to make a subjectve statement about whether content is "good"/worth watching: it's up to the user to not watch channels which publish low-quality content, and to block the channel from their recommendations.

User:AcesFullOfKings/draft

2024-12-14T17:13:48Z

AcesFullOfKings: /* Rejected suggestions: */

== Can you add a segment category for X? ==
Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases. New category suggestions may be considered, but must account for the following:

=== Considerations ===

==== Necessity ====
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

==== Commonly-occurring ====
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

==== Well-defined ====
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a partucular segment should be marked.

==== Not protecting a user's mental or physical health ====
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

==== Use of Chapters ====
Consider whether a [[chapter]] could be used instead - labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.

==== Use of Filler ====
Consider whether a [[Filler Tangent/Jokes|filler]] segment could be used instead - filler is for tangential scenes which are added only for filler or humour and are not required to understand the main content of the video. This is a broad and slightly subjective category, but should not be used simply for scenes that you aren't personally interested in. This category could be used in situations where people who have enabled filler may want to skip an irrelevant section of video.

=== Rejected suggestions ===
Below are examples of frequently suggested categories and the reasons they are not implemented:

==== Epilepsy ====

* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': although this is a nice idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than useless as it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. It's up to creators to be mindful of epileptics in their audience.

==== Fear/Phobia ====

* '''Suggestion''': skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.

* '''Reason''': this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

==== NSFW content / profanity ====
* '''Suggestion''': skip content that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

==== Jumpscares ====
* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds
* '''Reason''': this is out of scope as it could fall under protecting users' health - again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider leaving a dislike and avoiding creators who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc if they don't want to see jumpscares.

==== AI-generated Video ====
* '''Suggestion''': Apply a full-video label to AI-generated videos, or allow skipping or labelling of AI-generated segments.
* '''Reason''': this may be difficult to moderate, is not easy to define, and is arguably not necessary. AI-generated content is sometimes obvious but can be deceptively realistic, so identifying it may be difficult. In addition, there's a potential blurry line between skillful video editing by a competent human, vs low-effort generative AI. SponsorBlock is not intended to make a subjectve statement about whether content is "good"/worth watching: it's up to the user to not watch channels which publish low-quality content, and to block the channel from their recommendations.

User:AcesFullOfKings/draft

2024-12-14T14:14:46Z

AcesFullOfKings: /* AI-generated Video */ remove recommendation to dislike bad videos

== Can you add a segment category for X? ==
Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases. New category suggestions may be considered, but must account for the following:

=== Considerations ===

==== Necessity ====
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

==== Commonly-occurring ====
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

==== Well-defined ====
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a partucular segment should be marked.

==== Not protecting a user's mental or physical health ====
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

==== Use of Chapters ====
Consider whether a [[chapter]] could be used instead - labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.

==== Use of Filler ====
Consider whether a [[Filler Tangent/Jokes|filler]] segment could be used instead - filler is for tangential scenes which are added only for filler or humour and are not required to understand the main content of the video. This is a broad and slightly subjective category, but should not be used simply for scenes that you aren't personally interested in. This category could be used in situations where people who have enabled filler may want to skip an irrelevant section of video.

=== Rejected suggestions: ===
Below are examples of frequently suggested categories and the reasons they are not implemented:

==== Epilepsy ====

* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': although this is a nice idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than useless as it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. It's up to creators to be mindful of epileptics in their audience.

==== Fear/Phobia ====

* '''Suggestion''': skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.

* '''Reason''': this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

==== NSFW content / profanity ====
* '''Suggestion''': skip content that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

==== Jumpscares ====
* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds
* '''Reason''': this is out of scope as it could fall under protecting users' health - again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider leaving a dislike and avoiding creators who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc if they don't want to see jumpscares.

==== AI-generated Video ====
* '''Suggestion''': Apply a full-video label to AI-generated videos, or allow skipping or labelling of AI-generated segments.
* '''Reason''': this may be difficult to moderate, is not easy to define, and is arguably not necessary. AI-generated content is sometimes obvious but can be deceptively realistic, so identifying it may be difficult. In addition, there's a potential blurry line between skillful video editing by a competent human, vs low-effort generative AI. SponsorBlock is not intended to make a subjectve statement about whether content is "good"/worth watching: it's up to the user to not watch channels which publish low-quality content, and to block the channel from their recommendations.

User:AcesFullOfKings/draft

2024-12-14T14:09:26Z

AcesFullOfKings: /* Epilepsy */

== Can you add a segment category for X? ==
Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases. New category suggestions may be considered, but must account for the following:

=== Considerations ===

==== Necessity ====
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

==== Commonly-occurring ====
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

==== Well-defined ====
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a partucular segment should be marked.

==== Not protecting a user's mental or physical health ====
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

==== Use of Chapters ====
Consider whether a [[chapter]] could be used instead - labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.

==== Use of Filler ====
Consider whether a [[Filler Tangent/Jokes|filler]] segment could be used instead - filler is for tangential scenes which are added only for filler or humour and are not required to understand the main content of the video. This is a broad and slightly subjective category, but should not be used simply for scenes that you aren't personally interested in. This category could be used in situations where people who have enabled filler may want to skip an irrelevant section of video.

=== Rejected suggestions: ===
Below are examples of frequently suggested categories and the reasons they are not implemented:

==== Epilepsy ====

* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': although this is a nice idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than useless as it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. It's up to creators to be mindful of epileptics in their audience.

==== Fear/Phobia ====

* '''Suggestion''': skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.

* '''Reason''': this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

==== NSFW content / profanity ====
* '''Suggestion''': skip content that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

==== Jumpscares ====
* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds
* '''Reason''': this is out of scope as it could fall under protecting users' health - again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider leaving a dislike and avoiding creators who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc if they don't want to see jumpscares.

==== AI-generated Video ====
* '''Suggestion''': Apply a full-video label to AI-generated videos, or allow skipping or labelling of AI-generated segments.
* '''Reason''': this may be difficult to moderate, is not easy to define, and is arguably not necessary. AI-generated content is sometimes obvious but can be deceptively realistic, so identifying it may be difficult. In addition, there's a potential blurry line between skillful video editing by a competent human, vs low-effort generative AI. SponsorBlock is not intended to make a subjectve statement about whether content is "good"/worth watching: it's up to the user to not watch channels which publish low-quality content, and to leave a dislike and block the channel from their recommendations.

User:AcesFullOfKings/draft

2024-12-14T14:08:51Z

AcesFullOfKings: /* Use of Filler */ fix typo

== Can you add a segment category for X? ==
Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases. New category suggestions may be considered, but must account for the following:

=== Considerations ===

==== Necessity ====
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

==== Commonly-occurring ====
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

==== Well-defined ====
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a partucular segment should be marked.

==== Not protecting a user's mental or physical health ====
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

==== Use of Chapters ====
Consider whether a [[chapter]] could be used instead - labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.

==== Use of Filler ====
Consider whether a [[Filler Tangent/Jokes|filler]] segment could be used instead - filler is for tangential scenes which are added only for filler or humour and are not required to understand the main content of the video. This is a broad and slightly subjective category, but should not be used simply for scenes that you aren't personally interested in. This category could be used in situations where people who have enabled filler may want to skip an irrelevant section of video.

=== Rejected suggestions: ===
Below are examples of frequently suggested categories and the reasons they are not implemented:

==== Epilepsy ====

* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': although this is a nice idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than useless as it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. Again, it's up to creators to be mindful of epileptics in their audience.

==== Fear/Phobia ====

* '''Suggestion''': skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.

* '''Reason''': this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

==== NSFW content / profanity ====
* '''Suggestion''': skip content that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

==== Jumpscares ====
* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds
* '''Reason''': this is out of scope as it could fall under protecting users' health - again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider leaving a dislike and avoiding creators who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc if they don't want to see jumpscares.

==== AI-generated Video ====
* '''Suggestion''': Apply a full-video label to AI-generated videos, or allow skipping or labelling of AI-generated segments.
* '''Reason''': this may be difficult to moderate, is not easy to define, and is arguably not necessary. AI-generated content is sometimes obvious but can be deceptively realistic, so identifying it may be difficult. In addition, there's a potential blurry line between skillful video editing by a competent human, vs low-effort generative AI. SponsorBlock is not intended to make a subjectve statement about whether content is "good"/worth watching: it's up to the user to not watch channels which publish low-quality content, and to leave a dislike and block the channel from their recommendations.

User:AcesFullOfKings/draft

2024-12-14T14:08:02Z

AcesFullOfKings: /* Use of Filler */ fix typo

== Can you add a segment category for X? ==
Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases. New category suggestions may be considered, but must account for the following:

=== Considerations ===

==== Necessity ====
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

==== Commonly-occurring ====
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

==== Well-defined ====
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a partucular segment should be marked.

==== Not protecting a user's mental or physical health ====
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

==== Use of Chapters ====
Consider whether a [[chapter]] could be used instead - labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.

==== Use of Filler ====
Consider whether a [[Filler Tangent/Jokes|filler]] segment could be used instead - filler is for tangential scenes which are added only for filler or humor and are not required to understand the main content of the video. This is a broad and slightly subjective category, but should not be used simply for scenes that you aren't personally interested in. This category could be used in situations where people who have enabled filler may want to skip an irrelevant section of video.

=== Rejected suggestions: ===
Below are examples of frequently suggested categories and the reasons they are not implemented:

==== Epilepsy ====

* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': although this is a nice idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than useless as it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. Again, it's up to creators to be mindful of epileptics in their audience.

==== Fear/Phobia ====

* '''Suggestion''': skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.

* '''Reason''': this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

==== NSFW content / profanity ====
* '''Suggestion''': skip content that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

==== Jumpscares ====
* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds
* '''Reason''': this is out of scope as it could fall under protecting users' health - again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider leaving a dislike and avoiding creators who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc if they don't want to see jumpscares.

==== AI-generated Video ====
* '''Suggestion''': Apply a full-video label to AI-generated videos, or allow skipping or labelling of AI-generated segments.
* '''Reason''': this may be difficult to moderate, is not easy to define, and is arguably not necessary. AI-generated content is sometimes obvious but can be deceptively realistic, so identifying it may be difficult. In addition, there's a potential blurry line between skillful video editing by a competent human, vs low-effort generative AI. SponsorBlock is not intended to make a subjectve statement about whether content is "good"/worth watching: it's up to the user to not watch channels which publish low-quality content, and to leave a dislike and block the channel from their recommendations.

User:AcesFullOfKings/draft

2024-12-14T13:42:05Z

AcesFullOfKings: /* AI-generated Content */ ok fine I won't call it garbage, but it is

== Can you add a segment category for X? ==
Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases. New category suggestions may be considered, but must account for the following:

=== Considerations ===

==== Necessity ====
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

==== Commonly-occurring ====
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

==== Well-defined ====
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a partucular segment should be marked.

==== Not protecting a user's mental or physical health ====
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

==== Use of Chapters ====
Consider whether a [[chapter]] could be used instead - labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.

==== Use of Filler ====
Consider whether a [[Filler Tangent/Jokes|filler]] segment count be used instead - filler is for tangential scenes which are added only for filler or humor and are not required to understand the main content of the video. This is a broad and slightly subjective category, but should not be used simply for scenes that you aren't personally interested in. This category could be used in situations where people who have enabled filler may want to skip an irrelevant section of video.

=== Rejected suggestions: ===
Below are examples of frequently suggested categories and the reasons they are not implemented:

==== Epilepsy ====

* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': although this is a nice idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than useless as it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. Again, it's up to creators to be mindful of epileptics in their audience.

==== Fear/Phobia ====

* '''Suggestion''': skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.

* '''Reason''': this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

==== NSFW content / profanity ====
* '''Suggestion''': skip content that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

==== Jumpscares ====
* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds
* '''Reason''': this is out of scope as it could fall under protecting users' health - again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider leaving a dislike and avoiding creators who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc if they don't want to see jumpscares.

==== AI-generated Video ====
* '''Suggestion''': Apply a full-video label to AI-generated videos, or allow skipping or labelling of AI-generated segments.
* '''Reason''': this may be difficult to moderate, is not easy to define, and is arguably not necessary. AI-generated content is sometimes obvious but can be deceptively realistic, so identifying it may be difficult. In addition, there's a potential blurry line between skillful video editing by a competent human, vs low-effort generative AI. SponsorBlock is not intended to make a subjectve statement about whether content is "good"/worth watching: it's up to the user to not watch channels which publish low-quality content, and to leave a dislike and block the channel from their recommendations.

User:AcesFullOfKings/draft

2024-12-14T13:37:10Z

AcesFullOfKings: /* AI-generated Content */ fixed headings (again)

== Can you add a segment category for X? ==
Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases. New category suggestions may be considered, but must account for the following:

=== Considerations ===

==== Necessity ====
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

==== Commonly-occurring ====
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

==== Well-defined ====
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a partucular segment should be marked.

==== Not protecting a user's mental or physical health ====
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

==== Use of Chapters ====
Consider whether a [[chapter]] could be used instead - labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.

==== Use of Filler ====
Consider whether a [[Filler Tangent/Jokes|filler]] segment count be used instead - filler is for tangential scenes which are added only for filler or humor and are not required to understand the main content of the video. This is a broad and slightly subjective category, but should not be used simply for scenes that you aren't personally interested in. This category could be used in situations where people who have enabled filler may want to skip an irrelevant section of video.

=== Rejected suggestions: ===
Below are examples of frequently suggested categories and the reasons they are not implemented:

==== Epilepsy ====

* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': although this is a nice idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than useless as it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. Again, it's up to creators to be mindful of epileptics in their audience.

==== Fear/Phobia ====

* '''Suggestion''': skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.

* '''Reason''': this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

==== NSFW content / profanity ====
* '''Suggestion''': skip content that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

==== Jumpscares ====
* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds
* '''Reason''': this is out of scope as it could fall under protecting users' health - again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider leaving a dislike and avoiding creators who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc if they don't want to see jumpscares.

==== AI-generated Content ====
* '''Suggestion''': Apply a full-video label to AI-generated videos, or allow skipping or labelling of AI-generated segments.
* '''Reason''': this may be difficult to moderate, is not easy to define, and is arguably not necessary. It's up to the user to not watch channels which publish garbage content, and to leave a dislike and block the channel from their recommendations. AI-generated content is sometimes obvious but can be deceptively realistic, so identifying it may be difficult. In addition, there's a potential blurry line between skillful video editing by a competent human, vs low-effort generative AI. SponsorBlock is not intended to make a subjectve statement about whether content is "good"/worth watching.

User:AcesFullOfKings/draft

2024-12-14T13:34:24Z

AcesFullOfKings: /* Rejected suggestions: */ fixed headings

== Can you add a segment category for X? ==
Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases. New category suggestions may be considered, but must account for the following:

=== Considerations ===

==== Necessity ====
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

==== Commonly-occurring ====
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

==== Well-defined ====
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a partucular segment should be marked.

==== Not protecting a user's mental or physical health ====
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

==== Use of Chapters ====
Consider whether a [[chapter]] could be used instead - labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.

==== Use of Filler ====
Consider whether a [[Filler Tangent/Jokes|filler]] segment count be used instead - filler is for tangential scenes which are added only for filler or humor and are not required to understand the main content of the video. This is a broad and slightly subjective category, but should not be used simply for scenes that you aren't personally interested in. This category could be used in situations where people who have enabled filler may want to skip an irrelevant section of video.

=== Rejected suggestions: ===
Below are examples of frequently suggested categories and the reasons they are not implemented:

==== Epilepsy ====

* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': although this is a nice idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than useless as it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. Again, it's up to creators to be mindful of epileptics in their audience.

==== Fear/Phobia ====

* '''Suggestion''': skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.

* '''Reason''': this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

==== NSFW content / profanity ====
* '''Suggestion''': skip content that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

==== Jumpscares ====
* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds
* '''Reason''': this is out of scope as it could fall under protecting users' health - again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider leaving a dislike and avoiding creators who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc if they don't want to see jumpscares.

=== AI-generated Content ===

* '''Suggestion''': Apply a full-video label to AI-generated videos, or allow skipping or labelling of AI-generated segments.
* '''Reason''': this may be difficult to moderate, is not easy to define, and is arguably not necessary. It's up to the user to not watch channels which publish garbage content, and to leave a dislike and block the channel from their recommendations. AI-generated content is sometimes obvious but can be deceptively realistic, so identifying it may be difficult. In addition, there's a potential blurry line between skillful video editing by a competent human, vs low-effort generative AI. SponsorBlock is not intended to make a subjectve statement about whether content is "good"/worth watching.

User:AcesFullOfKings/draft

2024-12-14T13:32:21Z

AcesFullOfKings: /* Rejected suggestions: */ added AI-generated content

== Can you add a segment category for X? ==
Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases. New category suggestions may be considered, but must account for the following:

=== Considerations ===

==== Necessity ====
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

==== Commonly-occurring ====
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

==== Well-defined ====
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a partucular segment should be marked.

==== Not protecting a user's mental or physical health ====
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

==== Use of Chapters ====
Consider whether a [[chapter]] could be used instead - labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.

==== Use of Filler ====
Consider whether a [[Filler Tangent/Jokes|filler]] segment count be used instead - filler is for tangential scenes which are added only for filler or humor and are not required to understand the main content of the video. This is a broad and slightly subjective category, but should not be used simply for scenes that you aren't personally interested in. This category could be used in situations where people who have enabled filler may want to skip an irrelevant section of video.

=== Rejected suggestions: ===
Below are examples of frequently suggested categories and the reasons they are not implemented:

==== Epilepsy ====

* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': although this is a nice idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than useless as it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. Again, it's up to creators to be mindful of epileptics in their audience.

==== Fear/Phobia ====

* '''Suggestion''': skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.

* '''Reason''': this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

=== NSFW content / profanity ===

* '''Suggestion''': skip content that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

=== Jumpscares ===

* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds
* '''Reason''': this is out of scope as it could fall under protecting users' health - again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider leaving a dislike and avoiding creators who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc if they don't want to see jumpscares.

=== AI-generated Content ===

* '''Suggestion''': Apply a full-video label to AI-generated videos, or allow skipping or labelling of AI-generated segments.
* '''Reason''': this may be difficult to moderate, is not easy to define, and is arguably not necessary. It's up to the user to not watch channels which publish garbage content, and to leave a dislike and block the channel from their recommendations. AI-generated content is sometimes obvious but can be deceptively realistic, so identifying it may be difficult. In addition, there's a potential blurry line between skillful video editing by a competent human, vs low-effort generative AI. SponsorBlock is not intended to make a subjectve statement about whether content is "good"/worth watching.

User:AcesFullOfKings/draft

2024-12-14T13:21:16Z

AcesFullOfKings: Added use of filler, and link to chapter

== Can you add a segment category for X? ==
Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases. New category suggestions may be considered, but must account for the following:

=== Considerations ===

==== Necessity ====
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

==== Commonly-occurring ====
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

==== Well-defined ====
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a partucular segment should be marked.

==== Not protecting a user's mental or physical health ====
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

==== Use of Chapters ====
Consider whether a [[chapter]] could be used instead - labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.

==== Use of Filler ====
Consider whether a [[Filler Tangent/Jokes|filler]] segment count be used instead - filler is for tangential scenes which are added only for filler or humor and are not required to understand the main content of the video. This is a broad and slightly subjective category, but should not be used simply for scenes that you aren't personally interested in. This category could be used in situations where people who have enabled filler may want to skip an irrelevant section of video.

=== Rejected suggestions: ===
Below are examples of frequently suggested categories and the reasons they are not implemented:

==== Epilepsy ====

* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': although this is a nice idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than useless as it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. Again, it's up to creators to be mindful of epileptics in their audience.

==== Fear/Phobia ====

* '''Suggestion''': skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.

* '''Reason''': this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

=== NSFW content / profanity ===

* '''Suggestion''': skip content that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

=== Jumpscares ===

* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds
* '''Reason''': this is out of scope as it could fall under protecting users' health - again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider leaving a dislike and avoiding creators who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc if they don't want to see jumpscares.

User:AcesFullOfKings/draft

2024-12-14T13:11:58Z

AcesFullOfKings: /* Jumpscares */ rephrasing

== Can you add a segment category for X? ==
Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases. New category suggestions may be considered, but must account for the following:

=== Considerations ===

==== Necessity ====
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

==== Commonly-occurring ====
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

==== Well-defined ====
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a partucular segment should be marked.

==== Not protecting a user's mental or physical health ====
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

==== Use of Chapters ====
Consider whether a chapter could be used instead - labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.
=== Rejected suggestions: ===
Below are examples of frequently suggested categories and the reasons they are not implemented:

==== Epilepsy ====

* '''Suggestion''': Mark segments with flashing lights that may trigger epileptic seizures.
* '''Reason''': although this is a nice idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than useless as it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. Again, it's up to creators to be mindful of epileptics in their audience.

==== Fear/Phobia ====

* '''Suggestion''': skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.

* '''Reason''': this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

=== NSFW content / profanity ===

* '''Suggestion''': skip content that may not be suitable for work, such as sexually suggestive material or profanity.
* '''Reason''': This category is subjective and depends heavily on individual preferences. It is ultimately up to users to avoid potentially inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

=== Jumpscares ===

* '''Suggestion''': Skip/mute jumpscares or sudden loud sounds
* '''Reason''': this is out of scope as it could fall under protecting users' health - again, SponsorBlock should not be relied upon to save a user from jumpscares as many would remain unmarked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider leaving a dislike and avoiding creators who use unpleasant jumpscares. Again, it's up to the user to not watch videos of horror games or movies etc if they don't want to see jumpscares.

User:AcesFullOfKings/draft

2024-12-14T13:01:40Z

AcesFullOfKings: /* Epilepsy */ Added Jumpscare

== Can you add a segment category for X? ==
Although new categories do get added occasionally, going forwards further new categories are unlikely to be added because the current categories cover all common cases. New category suggestions may be considered, but must account for the following:

=== Considerations ===

==== Necessity ====
Does your suggested category address a widespread need? It’s not enough for just a few users to want it - there should be substantial demand. For a category to be useful, enough people must be willing to create segments for it across a broad range of videos.

==== Commonly-occurring ====
The segment type should appear frequently in a significant number of videos. One-off or extremely rare occurrences are unlikely to justify a new category.

==== Well-defined ====
Categories must have a strict and objective definition. The boundaries of the category should be clear, specifying what the category does and does not include. Consider edge cases and whether disagreements could arise about whether a partucular segment should be marked.

==== Not protecting a user's mental or physical health ====
SponsorBlock is not intended to protect users' health. Categories aimed at skipping content which may cause distress or discomfort will be rejected as out of scope. The reason is that SponsorBlock relies on user-submitted segments, which may be incomplete or inaccurate, so should not be relied upon for health or wellbeing.

A user who believes that SponsorBlock will protect their health may watch videos which are not (correctly) marked, so will inevitably be exposed to triggering content. It is ultimately the responsibility of content creators to consider their audience’s health and wellbeing needs, and the responsibility of viewers to not expose themselves to potentially triggering content.

==== Use of Chapters ====
Consider whether a chapter could be used instead - labelling a rare or overly-specific segment with a concise chapter name is preferred as it allows users to decide whether to skip it without the need for a new category.
=== Rejected suggestions: ===
Below are examples of frequently suggested categories and the reasons they are not implemented:

==== Epilepsy ====

* Suggestion: Mark segments with flashing lights that may trigger epileptic seizures.
* Reason: although this is a nice idea, as above this comes under protecting a user's health so is rejected as out of scope. As this could never be relied upon, it would be worse than useless as it may create a false sense of security for an epileptic who believes they can safely watch videos and would then be exposed to unmarked flashing lights. Again, it's up to creators to be mindful of epileptics in their audience.

==== Fear/Phobia ====

* Suggestion: skip content which some viewers may find uncomfortable, such as spiders for viewers with arachnophobia.

* Reason: this category is too subjective and broad to be practical, as each user will have different fears and phobias. Attempting to categorise specific fears, such as arachnophobia, would result in far too many categories to be useful. If a user has arachnophobia then they should avoid videos which may contain spiders. It's up to the creator to be mindful of their audience's viewing preferences.
* This also comes under protecting a user's mental wellbeing, which as above is out of scope due to the inherently incomplete/inaccurate database

=== NSFW content / profanity ===

* Suggestion: skip content which you may not want to watch at work, e.g. sexually suggestive or profane content etc.
* Reason: again, this is subjective, and really it's up to users to not watch potentially-inappropriate content in a professional environment. And, as above, we wouldn't want anyone to rely on this category and then encounter unmarked NSFW content.

=== Jumpscares ===

* Suggestion: Skip/mute jumpscares or sudden loud sounds
* Reason: this could fall under protecting a user's health - again, SB should not be relied upon to save a user from jumpscares as many will not be marked. It's also not really that common because creators who include jumpscares generally get a lot of negative feedback. Consider leaving a thumbs-down and not watching further videos from a creator who jumpscares you.

User:AcesFullOfKings/draft

2024-12-14T12:54:07Z

AcesFullOfKings: add profanity to NSFW

User:AcesFullOfKings/draft

2024-12-14T12:53:23Z

AcesFullOfKings: Add NSFW example

User:AcesFullOfKings/draft

2024-12-14T12:45:02Z

AcesFullOfKings: /* Can you add a segment category for X? */

User:AcesFullOfKings/draft

2024-12-14T12:44:25Z

AcesFullOfKings: /* Use of Chapters */ phrasing

User:AcesFullOfKings/draft

2024-12-14T12:43:28Z

AcesFullOfKings: Added section for Use of Chapters

User:AcesFullOfKings/draft

2024-12-14T12:38:20Z

AcesFullOfKings: /* Can you add a segment category for X? */

User:AcesFullOfKings/draft

2024-12-14T12:37:36Z

AcesFullOfKings: grammar

User:AcesFullOfKings/draft

2024-12-14T12:37:14Z

AcesFullOfKings: /* Epilepsy */ grammar/layout

User:AcesFullOfKings/draft

2024-12-14T12:33:53Z

AcesFullOfKings: FAQ: new categories // first draft

API Docs

2024-09-18T17:57:00Z

AcesFullOfKings: revert last incorrect edit

{{API Docs}}

If you are looking for DeArrow API Docs, see [[API Docs/DeArrow|its page]].

'''Libraries''': [https://www.npmjs.com/package/sponsorblock-api Node.js], [https://github.com/wasi-master/sponsorblock.py Python], [https://crates.io/crates/sponsor-block Rust], [https://github.com/porjo/sponsorblockgo Go]

<sub>[https://github.com/ajayyy/SponsorBlock/wiki/Webhooks Webhook Docs] | [https://github.com/mchangrh/sb-openapi OpenAPI Docs]</sub>
-----
====='''GET''' <code>/api/skipSegments</code>=====
Get segments for a video.

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
videoID: string,

category: string, // Optional, defaults to "sponsor", can be repeated for multiple categories. [1]
// OR
categories: string[], // Optional [1]

requiredSegment: string, // Segment UUID to require to be retrieved, even if they don't meet the minimum vote threshold. Can be repeated for multiple segments.
// OR
requiredSegments: string[], // Optional, array of required segment UUIDs

actionType: string // Optional, default skip. Can be repeated for multiple types. [3]
// OR
actionTypes: string[] // Optional, array of action types

service: string, // Optional, default is 'YouTube' [2]
}
</syntaxhighlight>

References: <ref name=":0">See [[Types#Category|Types]] for full list of possible categories. To get multiple, create an array with the format <code>["sponsor", intro"]</code>. </ref> <ref name=":1">Service to get segments for. See [[Types#Service|Types]] for supported services</ref> <ref name=":2">Action Types: See [[Types#Action Type|Types]] for possible values. Select multiple with the format <code>["skip","mute]</code></ref>

'''Response''':
<syntaxhighlight lang="ts">
[{ // Array of this object
segment: float[], //[0, 15.23] start and end time in seconds
UUID: string,
category: string, // [1]
videoDuration: float // Duration of video when submission occurred (to be used to determine when a submission is out of date). 0 when unknown. +- 1 second
actionType: string, // [3]
locked: int, // if submission is locked
votes: int, // Votes on segment
description: string, // title for chapters, empty string for other segments
}]
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

404: Not Found
-----

====='''GET''' <code>/api/skipSegments/:sha256HashPrefix</code>=====
Get segments for a video with extra privacy

<code>sha256HashPrefix</code> is a hash of the YouTube <code>videoID</code>. It should be the first 4 - 32 characters (4 is recommended). This provides extra privacy by potentially finding more than just the video you are looking for since the server will not know exactly what video you are looking for.

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
prefix: string, // Can be used instead of path

category: string, // Optional, defaults to "sponsor", can be repeated for multiple categories. [1]
// OR
categories: string[], // Optional, array of categories [1]

requiredSegment: string, // Segment UUID to require to be retrieved, even if they don't meet the minimum vote threshold. Can be repeated for multiple segments.
// OR
requiredSegments: string[], // Optional, array of required segment UUIDs

actionType: string // Optional, default skip. Can be repeated for multiple types. [3]
// OR
actionTypes: string[] // Optional, array of action types [3]

service: string // Optional, default is 'YouTube'. [2]
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":1" /> <ref name=":2" />

'''Response'''
<syntaxhighlight lang="ts">
[{ // Array of this object
videoID: string,
segments: [{ // Array of this object
segment: float[], // [0, 15.23] start and end time in seconds
UUID: string,
category: string, [1]
actionType: string, // [1]
locked: int, // if segment is locked
votes: int, // votes on segment
videoDuration: int, // Duration of video when submissions occurred
description: string // title for chapters, empty string for other segments
}]
}]
</syntaxhighlight>
'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

404: Not Found
-----

====='''POST''' <code>/api/skipSegments</code>=====
Create a segment on a video

'''If you're looking to automate submissions: please see the [[Automating Submissions]] page.'''

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
videoID: string,
startTime: float,
endTime: float,
category: string, // [1]
userID: string, // This should be a randomly generated 30 char string stored locally (not the public one)
userAgent: string, // "Name of Client/Version" or "[BOT] Name of Bot/Version" ex. "Chromium/1.0.0"
service: string, // Optional, default is 'YouTube'. [2]
videoDuration: float, // Optional, duration of video, will attempt to retrieve from the YouTube API if missing (to be used to determine when a submission is out of date)
actionType: string // Optional, default is "skip". [3]
description: string // Chapter title for chapters, must be an empty string or not present for other segment types
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":1" /> <ref name=":2" />

'''OR'''

'''Input''' (JSON Body):
<syntaxhighlight lang="ts">
{
videoID: string,
userID: string, // This should be a randomly generated 30 character string stored locally (not the public one)
userAgent: string, // "Name of Client/Version" or "[BOT] Name of Bot/Version" ex. "Chromium/1.0.0"
service: string, // Optional, default is 'YouTube'.[2]
videoDuration: float, // Optional, duration of video, will attempt to retrieve from the YouTube API if missing (to be used to determine when a submission is out of date)

segments: [{ // Array of this object
segment: float[], // [0, 15.23] start and end time in seconds
category: string, // [1]
actionType: string // Optional, defaults to "skip". [3]
description: string // Chapter title for chapters, must be an empty string or not present for other segment types
}]
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":1" /> <ref name=":2" />

'''Response''':
<syntaxhighlight lang="ts">
{ // array of this object
UUID: string, // UUID of submitted segment
category: string, // submitted category [1]
segment: float[] // start and end time of submitted segment
}[]
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Rejected by auto moderator (Reason will be sent in the response)

429: Rate Limit (Too many for the same user or IP)

409: Duplicate
-----

====='''POST''' <code>/api/voteOnSponsorTime</code>=====
Vote on a segment or vote to change the category of the segment.

Creators of the segment and VIPs can remove the segment or change the category with only one vote.

<div class="toccolours mw-collapsible mw-collapsed" style="width:400px;">
<div style="font-weight:bold;">VIP voting notes</div>
<div class="mw-collapsible-content">
VIP upvotes will:
* lock the segment
* remove "hidden" property
* remove "shadowHidden" property
</div></div>

'''Input: Normal Vote''' (URL Parameters):
<syntaxhighlight lang="ts">
{
UUID: string, // UUID of the segment being voted on
userID: string, // Local userID
type: int // 0 for downvote, 1 for upvote, 20 to undo vote
}
</syntaxhighlight>

'''OR'''

'''Input: Category Vote''' (URL Parameters):
<syntaxhighlight lang="ts">
{
UUID: string, // UUID of the segment being voted on
userID: string, // Local userID
category: string // Category to change this submission to [1]
} </syntaxhighlight>

References: <ref name=":0" />

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Reason given in request (moderation)
-----

====='''POST''' <code>/api/viewedVideoSponsorTime</code>=====
Add view to segment

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
UUID: string // UUID of segment viewed
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)
-----
====='''GET''' <code>/api/userInfo</code>=====
Get information about a user

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string // local UserID
// OR
publicUserID: string // Public userID

values: string[] // Optional, Values to get from userInfo
// default values are
// ["userID", "userName", "minutesSaved", "segmentCount", "ignoredSegmentCount",
// "viewCount", "ignoredViewCount", "warnings", "warningReason", "reputation",
// "vip", "lastSegmentID"]
// OR
value: string // Optional, Value to get from userInfo, can be repeated for multiple values
}
</syntaxhighlight>
'''Response''':
<syntaxhighlight lang="ts">
{
userID: string, // Public userID
userName: string, // Public userID if not set
minutesSaved: float, // Minutes saved
segmentCount: int, // Total number of segments excluding ignored/ hidden segments
ignoredSegmentCount: int, // Total number of ignored/ hidden segments
viewCount: int, // Total number of views excluding view on ignored/ hidden segments
ignoredViewCount: int, // Total number of view on ignored/ hidden segments
warnings: int, // Currently enabled warnings
reputation: float,
vip: int, // VIP status
lastSegmentID: string, // UUID of last submitted segment
permissions: { // Can the user submit segments of this category?
category: boolean // [1]
}
}
</syntaxhighlight>

References: <ref name=":0" />

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

-----

====='''GET''' <code>/api/userStats</code>=====

Get stats for a user

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string // local UserID
// OR
publicUserID: string // Public userID

fetchCategoryStats: boolean // default false, display category stats
fetchActionTypeStats: boolean // default false, display type stats
}
</syntaxhighlight>
'''Response''':
<syntaxhighlight lang="ts">
{
userID: string // hashed userID
userName: string // userName
overallStats: {
minutesSaved: integer // same as userInfo
segmentCount: integer // same as userInfo
}
// IF CHOSEN
categoryCount: { // # of segments per category
sponsor: integer
intro: integer
outro: integer
interaction: integer
selfpromo: integer
music_offtopic: integer
preview: integer
poi_highlight: integer
filler: integer,
exclusive_access: integer,
chapter: integer
}
// IF CHOSEN
actionTypeCount: { // # of segments per type
skip: integer,
mute: integer,
full: integer,
poi: integer,
chapter: integer
}
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)
-----

====='''GET''' <code>/api/getViewsForUser</code>=====
Get the number of views a user has on all their segments

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string // local UserID
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="js">
{
viewCount: int
}
</syntaxhighlight>

'''Error codes''':

404: Not Found
-----
====='''GET''' <code>/api/getSavedTimeForUser</code>=====
Get the total time saved from all the user's segments

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string // Local userID
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
timeSaved: float // In minutes
}
</syntaxhighlight>

'''Error codes''':

404: Not Found
-----
====='''POST''' <code>/api/setUsername</code>=====
Set a username for a userID

'''Input''' (URL Parameters): Setting username for self
<syntaxhighlight lang="ts">
{
userID: string, // Local userID
username: string, // Optional
}
</syntaxhighlight>

'''OR'''

'''Input''' (URL Parameters): Setting username as '''admin'''<syntaxhighlight lang="ts">
{
userID: string, // Public userID
username: string, // Optional
adminUserID: string // Admin's local userID
}
</syntaxhighlight>'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not an admin)
-----
====='''GET''' <code>/api/getUsername</code>=====
Get current username

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string // Local userID
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
userName: string // Public userID if no username has been set
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)
-----
====='''GET''' <code>/api/segmentInfo</code>=====
Get information about segments

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
// Only the first 10 entries will be processed
UUID: string, // Can be repeated for multiple segments
// OR
UUIDs: string[] // Looks like ["a...0", "b...1"]
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
[{ // Array of this object
videoID: string,
startTime: float,
endTime: float,
votes: int,
locked: int, // Status of lock - If upvoted by a VIP, the segment is locked
UUID: string,
userID: string, // PublicID of submitter
timeSubmitted: int,
views: int, // Number of reported views on the segment
category: string, // [1]
service: string, // [2]
actionType: string, // [3]
videoDuration: int,
hidden: int, // If the segment has 2 downvotes or was downvoted by a VIP
reputation: int, // Reputation of submitter at time of submission
shadowHidden: int, // If the submitter is shadowbanned
hashedVideoID: string, // sha256 hash of the videoID
userAgent: string, // userAgent of the submitter,
description: string // title for chapters, empty string for other segments
}]
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":1" /> <ref name=":2" />

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

404: Not Found
-----

====='''GET''' <code>/api/userID</code>=====
List all users matching the username search

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
username: string, // search string for username
// case sensitive
// minimum for non-exact search is 3 characters, maximum is 64 characters
exact: boolean // searches for exact username with no wildcard at end
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
[{ // Array of this object - maximum 10 results
userName: string,
userID: string
}]
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible) or exceed the character limits

404: Not Found
-----
====='''GET''' <code>/api/lockCategories</code>=====
Get locked categories for a video

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
videoID: string,
actionTypes: string[] // [3]
// default [skip, mute]
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
categories: string[], // [1]
reason: string, // Specified reason for the lock
// Only the most recent reason will be returned
actionTypes: string[] // [3]
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":2" />

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

404: Not Found
-----
====='''GET''' <code>/api/lockCategories/:sha256HashPrefix</code>=====
Get locked categories for a video with extra privacy

<code>sha256HashPrefix</code> is a hash of the YouTube <code>videoID</code>. It should be the first 4 - 32 characters (4 is recommended). This provides extra privacy by potentially finding more than just the video you are looking for. This makes the server not know exactly what video you are looking for.

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
prefix: sha256HashPrefix // Optional if not sent through path
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
[{ // Array of this object
videoID: string,
hash: string, // The full hash of the videoID
categories": string[], // [1]
reason: string // Specified reason for the lock
}]
</syntaxhighlight>

References: <ref name=":0" />

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

404: Not Found
-----
====='''GET''' <code>/api/lockReason</code>=====
Get reason for lock(s)

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
videoID: string

// Categories to get reasons for, defaults to all [1]
category: string
// OR
categories: string[],
actionTypes: string[] // [3]
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":2" />

'''Response''':
<syntaxhighlight lang="ts">
[{ // Array of this object
category: string, // category [1]
locked: integer, // status of lock
reason: string, // reason for lock
userID: string, // publicID of locking VIP
userName: string // username of locking VIP
}]
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)
-----
====='''GET''' <code>/api/searchSegments</code>=====
Get all segments of a video based on specified filters. Note: It is suggested that you don't use this for knowing which segments to skip on your client, as thresholds and values that determine which segments are the best change over time. Using [https://wiki.sponsor.ajay.app/index.php/API_Docs#GET_.2Fapi.2FskipSegments /api/skipSegments] ensures that you will always get the best segments.

'''Input''' (URL Parameters) '''OR''' (JSON Body):
<syntaxhighlight lang="ts">
{
// See skipSegments
videoID: string

category: string // [1]
// OR
categories: string[]

actionType: string // [3]
// OR
actionTypes: string[]

service: string // [2]
// End SkipSegments

page: int // Page to start from (default 0)

// Vote/ view thresholds, inclusive, default includes all segments
minVotes: int
maxVotes: int

minViews: int
maxViews: int

// Default true - if false, don't show segments that match type
locked: boolean
hidden: boolean
ignored: boolean // hidden or below vote threshold
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":1" /> <ref name=":2" />

'''Response''':
<syntaxhighlight lang="ts">
{
segmentCount: int, // Total number of segments matching query
page: int, // Page number
segments: [{ // Array of this object, max 10
// see segmentInfo
UUID: string,
timeSubmitted: int,
startTime: int,
endTime: int,
category: string, // [1]
actionType: string, // [3]
votes: int,
views: int,
locked: int,
hidden: int,
shadowHidden: int,
userID: string, // UUID of submitter
description: string // title for chapters, empty string for other segments
}]
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":2" />

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

404: Not Found

-----

====='''GET''' <code>/api/status/:value</code>=====
Get status of server

'''Input:''' (URL path)

Can be any key value in response, requests without path will return all values.

'''Response''':
<syntaxhighlight lang="ts">
{
uptime: int, // Uptime of server in seconds
commit: string, // Full SHA hash of latest git commit, development or test
db: int, // Current database version
startTime: int, // Unix time (miliseconds) that request was received
processTime: int, // Delay between DB request made and response received (miliseconds)
redisProcessTime: int, // Delay between redis request made and response received (miliseconds)
loadavg: int[], // 5 and 15 minute loadavg
statusRequests: int, // number of /status requests in the last minute
hostname: string // hostname of current server
}
</syntaxhighlight>

'''Error codes''':

404: Not Found
-----

===Stats Calls===
====='''GET''' <code>/api/getTopUsers</code>=====
'''This endpoint is currently disabled and will always return 404.'''

Get top submitters

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
sortType: int
// 0 for by minutes saved
// 1 for by view count
// 2 for by total submissions
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
userNames: string[],
viewCounts: int[],
totalSubmissions: int[],
minutesSaved: float[]
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)
-----'''GET''' <code>/api/getTopCategoryUsers</code>
'''This endpoint is currently disabled and will always return 404.'''

Get top submitters by category

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
sortType: int,
// 0 for by minutes saved
// 1 for by view count
// 2 for by total submissions
category: string // category to fetch stats for
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
userNames: string[],
viewCounts: int[],
totalSubmissions: int[],
minutesSaved: float[]
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)
-----

====='''GET''' <code>/api/getTotalStats</code>=====
Get total stats

'''Input''' (URL Parameters):

<syntaxhighlight lang="ts">
{
countContributingUsers: boolean // Optional, default false
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
userCount: int, // Only if countContributingUsers was true
activeUsers: int, // Sum of public install stats from Chrome webstore and Firefox addons store
apiUsers: int, // 48-hour active API users (https://github.com/ajayyy/PrivacyUserCount)
viewCount: int,
totalSubmissions: int,
minutesSaved: float
}
</syntaxhighlight>

'''Error codes''':

None
-----
====='''GET''' <code>/api/getDaysSavedFormatted</code>=====
Get days saved by all skips

'''Input''':
<syntaxhighlight lang="ts">
{
Nothing
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
daysSaved: float (2 decimal places)
}
</syntaxhighlight>

'''Error codes''':

None
-----
===VIP Calls===
These can only be called by the users added to the VIP table.
====='''GET''' <code>/api/isUserVIP</code>=====
If the user is a VIP

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string, // Local userID
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
hashedUserID: string, // Public userID
vip: boolean
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)
-----
====='''POST''' <code>/api/lockCategories</code>=====
Create a category lock on the video, disallowing further submissions for that category

'''Input''' (Request Body):
<syntaxhighlight lang="ts">
{
videoID: string,
userID: string, // Local userID
categories: string[], // [1]
actionTypes: string[], // [3]
reason: string, // Reason for lock
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":2" />

'''Response''':
<syntaxhighlight lang="ts">
{
submitted: string[], // categories [1]
submittedValues: {
actionType: string, // [3]
category: string // [1]
} // array of this object
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":2" />

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)
-----

===== '''DELETE''' <code>/api/lockCategories</code>=====
Delete existing category locks on that video

'''Input''' (Request Body):
<syntaxhighlight lang="ts">
{
videoID: string,
userID: string, // Local userID
categories: string[] // [1]
}
</syntaxhighlight>

References: <ref name=":0" />

'''Response''':
<syntaxhighlight lang="ts">
{
message: "Removed lock categories entries for video videoID"
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)
-----
====='''POST''' <code>/api/shadowBanUser</code>=====
Shadow banned submissions are hidden for everyone but the IP that originally submitted it. Shadow banning a user shadow bans all future submissions.

User can be re-shadowbanned if segments were not previously hidden

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string, // Public userID of the user you want to shadowBan
adminUserID: string, // Local userID of VIP or Admin
enabled: boolean, // Optional, default true, true to ban and false to unban
unHideOldSubmissions: boolean, // Optional, depends on the enabled parameter, should all previous submissions be (un)hidden as well?
categories: string // Optional, defaults to all categories, in the format "["sponsor", "selfpromo"]" etc...
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)

409: Duplicate (User already shadowbanned & unHideOldSubmissions not changed)
-----
===== '''POST''' <code>/api/warnUser</code>=====
Temporary ban that shows a warning asking them to contact us.

If a user is re-warned but there is still a non-expired warning, it is reenabled

'''Input''' (Request Body):
<syntaxhighlight lang="ts"> {
issuerUserID: string, // Issuer userID (Local userID)
userID: string, // Public userID you are warning
reason: string, // Optional
enabled: boolean // Optional, default true
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)

409: User already warned
-----

====='''POST''' <code>/api/clearCache</code>=====
Clear redis cache for video.

'''Input''' (Request Body):
<syntaxhighlight lang="ts">
{
userID: string, // Local userID
videoID: string
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Cache cleared on video videoID (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)
-----
====='''POST''' <code>/api/purgeAllSegments</code>=====
Hide all segments on a video without affecting submitters' reputation

'''Input''' (Request Body):
<syntaxhighlight lang="ts">
{
userID: string, // Local userID
videoID: string,
service: string // Service of video, defaults to YouTube
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)
-----
====='''POST''' <code>/api/segmentShift</code>=====
Shift all segments on a video

'''Input''' (Request Body):
<syntaxhighlight lang="ts">
{
videoID: string,
userID: string, // Local userID
startTime: float,
endTime: float
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)
-----
====='''POST''' <code>/api/addUserAsTempVIP</code>=====
Add temporary 24 Hour Channel VIP

A user cannot be a VIP of multiple channels, the most recent channel will take precedence and override

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string, // User to grant temp VIP to
adminUserID: string, // Local userID of existing VIP
channelVideoID: string, // videoID of channel to grant VIP on
enabled: string // default "true" Enable or disable VIP status
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Temp VIP added on channel channelName (status code 200)
Temp VIP removed (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)

404: Not Found (No channel found for videoID)

409: Duplicate (User is already a permanent VIP)
-----

====='''POST''' <code>/api/feature</code>=====
Add or remove user features

'''Input''' (Request Body):
<syntaxhighlight lang="ts">
{
userID: string, // User to add or remove features from
adminUserID: string, // Local userID of existing VIP
feature: int, // [4]
enabled: boolean // default "true" Enable or disable feature
}
</syntaxhighlight>

References: <ref name=":4">See [[Types#User_Features|Types]] for a full list of possible user features.</ref>

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible or the feature does not exist)

403: Unauthorized (You are not a VIP)
-----
===Admin Calls===
These can only be called by the server administrator, set in the config.
====='''POST''' <code>/api/addUserAsVIP</code>=====
VIPs have extra privileges and their votes count more.

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string, // Public userID of the user you want to add to the VIP list
adminUserID: string, // Admin's local userID
enabled: boolean // Optional, to be able to add and remove users (default: false)
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not an admin)
-----

===Legacy API===
https://github.com/ajayyy/SponsorBlock/wiki/Legacy-API
===Local userID vs Public userID===
The local userID should be a randomly generated and saved client side and must be 32 characters (or more). If it is not 32 characters or more, you will not be able to vote or submit. The public userID is what is used as an identifier in the database. This is the local userID with a SHA 256 hash 5000 times.

=== References ===
<references />
__INDEX__
__NEWSECTIONLINK__
[[Category:Developer Reference]]
[[Category:SponsorBlock]]

API Docs

2024-09-18T17:55:12Z

AcesFullOfKings: /* GET /api/getViewsForUser */

{{API Docs}}

If you are looking for DeArrow API Docs, see [[API Docs/DeArrow|its page]].

'''Libraries''': [https://www.npmjs.com/package/sponsorblock-api Node.js], [https://github.com/wasi-master/sponsorblock.py Python], [https://crates.io/crates/sponsor-block Rust], [https://github.com/porjo/sponsorblockgo Go]

<sub>[https://github.com/ajayyy/SponsorBlock/wiki/Webhooks Webhook Docs] | [https://github.com/mchangrh/sb-openapi OpenAPI Docs]</sub>
-----
====='''GET''' <code>/api/skipSegments</code>=====
Get segments for a video.

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
videoID: string,

category: string, // Optional, defaults to "sponsor", can be repeated for multiple categories. [1]
// OR
categories: string[], // Optional [1]

requiredSegment: string, // Segment UUID to require to be retrieved, even if they don't meet the minimum vote threshold. Can be repeated for multiple segments.
// OR
requiredSegments: string[], // Optional, array of required segment UUIDs

actionType: string // Optional, default skip. Can be repeated for multiple types. [3]
// OR
actionTypes: string[] // Optional, array of action types

service: string, // Optional, default is 'YouTube' [2]
}
</syntaxhighlight>

References: <ref name=":0">See [[Types#Category|Types]] for full list of possible categories. To get multiple, create an array with the format <code>["sponsor", intro"]</code>. </ref> <ref name=":1">Service to get segments for. See [[Types#Service|Types]] for supported services</ref> <ref name=":2">Action Types: See [[Types#Action Type|Types]] for possible values. Select multiple with the format <code>["skip","mute]</code></ref>

'''Response''':
<syntaxhighlight lang="ts">
[{ // Array of this object
segment: float[], //[0, 15.23] start and end time in seconds
UUID: string,
category: string, // [1]
videoDuration: float // Duration of video when submission occurred (to be used to determine when a submission is out of date). 0 when unknown. +- 1 second
actionType: string, // [3]
locked: int, // if submission is locked
votes: int, // Votes on segment
description: string, // title for chapters, empty string for other segments
}]
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

404: Not Found
-----

====='''GET''' <code>/api/skipSegments/:sha256HashPrefix</code>=====
Get segments for a video with extra privacy

<code>sha256HashPrefix</code> is a hash of the YouTube <code>videoID</code>. It should be the first 4 - 32 characters (4 is recommended). This provides extra privacy by potentially finding more than just the video you are looking for since the server will not know exactly what video you are looking for.

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
prefix: string, // Can be used instead of path

category: string, // Optional, defaults to "sponsor", can be repeated for multiple categories. [1]
// OR
categories: string[], // Optional, array of categories [1]

requiredSegment: string, // Segment UUID to require to be retrieved, even if they don't meet the minimum vote threshold. Can be repeated for multiple segments.
// OR
requiredSegments: string[], // Optional, array of required segment UUIDs

actionType: string // Optional, default skip. Can be repeated for multiple types. [3]
// OR
actionTypes: string[] // Optional, array of action types [3]

service: string // Optional, default is 'YouTube'. [2]
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":1" /> <ref name=":2" />

'''Response'''
<syntaxhighlight lang="ts">
[{ // Array of this object
videoID: string,
segments: [{ // Array of this object
segment: float[], // [0, 15.23] start and end time in seconds
UUID: string,
category: string, [1]
actionType: string, // [1]
locked: int, // if segment is locked
votes: int, // votes on segment
videoDuration: int, // Duration of video when submissions occurred
description: string // title for chapters, empty string for other segments
}]
}]
</syntaxhighlight>
'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

404: Not Found
-----

====='''POST''' <code>/api/skipSegments</code>=====
Create a segment on a video

'''If you're looking to automate submissions: please see the [[Automating Submissions]] page.'''

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
videoID: string,
startTime: float,
endTime: float,
category: string, // [1]
userID: string, // This should be a randomly generated 30 char string stored locally (not the public one)
userAgent: string, // "Name of Client/Version" or "[BOT] Name of Bot/Version" ex. "Chromium/1.0.0"
service: string, // Optional, default is 'YouTube'. [2]
videoDuration: float, // Optional, duration of video, will attempt to retrieve from the YouTube API if missing (to be used to determine when a submission is out of date)
actionType: string // Optional, default is "skip". [3]
description: string // Chapter title for chapters, must be an empty string or not present for other segment types
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":1" /> <ref name=":2" />

'''OR'''

'''Input''' (JSON Body):
<syntaxhighlight lang="ts">
{
videoID: string,
userID: string, // This should be a randomly generated 30 character string stored locally (not the public one)
userAgent: string, // "Name of Client/Version" or "[BOT] Name of Bot/Version" ex. "Chromium/1.0.0"
service: string, // Optional, default is 'YouTube'.[2]
videoDuration: float, // Optional, duration of video, will attempt to retrieve from the YouTube API if missing (to be used to determine when a submission is out of date)

segments: [{ // Array of this object
segment: float[], // [0, 15.23] start and end time in seconds
category: string, // [1]
actionType: string // Optional, defaults to "skip". [3]
description: string // Chapter title for chapters, must be an empty string or not present for other segment types
}]
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":1" /> <ref name=":2" />

'''Response''':
<syntaxhighlight lang="ts">
{ // array of this object
UUID: string, // UUID of submitted segment
category: string, // submitted category [1]
segment: float[] // start and end time of submitted segment
}[]
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Rejected by auto moderator (Reason will be sent in the response)

429: Rate Limit (Too many for the same user or IP)

409: Duplicate
-----

====='''POST''' <code>/api/voteOnSponsorTime</code>=====
Vote on a segment or vote to change the category of the segment.

Creators of the segment and VIPs can remove the segment or change the category with only one vote.

<div class="toccolours mw-collapsible mw-collapsed" style="width:400px;">
<div style="font-weight:bold;">VIP voting notes</div>
<div class="mw-collapsible-content">
VIP upvotes will:
* lock the segment
* remove "hidden" property
* remove "shadowHidden" property
</div></div>

'''Input: Normal Vote''' (URL Parameters):
<syntaxhighlight lang="ts">
{
UUID: string, // UUID of the segment being voted on
userID: string, // Local userID
type: int // 0 for downvote, 1 for upvote, 20 to undo vote
}
</syntaxhighlight>

'''OR'''

'''Input: Category Vote''' (URL Parameters):
<syntaxhighlight lang="ts">
{
UUID: string, // UUID of the segment being voted on
userID: string, // Local userID
category: string // Category to change this submission to [1]
} </syntaxhighlight>

References: <ref name=":0" />

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Reason given in request (moderation)
-----

====='''POST''' <code>/api/viewedVideoSponsorTime</code>=====
Add view to segment

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
UUID: string // UUID of segment viewed
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)
-----
====='''GET''' <code>/api/userInfo</code>=====
Get information about a user

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string // local UserID
// OR
publicUserID: string // Public userID

values: string[] // Optional, Values to get from userInfo
// default values are
// ["userID", "userName", "minutesSaved", "segmentCount", "ignoredSegmentCount",
// "viewCount", "ignoredViewCount", "warnings", "warningReason", "reputation",
// "vip", "lastSegmentID"]
// OR
value: string // Optional, Value to get from userInfo, can be repeated for multiple values
}
</syntaxhighlight>
'''Response''':
<syntaxhighlight lang="ts">
{
userID: string, // Public userID
userName: string, // Public userID if not set
minutesSaved: float, // Minutes saved
segmentCount: int, // Total number of segments excluding ignored/ hidden segments
ignoredSegmentCount: int, // Total number of ignored/ hidden segments
viewCount: int, // Total number of views excluding view on ignored/ hidden segments
ignoredViewCount: int, // Total number of view on ignored/ hidden segments
warnings: int, // Currently enabled warnings
reputation: float,
vip: int, // VIP status
lastSegmentID: string, // UUID of last submitted segment
permissions: { // Can the user submit segments of this category?
category: boolean // [1]
}
}
</syntaxhighlight>

References: <ref name=":0" />

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

-----

====='''GET''' <code>/api/userStats</code>=====

Get stats for a user

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string // local UserID
// OR
publicUserID: string // Public userID

fetchCategoryStats: boolean // default false, display category stats
fetchActionTypeStats: boolean // default false, display type stats
}
</syntaxhighlight>
'''Response''':
<syntaxhighlight lang="ts">
{
userID: string // hashed userID
userName: string // userName
overallStats: {
minutesSaved: integer // same as userInfo
segmentCount: integer // same as userInfo
}
// IF CHOSEN
categoryCount: { // # of segments per category
sponsor: integer
intro: integer
outro: integer
interaction: integer
selfpromo: integer
music_offtopic: integer
preview: integer
poi_highlight: integer
filler: integer,
exclusive_access: integer,
chapter: integer
}
// IF CHOSEN
actionTypeCount: { // # of segments per type
skip: integer,
mute: integer,
full: integer,
poi: integer,
chapter: integer
}
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)
-----

====='''GET''' <code>/api/getViewsForUser</code>=====
Get the number of views a user has on all their segments

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string // user's Private ID
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="js">
{
viewCount: int
}
</syntaxhighlight>

'''Error codes''':

404: Not Found
-----
====='''GET''' <code>/api/getSavedTimeForUser</code>=====
Get the total time saved from all the user's segments

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string // Local userID
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
timeSaved: float // In minutes
}
</syntaxhighlight>

'''Error codes''':

404: Not Found
-----
====='''POST''' <code>/api/setUsername</code>=====
Set a username for a userID

'''Input''' (URL Parameters): Setting username for self
<syntaxhighlight lang="ts">
{
userID: string, // Local userID
username: string, // Optional
}
</syntaxhighlight>

'''OR'''

'''Input''' (URL Parameters): Setting username as '''admin'''<syntaxhighlight lang="ts">
{
userID: string, // Public userID
username: string, // Optional
adminUserID: string // Admin's local userID
}
</syntaxhighlight>'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not an admin)
-----
====='''GET''' <code>/api/getUsername</code>=====
Get current username

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string // Local userID
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
userName: string // Public userID if no username has been set
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)
-----
====='''GET''' <code>/api/segmentInfo</code>=====
Get information about segments

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
// Only the first 10 entries will be processed
UUID: string, // Can be repeated for multiple segments
// OR
UUIDs: string[] // Looks like ["a...0", "b...1"]
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
[{ // Array of this object
videoID: string,
startTime: float,
endTime: float,
votes: int,
locked: int, // Status of lock - If upvoted by a VIP, the segment is locked
UUID: string,
userID: string, // PublicID of submitter
timeSubmitted: int,
views: int, // Number of reported views on the segment
category: string, // [1]
service: string, // [2]
actionType: string, // [3]
videoDuration: int,
hidden: int, // If the segment has 2 downvotes or was downvoted by a VIP
reputation: int, // Reputation of submitter at time of submission
shadowHidden: int, // If the submitter is shadowbanned
hashedVideoID: string, // sha256 hash of the videoID
userAgent: string, // userAgent of the submitter,
description: string // title for chapters, empty string for other segments
}]
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":1" /> <ref name=":2" />

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

404: Not Found
-----

====='''GET''' <code>/api/userID</code>=====
List all users matching the username search

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
username: string, // search string for username
// case sensitive
// minimum for non-exact search is 3 characters, maximum is 64 characters
exact: boolean // searches for exact username with no wildcard at end
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
[{ // Array of this object - maximum 10 results
userName: string,
userID: string
}]
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible) or exceed the character limits

404: Not Found
-----
====='''GET''' <code>/api/lockCategories</code>=====
Get locked categories for a video

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
videoID: string,
actionTypes: string[] // [3]
// default [skip, mute]
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
categories: string[], // [1]
reason: string, // Specified reason for the lock
// Only the most recent reason will be returned
actionTypes: string[] // [3]
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":2" />

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

404: Not Found
-----
====='''GET''' <code>/api/lockCategories/:sha256HashPrefix</code>=====
Get locked categories for a video with extra privacy

<code>sha256HashPrefix</code> is a hash of the YouTube <code>videoID</code>. It should be the first 4 - 32 characters (4 is recommended). This provides extra privacy by potentially finding more than just the video you are looking for. This makes the server not know exactly what video you are looking for.

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
prefix: sha256HashPrefix // Optional if not sent through path
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
[{ // Array of this object
videoID: string,
hash: string, // The full hash of the videoID
categories": string[], // [1]
reason: string // Specified reason for the lock
}]
</syntaxhighlight>

References: <ref name=":0" />

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

404: Not Found
-----
====='''GET''' <code>/api/lockReason</code>=====
Get reason for lock(s)

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
videoID: string

// Categories to get reasons for, defaults to all [1]
category: string
// OR
categories: string[],
actionTypes: string[] // [3]
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":2" />

'''Response''':
<syntaxhighlight lang="ts">
[{ // Array of this object
category: string, // category [1]
locked: integer, // status of lock
reason: string, // reason for lock
userID: string, // publicID of locking VIP
userName: string // username of locking VIP
}]
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)
-----
====='''GET''' <code>/api/searchSegments</code>=====
Get all segments of a video based on specified filters. Note: It is suggested that you don't use this for knowing which segments to skip on your client, as thresholds and values that determine which segments are the best change over time. Using [https://wiki.sponsor.ajay.app/index.php/API_Docs#GET_.2Fapi.2FskipSegments /api/skipSegments] ensures that you will always get the best segments.

'''Input''' (URL Parameters) '''OR''' (JSON Body):
<syntaxhighlight lang="ts">
{
// See skipSegments
videoID: string

category: string // [1]
// OR
categories: string[]

actionType: string // [3]
// OR
actionTypes: string[]

service: string // [2]
// End SkipSegments

page: int // Page to start from (default 0)

// Vote/ view thresholds, inclusive, default includes all segments
minVotes: int
maxVotes: int

minViews: int
maxViews: int

// Default true - if false, don't show segments that match type
locked: boolean
hidden: boolean
ignored: boolean // hidden or below vote threshold
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":1" /> <ref name=":2" />

'''Response''':
<syntaxhighlight lang="ts">
{
segmentCount: int, // Total number of segments matching query
page: int, // Page number
segments: [{ // Array of this object, max 10
// see segmentInfo
UUID: string,
timeSubmitted: int,
startTime: int,
endTime: int,
category: string, // [1]
actionType: string, // [3]
votes: int,
views: int,
locked: int,
hidden: int,
shadowHidden: int,
userID: string, // UUID of submitter
description: string // title for chapters, empty string for other segments
}]
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":2" />

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

404: Not Found

-----

====='''GET''' <code>/api/status/:value</code>=====
Get status of server

'''Input:''' (URL path)

Can be any key value in response, requests without path will return all values.

'''Response''':
<syntaxhighlight lang="ts">
{
uptime: int, // Uptime of server in seconds
commit: string, // Full SHA hash of latest git commit, development or test
db: int, // Current database version
startTime: int, // Unix time (miliseconds) that request was received
processTime: int, // Delay between DB request made and response received (miliseconds)
redisProcessTime: int, // Delay between redis request made and response received (miliseconds)
loadavg: int[], // 5 and 15 minute loadavg
statusRequests: int, // number of /status requests in the last minute
hostname: string // hostname of current server
}
</syntaxhighlight>

'''Error codes''':

404: Not Found
-----

===Stats Calls===
====='''GET''' <code>/api/getTopUsers</code>=====
'''This endpoint is currently disabled and will always return 404.'''

Get top submitters

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
sortType: int
// 0 for by minutes saved
// 1 for by view count
// 2 for by total submissions
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
userNames: string[],
viewCounts: int[],
totalSubmissions: int[],
minutesSaved: float[]
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)
-----'''GET''' <code>/api/getTopCategoryUsers</code>
'''This endpoint is currently disabled and will always return 404.'''

Get top submitters by category

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
sortType: int,
// 0 for by minutes saved
// 1 for by view count
// 2 for by total submissions
category: string // category to fetch stats for
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
userNames: string[],
viewCounts: int[],
totalSubmissions: int[],
minutesSaved: float[]
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)
-----

====='''GET''' <code>/api/getTotalStats</code>=====
Get total stats

'''Input''' (URL Parameters):

<syntaxhighlight lang="ts">
{
countContributingUsers: boolean // Optional, default false
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
userCount: int, // Only if countContributingUsers was true
activeUsers: int, // Sum of public install stats from Chrome webstore and Firefox addons store
apiUsers: int, // 48-hour active API users (https://github.com/ajayyy/PrivacyUserCount)
viewCount: int,
totalSubmissions: int,
minutesSaved: float
}
</syntaxhighlight>

'''Error codes''':

None
-----
====='''GET''' <code>/api/getDaysSavedFormatted</code>=====
Get days saved by all skips

'''Input''':
<syntaxhighlight lang="ts">
{
Nothing
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
daysSaved: float (2 decimal places)
}
</syntaxhighlight>

'''Error codes''':

None
-----
===VIP Calls===
These can only be called by the users added to the VIP table.
====='''GET''' <code>/api/isUserVIP</code>=====
If the user is a VIP

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string, // Local userID
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
hashedUserID: string, // Public userID
vip: boolean
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)
-----
====='''POST''' <code>/api/lockCategories</code>=====
Create a category lock on the video, disallowing further submissions for that category

'''Input''' (Request Body):
<syntaxhighlight lang="ts">
{
videoID: string,
userID: string, // Local userID
categories: string[], // [1]
actionTypes: string[], // [3]
reason: string, // Reason for lock
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":2" />

'''Response''':
<syntaxhighlight lang="ts">
{
submitted: string[], // categories [1]
submittedValues: {
actionType: string, // [3]
category: string // [1]
} // array of this object
}
</syntaxhighlight>

References: <ref name=":0" /> <ref name=":2" />

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)
-----

===== '''DELETE''' <code>/api/lockCategories</code>=====
Delete existing category locks on that video

'''Input''' (Request Body):
<syntaxhighlight lang="ts">
{
videoID: string,
userID: string, // Local userID
categories: string[] // [1]
}
</syntaxhighlight>

References: <ref name=":0" />

'''Response''':
<syntaxhighlight lang="ts">
{
message: "Removed lock categories entries for video videoID"
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)
-----
====='''POST''' <code>/api/shadowBanUser</code>=====
Shadow banned submissions are hidden for everyone but the IP that originally submitted it. Shadow banning a user shadow bans all future submissions.

User can be re-shadowbanned if segments were not previously hidden

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string, // Public userID of the user you want to shadowBan
adminUserID: string, // Local userID of VIP or Admin
enabled: boolean, // Optional, default true, true to ban and false to unban
unHideOldSubmissions: boolean, // Optional, depends on the enabled parameter, should all previous submissions be (un)hidden as well?
categories: string // Optional, defaults to all categories, in the format "["sponsor", "selfpromo"]" etc...
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)

409: Duplicate (User already shadowbanned & unHideOldSubmissions not changed)
-----
===== '''POST''' <code>/api/warnUser</code>=====
Temporary ban that shows a warning asking them to contact us.

If a user is re-warned but there is still a non-expired warning, it is reenabled

'''Input''' (Request Body):
<syntaxhighlight lang="ts"> {
issuerUserID: string, // Issuer userID (Local userID)
userID: string, // Public userID you are warning
reason: string, // Optional
enabled: boolean // Optional, default true
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)

409: User already warned
-----

====='''POST''' <code>/api/clearCache</code>=====
Clear redis cache for video.

'''Input''' (Request Body):
<syntaxhighlight lang="ts">
{
userID: string, // Local userID
videoID: string
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Cache cleared on video videoID (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)
-----
====='''POST''' <code>/api/purgeAllSegments</code>=====
Hide all segments on a video without affecting submitters' reputation

'''Input''' (Request Body):
<syntaxhighlight lang="ts">
{
userID: string, // Local userID
videoID: string,
service: string // Service of video, defaults to YouTube
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)
-----
====='''POST''' <code>/api/segmentShift</code>=====
Shift all segments on a video

'''Input''' (Request Body):
<syntaxhighlight lang="ts">
{
videoID: string,
userID: string, // Local userID
startTime: float,
endTime: float
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)
-----
====='''POST''' <code>/api/addUserAsTempVIP</code>=====
Add temporary 24 Hour Channel VIP

A user cannot be a VIP of multiple channels, the most recent channel will take precedence and override

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string, // User to grant temp VIP to
adminUserID: string, // Local userID of existing VIP
channelVideoID: string, // videoID of channel to grant VIP on
enabled: string // default "true" Enable or disable VIP status
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Temp VIP added on channel channelName (status code 200)
Temp VIP removed (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not a VIP)

404: Not Found (No channel found for videoID)

409: Duplicate (User is already a permanent VIP)
-----

====='''POST''' <code>/api/feature</code>=====
Add or remove user features

'''Input''' (Request Body):
<syntaxhighlight lang="ts">
{
userID: string, // User to add or remove features from
adminUserID: string, // Local userID of existing VIP
feature: int, // [4]
enabled: boolean // default "true" Enable or disable feature
}
</syntaxhighlight>

References: <ref name=":4">See [[Types#User_Features|Types]] for a full list of possible user features.</ref>

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible or the feature does not exist)

403: Unauthorized (You are not a VIP)
-----
===Admin Calls===
These can only be called by the server administrator, set in the config.
====='''POST''' <code>/api/addUserAsVIP</code>=====
VIPs have extra privileges and their votes count more.

'''Input''' (URL Parameters):
<syntaxhighlight lang="ts">
{
userID: string, // Public userID of the user you want to add to the VIP list
adminUserID: string, // Admin's local userID
enabled: boolean // Optional, to be able to add and remove users (default: false)
}
</syntaxhighlight>

'''Response''':
<syntaxhighlight lang="ts">
{
Nothing (status code 200)
}
</syntaxhighlight>

'''Error codes''':

400: Bad Request (Your inputs are wrong/impossible)

403: Unauthorized (You are not an admin)
-----

===Legacy API===
https://github.com/ajayyy/SponsorBlock/wiki/Legacy-API
===Local userID vs Public userID===
The local userID should be a randomly generated and saved client side and must be 32 characters (or more). If it is not 32 characters or more, you will not be able to vote or submit. The public userID is what is used as an identifier in the database. This is the local userID with a SHA 256 hash 5000 times.

=== References ===
<references />
__INDEX__
__NEWSECTIONLINK__
[[Category:Developer Reference]]
[[Category:SponsorBlock]]

Community

2023-11-15T06:30:11Z

AcesFullOfKings: /* Websites */ Add leaderboard to Websites section

== Media ==
[https://github.com/cole8888/SponsorBlock-Flowchart SponsorBlock Flowchart] by E.Coli. Flowchart to help users choose the correct category when making submissions.

Please see the latest version on the [https://github.com/cole8888/SponsorBlock-Flowchart GitHub]
[[File:SB Flowchart small 1.10.1.png|none|thumb|500x500px|Flow chart to help users choose the correct category when making submissions.]]

== Websites ==
[https://sb.ltn.fi/ SponsorBlock Browser] by Lartza. Explore segments on a 5-minute delayed version of the live database

[https://mruy.github.io/sponsorBlockControl-sveltekit/ SponsorBlockControl-sveltekit] by Nanobyte. Vote on segments with UUID, also for VIP operations

[https://openapi.sb.blabdu.de/ SponsorBlock Swagger] by mchangrh. Explore and try the SponsorBlock API.

[https://leaderboard.sbstats.uk/ SponsorBlock Leaderboard] by AcesFullOfKings. See who the top submitters and time-savers are.

=== Userscripts ===
Userscripts require a userscript manager like [https://www.tampermonkey.net/ Tampermonkey].

==== SponsorBlock Browser ====
{| class="wikitable"
|+Userscripts
!Name
!Description
!Targets
!Author
!Install Link
|-
|sb.ltn.fi.lastupdate.user.js
|Show the last update time
|Global
| rowspan="3" |[https://github.com/MRuy NanoByte]
|[https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.lastupdate.user.js Install]
|-
|sb.ltn.fi.similarsegments.user.js
|Color code similar segments
|Videos
|[https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.similarsegments.user.js Install]
|-
|sb.ltn.fi.sponsorblock.paste.ytlink.user.js
|Paste YT Link into videoID Field
|Navigation
|[https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.sponsorblock.paste.ytlink.user.js Install]
|-
|sb.ltn.fi.clickableellipsisnavigation.user.js
|ellipsis in page navigation will show a prompt for page number
|Navigation
| rowspan="6" |[https://github.com/TheJzoli TheJzoli]
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.clickableellipsisnavigation.user.js Install]
|-
|sb.ltn.fi.copyuserid.user.js
|Adds a button on the userID page to copy that userID
|Users
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.copyuserid.user.js Install]
|-
|sb.ltn.fi.copyvideopagelink.user.js
|copy video ID" (✂) button copies SBB page link instead
|Segment Options
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.copyvideopagelink.user.js Install]
|-
|sb.ltn.fi.forceupdate.user.js
|Fetches the segments and updated info for the video, so that you don't have to wait for the video page to update.
|Videos
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.forceupdate.user.js Install]
|-
|sb.ltn.fi.hidecolumns.user.js
|Hide any column you want
|Column/ Table
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.hidecolumns.user.js Install]
|-
|sb.ltn.fi.pagenavigationabovetable.user.js
|Duplicate page navigation element above table
|Navigation
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.pagenavigationabovetable.user.js Install]
|-
|sbltnfi-time-saved-column.user.js
|Adds time saved column
|Videos
|[https://github.com/NoMoreAngel NoMoreAngel]
|[https://github.com/NoMoreAngel/userscripts/raw/main/sbltnfi/sbltnfi-time-saved-column.user.js Install]
|-
|sbltnfi-imprecise-times.user.js
|Removes trailing insignificant zeroes from Start, End and Length
|Videos
| rowspan="4" |[https://github.com/mchangrh blabdude]
|[https://uscript.mchang.xyz/sbltnfi/sbltnfi-imprecise-times.user.js Install]
|-
|sbltnfi-refresh.user.js
|Refresh individual segments
|Videos
|[https://uscript.mchang.xyz/sbltnfi/sbltnfi-refresh.user.js Install]
|-
|sbltnfi-requiredSegments.user.js
|Copy sb.mchang.xyz/UUID link
|Videos
|[https://uscript.mchang.xyz/sbltnfi/sbltnfi-requiredSegments.user.js Install]
|-
|sbltnfi-short-sbmchang.user.js
|Adds a shortened (videoid/partialHash) link to all entries
|Videos
|[https://uscript.mchang.xyz/sbltnfi/sbltnfi-short-sbmchang.user.js Install]
|-
|sb.ltn.fi index page Restoring functionality
|Restore functionality of Index Page
|Index Page
|[https://github.com/MRuy NanoByte]
|Defunct
|}
{| class="wikitable"
|+Userscripts with Forks
!Name
!Description
!Changes
!Targets
!Author
!Install Link
|-
| rowspan="2" |sb.ltn.fi.clickablestarttime.user.js
| rowspan="2" |Make the startTime Clickable
|
| rowspan="2" |Videos
|[https://github.com/MRuy NanoByte]
|[https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.clickablestarttime.user.js Install]
|-
|More aggressive videoID searching
|[https://github.com/mchangrh blabdude]
|[https://gist.github.com/mchangrh/9507604353e37b6abc2f7f6b3c6e1338/raw/sbltnfi-clickable-starttime-fork.user.js Install]
|-
| rowspan="3" |sb.ltn.fi.videotitles.user.js
| rowspan="3" |Replace videoID with video title
|
| rowspan="3" |Videos
|[https://github.com/TheJzoli TheJzoli]
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.videotitles.user.js Install]
|-
|searching done through InnerTube API (faster)
| rowspan="2" |[https://github.com/mchangrh blabdude]
|[https://uscript.mchang.xyz/sbltnfi/fork/sbltnfi-it-videotitle.user.js Install]
|-
|searching done through YouTube OEmbed API (reliable)
|[https://uscript.mchang.xyz/sbltnfi/fork/sbltnfi-oembed-videotitle.user.js Install]
|-
|sb.ltn.fi.lockCategories
| rowspan="3" |VIP Tools - Category Locking, Voting, Category Changing
|
| rowspan="3" |Videos
|[https://github.com/FlorianZahn Deedit]
|[https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879/raw/sb.ltn.fi.lockCategories.user.js Install]
|-
|sb.ltn.fi.vipinterface.user.js
|Adds option to lock categories and vote on segments.
|[https://github.com/TheJzoli TheJzoli]
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.vipinterface.user.js Install]
|-
|SBBCoolHelper.user.js
|Adds options to purge, more category support
|[https://github.com/ducng99 Maxhyt]
|[https://raw.githubusercontent.com/ducng99/SBBCoolHelper/master/SBBCoolHelper.user.js Install]
|-
| rowspan="3" |sb.ltn.fi.coloredcategories.user.js
| rowspan="3" |Color code categories
|
| rowspan="3" |Videos
|[https://github.com/MRuy NanoByte]
|[https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.coloredcategories.user.js Install]
|-
|Subtler category colours
|[https://github.com/AcesFullOfKings AcesFullOfKings]
|[https://github.com/AcesFullOfKings/SponsorBlock-UserScripts/raw/main/colourTableCellsByCategory.user.js Install]
|-
|Subtler, rounder category colours with ::before
|[https://github.com/mini-bomba mini-bomba]
|[https://discord.com/channels/603643120093233162/908441365879337080/1166086251603046491 Download]
|-
| rowspan="2" |sbltnfi-preset-replace.user.js
| rowspan="2" |Preload sb.ltn.fi links with filters/sorting
|
| rowspan="2" |Video, User
|[https://github.com/x1yl Xtyl]
|[https://gist.github.com/x1yl/12156c5487fbd5fe5141f0c142143e0c/raw/sbltnfi-preset-replace.user.js Install]
|-
|
|[https://github.com/mchangrh blabdude]
|[https://uscript.mchang.xyz/sbltnfi/sbltnfi-preset-replace.user.js Install]
|}
{| class="wikitable"
|+Public VIP Userscripts
!Name
!Description
!Targets
!Author
!Install Link
|-
|sbltnfi-discord-badge.user.js
|Adds discord badge to users that are registered with sb-slash
|Users
|[https://github.com/mchangrh blabdude]
|[https://uscript.mchang.xyz/sbltnfi/sbltnfi-discord-badge.user.js Install]
|-
|sbltnfi-sbc-warn.user.js
|Adds a warning button that opens SBC to pre-fill userID and copies all videoIDs + titles from current page
|Users
|[https://github.com/mchangrh blabdude]
|[https://uscript.mchang.xyz/sbltnfi/sbltnfi-sbc-warn.user.js Install]
|}

==== YouTube (SponsorBlock) ====
[https://gist.github.com/jiraph/e60d0a7ae7071f1f4ef060948d50a9a1 User(Styles)] by jiraph

* Styles thumbnail label to match YouTube's existing thumbnail badges.
* Styles dropdown list in the submission menu with each category's respective color.
{| class="wikitable"
!Name
!Description
!Author
!Install Link
|-
|PlaylistVideoOpener.user.js
|Open the current video when watching a playlist
| rowspan="2" |[https://github.com/FlorianZahn Deedit]
|[https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879/raw/PlaylistVideoOpener.user.js Install]
|-
|sb.ltn.fi.DBBOpener.user.js
|Open's the video's page in SBB
|[https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879/raw/sb.ltn.fi.DBBOpener.user.js Install]
|-
|cane-sb-buttons.user.js
|SBC/ SBB/ Playlist opener buttons in one script
|[https://github.com/mlnrDev cane]
|[https://gist.githubusercontent.com/mlnrDev/b0949e9d3f2ba312b7523579976c9f31/raw/cane-sb-buttons.user.js Install]
|}

== Bookmarklets ==
Opening SponsorBlock Browser page while on the YouTube page<syntaxhighlight lang="js">
javascript:(function(){window.open('https://sb.ltn.fi/video/' + new URL(document.URL).searchParams.get("v") + '/')})()
</syntaxhighlight>Opening SponsorBlockControl browse page while on the YouTube Page<syntaxhighlight lang="js">
javascript:(function(){window.open('https://mruy.github.io/sponsorBlockControl-sveltekit/browse/?videoID=' + new URL(document.URL).searchParams.get("v"))})()
</syntaxhighlight>Open video outside of playlist<syntaxhighlight lang="js">
javascript:(function(){window.open('https://youtube.com/watch?v=' + new URL(document.URL).searchParams.get("v"))})()
</syntaxhighlight>

== 3rd Party Ports ==
[https://github.com/ajayyy/SponsorBlock/wiki/3rd-Party-Ports Github Wiki 3rd Party Ports]

[https://docs.google.com/spreadsheets/d/1vxSx06dPs_X3WCCC0bMztmlxbg_ETzAmp7sL70HFIew/edit?usp=sharing SponsorBlock Port Matrix] by mchangrh. Supported endpoints, segment types and documentation versions for different ports/libraries

== Misc ==
[https://github.com/mchangrh/sb-slash sb-slash] by mchangrh. Interact with SponsorBlock over Discord

[https://github.com/mchangrh/uscripts/tree/main uscripts] by mchangrh - collection of other userscripts for youtube and sb.ltn.fi
[[Category:SponsorBlock User Guides]]

VIP

2023-10-23T17:06:56Z

AcesFullOfKings: /* How can I become a VIP? */ padded wording a bit

VIP permission allows a user to have moderation-like powers in SponsorBlock. In the [https://sb.ltn.fi/ database explorer] you can recognize them by the 👑 (crown) next to their votes. On the [https://discord.gg/QnmVMpU discord] you can recognize them by their VIP role and maybe a green or light-green colored username.

==Moderating segments==
VIP downvotes and upvotes have more power. Downvotes will remove segments immediately.

VIP submitted or upvoted segments will be locked by default. These segments will always be shown instead of similarly timed but unlocked segments and can only be removed by other VIPs. In the [https://sb.ltn.fi/ database explorer], locked segments can be identified by a 🔒 (lock) icon next to the number of votes.

VIPs can also lock categories on videos to prevent future submissions for one or more categories and action types. This is typically done to prevent future submissions if there are no missing segments for that category and all existing segments are perfectly timed. Usually, Highlights and Filler are not locked as those categories are more subjective.

If you think a VIP has made a mistake, send a link to the video along with a brief explanation to the #incorrect-submissions channel in the [https://discord.gg/QnmVMpU discord].

==Moderating users==
Users can be moderated in two ways: bans and warnings.

Warnings are issued to users who make common mistakes when submitting segments. Upon trying to submit their next segment or voting on a segment they will receive a popup prompting them to ask about their warning on [https://discord.gg/QnmVMpU discord] or [https://matrix.to/#/+sponsorblock:ajay.app Matrix].

A ban is always approved by at least two VIPs. The ban may also entail the removal of all submissions.

Behavior that will result in a ban consists of but is not limited to:
*Malicious segments such as:
**Censoring certain people regardless of what they did or who they are.
**Censoring a part of a video containing information which is not a sponsor or other valid segment. (Politics, Religion, etc).
**Submitting segments to stop people from viewing creators.
**Vandalizing a video by submitting many incorrect segments, making the video hard to watch.
*Submitting segments that are consistently badly timed. If the segment degrades the [[Guidelines#Reduces_viewer_experience |viewer experience]] because it is badly timed, it shouldn't be there in the first place.
*Submitting segments for sponsors, intros, self-promos, etc. that do not exist.
*Submitting incorrect segments that are absurdly long to try and farm saved time and skips.

==How can I become a VIP?==
Applications for new VIPs are indefinitely paused.

==I am a new VIP. How does stuff work?==
Check [[VIP_Guide|this article]] out.

Community

2023-10-23T15:41:23Z

AcesFullOfKings: remove my silly outdated userscript

== Media ==
[https://github.com/cole8888/SponsorBlock-Flowchart SponsorBlock Flowchart] by E.Coli. Flowchart to help users choose the correct category when making submissions.

Please see the latest version on the [https://github.com/cole8888/SponsorBlock-Flowchart GitHub]
[[File:SB Flowchart small 1.10.1.png|none|thumb|500x500px|Flow chart to help users choose the correct category when making submissions.]]

== Websites ==
[https://sb.ltn.fi/ SponsorBlock Browser] by Lartza. Explore segments on a 5-minute delayed version of the live database

[https://mruy.github.io/sponsorBlockControl-sveltekit/ SponsorBlockControl-sveltekit] by Nanobyte. Vote on segments with UUID, also for VIP operations

[https://openapi.sb.mchang.xyz/ SponsorBlock Swagger] by mchangrh. Explore and try the SponsorBlock API.

=== Userscripts ===
Userscripts require a userscript manager like [https://www.tampermonkey.net/ Tampermonkey].

==== SponsorBlock Browser ====
{| class="wikitable"
|+Userscripts
!Name
!Description
!Targets
!Author
!Install Link
|-
|sb.ltn.fi.lastupdate.user.js
|Show the last update time
|Global
| rowspan="3" |[https://github.com/MRuy NanoByte]
|[https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.lastupdate.user.js Install]
|-
|sb.ltn.fi.similarsegments.user.js
|Color code similar segments
|Videos
|[https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.similarsegments.user.js Install]
|-
|sb.ltn.fi.sponsorblock.paste.ytlink.user.js
|Paste YT Link into videoID Field
|Navigation
|[https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.sponsorblock.paste.ytlink.user.js Install]
|-
|sb.ltn.fi.clickableellipsisnavigation.user.js
|ellipsis in page navigation will show a prompt for page number
|Navigation
| rowspan="6" |[https://github.com/TheJzoli TheJzoli]
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.clickableellipsisnavigation.user.js Install]
|-
|sb.ltn.fi.copyuserid.user.js
|Adds a button on the userID page to copy that userID
|Users
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.copyuserid.user.js Install]
|-
|sb.ltn.fi.copyvideopagelink.user.js
|copy video ID" (✂) button copies SBB page link instead
|Segment Options
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.copyvideopagelink.user.js Install]
|-
|sb.ltn.fi.forceupdate.user.js
|Fetches the segments and updated info for the video, so that you don't have to wait for the video page to update.
|Videos
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.forceupdate.user.js Install]
|-
|sb.ltn.fi.hidecolumns.user.js
|Hide any column you want
|Column/ Table
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.hidecolumns.user.js Install]
|-
|sb.ltn.fi.pagenavigationabovetable.user.js
|Duplicate page navigation element above table
|Navigation
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.pagenavigationabovetable.user.js Install]
|-
|sbltnfi-time-saved-column.user.js
|Adds time saved column
|Videos
|[https://github.com/NoMoreAngel NoMoreAngel]
|[https://github.com/NoMoreAngel/userscripts/raw/main/sbltnfi/sbltnfi-time-saved-column.user.js Install]
|-
|sbltnfi-imprecise-times.user.js
|Removes trailing insignificant zeroes from Start, End and Length
|Videos
| rowspan="4" |[https://github.com/mchangrh blabdude]
|[https://uscript.mchang.xyz/sbltnfi/sbltnfi-imprecise-times.user.js Install]
|-
|sbltnfi-refresh.user.js
|Refresh individual segments
|Videos
|[https://uscript.mchang.xyz/sbltnfi/sbltnfi-refresh.user.js Install]
|-
|sbltnfi-requiredSegments.user.js
|Copy sb.mchang.xyz/UUID link
|Videos
|[https://uscript.mchang.xyz/sbltnfi/sbltnfi-requiredSegments.user.js Install]
|-
|sbltnfi-short-sbmchang.user.js
|Adds a shortened (videoid/partialHash) link to all entries
|Videos
|[https://uscript.mchang.xyz/sbltnfi/sbltnfi-short-sbmchang.user.js Install]
|-
|sb.ltn.fi index page Restoring functionality
|Restore functionality of Index Page
|Index Page
|[https://github.com/MRuy NanoByte]
|Defunct
|}
{| class="wikitable"
|+Userscripts with Forks
!Name
!Description
!Changes
!Targets
!Author
!Install Link
|-
| rowspan="2" |sb.ltn.fi.clickablestarttime.user.js
| rowspan="2" |Make the startTime Clickable
|
| rowspan="2" |Videos
|[https://github.com/MRuy NanoByte]
|[https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.clickablestarttime.user.js Install]
|-
|More aggressive videoID searching
|[https://github.com/mchangrh blabdude]
|[https://gist.github.com/mchangrh/9507604353e37b6abc2f7f6b3c6e1338/raw/sbltnfi-clickable-starttime-fork.user.js Install]
|-
| rowspan="3" |sb.ltn.fi.videotitles.user.js
| rowspan="3" |Replace videoID with video title
|
| rowspan="3" |Videos
|[https://github.com/TheJzoli TheJzoli]
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.videotitles.user.js Install]
|-
|searching done through InnerTube API (faster)
| rowspan="2" |[https://github.com/mchangrh blabdude]
|[https://uscript.mchang.xyz/sbltnfi/fork/sbltnfi-it-videotitle.user.js Install]
|-
|searching done through YouTube OEmbed API (reliable)
|[https://uscript.mchang.xyz/sbltnfi/fork/sbltnfi-oembed-videotitle.user.js Install]
|-
|sb.ltn.fi.lockCategories
| rowspan="3" |VIP Tools - Category Locking, Voting, Category Changing
|
| rowspan="3" |Videos
|[https://github.com/FlorianZahn Deedit]
|[https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879/raw/sb.ltn.fi.lockCategories.user.js Install]
|-
|sb.ltn.fi.vipinterface.user.js
|Adds option to lock categories and vote on segments.
|[https://github.com/TheJzoli TheJzoli]
|[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.vipinterface.user.js Install]
|-
|SBBCoolHelper.user.js
|Adds options to purge, more category support
|[https://github.com/ducng99 Maxhyt]
|[https://raw.githubusercontent.com/ducng99/SBBCoolHelper/master/SBBCoolHelper.user.js Install]
|-
| rowspan="2" |sb.ltn.fi.coloredcategories.user.js
| rowspan="2" |Color code categories
|
| rowspan="2" |Videos
|[https://github.com/MRuy NanoByte]
|[https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.coloredcategories.user.js Install]
|-
|Subtler category colours
|[https://github.com/AcesFullOfKings AcesFullOfKings]
|[https://github.com/AcesFullOfKings/SponsorBlock-UserScripts/raw/main/colourTableCellsByCategory.user.js Install]
|-
| rowspan="2" |sbltnfi-preset-replace.user.js
| rowspan="2" |Preload sb.ltn.fi links with filters/sorting
|
| rowspan="2" |Video, User
|[https://github.com/x1yl Xtyl]
|[https://gist.github.com/x1yl/12156c5487fbd5fe5141f0c142143e0c/raw/sbltnfi-preset-replace.user.js Install]
|-
|
|[https://github.com/mchangrh blabdude]
|[https://uscript.mchang.xyz/sbltnfi/sbltnfi-preset-replace.user.js Install]
|}
{| class="wikitable"
|+Public VIP Userscripts
!Name
!Description
!Targets
!Author
!Install Link
|-
|sbltnfi-discord-badge.user.js
|Adds discord badge to users that are registered with sb-slash
|Users
|[https://github.com/mchangrh blabdude]
|[https://uscript.mchang.xyz/sbltnfi/sbltnfi-discord-badge.user.js Install]
|-
|sbltnfi-sbc-warn.user.js
|Adds a warning button that opens SBC to pre-fill userID and copies all videoIDs + titles from current page
|Users
|[https://github.com/mchangrh blabdude]
|[https://uscript.mchang.xyz/sbltnfi/sbltnfi-sbc-warn.user.js Install]
|}

==== YouTube (SponsorBlock) ====
[https://gist.github.com/jiraph/e60d0a7ae7071f1f4ef060948d50a9a1 User(Styles)] by jiraph

* Styles thumbnail label to match YouTube's existing thumbnail badges.
* Styles dropdown list in the submission menu with each category's respective color.
{| class="wikitable"
!Name
!Description
!Author
!Install Link
|-
|PlaylistVideoOpener.user.js
|Open the current video when watching a playlist
| rowspan="2" |[https://github.com/FlorianZahn Deedit]
|[https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879/raw/PlaylistVideoOpener.user.js Install]
|-
|sb.ltn.fi.DBBOpener.user.js
|Open's the video's page in SBB
|[https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879/raw/sb.ltn.fi.DBBOpener.user.js Install]
|-
|cane-sb-buttons.user.js
|SBC/ SBB/ Playlist opener buttons in one script
|[https://github.com/mlnrDev cane]
|[https://gist.githubusercontent.com/mlnrDev/b0949e9d3f2ba312b7523579976c9f31/raw/cane-sb-buttons.user.js Install]
|}

== Bookmarklets ==
Opening SponsorBlock Browser page while on the YouTube page<syntaxhighlight lang="js">
javascript:(function(){window.open('https://sb.ltn.fi/video/' + new URL(document.URL).searchParams.get("v") + '/')})()
</syntaxhighlight>Opening SponsorBlockControl browse page while on the YouTube Page<syntaxhighlight lang="js">
javascript:(function(){window.open('https://mruy.github.io/sponsorBlockControl-sveltekit/browse/?videoID=' + new URL(document.URL).searchParams.get("v"))})()
</syntaxhighlight>Open video outside of playlist<syntaxhighlight lang="js">
javascript:(function(){window.open('https://youtube.com/watch?v=' + new URL(document.URL).searchParams.get("v"))})()
</syntaxhighlight>

== 3rd Party Ports ==
[https://github.com/ajayyy/SponsorBlock/wiki/3rd-Party-Ports Github Wiki 3rd Party Ports]

[https://docs.google.com/spreadsheets/d/1vxSx06dPs_X3WCCC0bMztmlxbg_ETzAmp7sL70HFIew/edit?usp=sharing SponsorBlock Port Matrix] by mchangrh. Supported endpoints, segment types and documentation versions for different ports/libraries

== Misc ==
[https://github.com/mchangrh/sb-slash sb-slash] by mchangrh. Interact with SponsorBlock over Discord

VIP Guide

2023-08-17T15:15:59Z

AcesFullOfKings: /* Manipulating Segments */ fix typo

__FORCETOC__

This article covers tools and work sequences for [[VIP|VIPs]]. VIPs can help moderate videos and investigate potential abuse if they have the time for it, but there are no expectations for the amount of work or commitment. VIP is a permission level, not a job.

Mandatory Informative <s>Anti-Union propaganda</s> video for all VIPs ([https://youtube.com/watch?v=uRpwVwFxyk4 This is a joke])

== Code of Conduct ==
Don't question VIPs on submitting a segment with a small difference to yours, unless you believe the new segment is worse than the original. In the end it is about creating good segments and not about your stats.

== Tools and Terminology ==
*[https://sb.ltn.fi/ SponsorBlock Browser] by Lartza. Short: SBB
**[https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6 Userscripts] by Nanobyte. They make SBB prettier and easier to read, as well as utility.
**[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181 Userscripts] by TheJzoli. Small user experience improvements for SBB.
**[https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879 Userscripts] by Deedit. Locking, category change and voting for SBB. SBB opener for YouTube.
**[https://github.com/ducng99/SBBCoolHelper Userscript] by Maxhyt. Locking, category change and voting for SBB.
**Explanations of all features at the top of the respective sites. You will need a userscript manager like [https://www.tampermonkey.net/ Tampermonkey]. Press raw on the right of the filename and then install.
**[[Community|Bookmarklets]]
*<s>[https://mruy.github.io/sponsorBlockControl/ SponsorBlockControl] by Nanobyte. Short: SBC</s>
*[https://mruy.github.io/sponsorBlockControl-sveltekit/ SponsorBlockControl-sveltekit] by Nanobyte. Short: SBC
**This version is updated more frequently and and has some features not in base SBC
*[https://github.com/mchangrh/sb-slash sb-slash] by mchangrh.
*👍 is commonly used to show support for a message, supporting a ban or another action taken while ✅ is used to show confirmation. Alt + left click will add an emoji to your favorites.
*For videos in #incorrect-submissions, react with ✅ to indicate that it is done, ❌ if the report is incorrect and ⏲️ to indicate that you are working on a message
**both ✅ and ❌ will trigger the bot to remove embeds on the message
*A full list of community projects and tools are available at [[Community]]

== Moderating Users ==

=== Warnings ===

==== What constitutes a warning and when to lift it? ====
Warnings should be issued to users who misinterpret the rules and can be set straight by simply telling them to review the rules and [[Guidelines|guidelines]], e.g. users who often mislabel the category can just use the flowchart.

The point of a warning is to get the user into matrix or discord so that we can talk to them, make sure they go over the guidelines and hopefully learn from their mistake.

Once they have confirmed they have read the guidelines, checked out their previous mistakes and if applicable, read the corresponding articles, the warning may be lifted. A possible prompt for this can be
<nowiki>Please read the guidelines and confirm if you understand the mistakes, or ask any questions if you have any.</nowiki>
Warnings can be lifted with sb-slash<ref name=":0">https://github.com/mchangrh/sb-slash/blob/main/docs/vip.md</ref>, SBC<ref name=":1">https://mruy.github.io/sponsorBlockControl</ref>

==== How to issue a warning? ====
In <code>#report-a-user</code> post a message with the warning reasons and link their profile on SBB. The message should look like this:
Warning for <nowiki>https://sb.ltn.fi/userid/7a7e6f513cd2a7a9abfd5c3dec7c8e2ea0e5e26f2683a83342ebad0f68d7754e/</nowiki>

Reasons:

Intro covering content:
<nowiki>https://sb.ltn.fi/video/kTZrV4M5Tcs/</nowiki>
<nowiki>https://sb.ltn.fi/video/BoQU3_4o90s/</nowiki>

Sponsor doesn't include segue:
<nowiki>https://sb.ltn.fi/video/NxYPNNftnNQ/</nowiki>
<nowiki>https://sb.ltn.fi/video/Fci_ALdEzGc/</nowiki>

Other unrelated tips...

'''The warning reason is everything after "Reasons".'''

On SBC<ref name=":1" /> paste the userID and the warning reason. Please paste the warning reasons! Yes, it can be quite long. If you want to give tips to the user, do it now, as they will see this message. If the user has many wrong segments, but you still feel like a warning is appropriate, consider removing all old segments by banning and unbanning them.

==== What does the user experience? ====
When the user is submitting or voting on a segment, a chat window of <code>#questions</code> will open and automatically post a message with their warning reason. They cannot navigate to any other channels, so don't link to a discord message or other channels. Their username will be set to their userID and they will see an [https://en.wikipedia.org/wiki/Alert_dialog_box alertbox] with the following text:
Submission rejected due to a warning from a moderator. This means that we noticed you were making some common mistakes that are not malicious, and we just want to clarify the rules. Could you please send a message in discord.gg/SponsorBlock or matrix.to/#/#sponsor:ajay.app so we can further help you? Your userID is ${userID}.

Warning reason: ${reason}

=== Bans ===
Bans of users with many submissions need approval of one other VIP. Don't hold back on banning users, when they submit bad segments. They should be mature enough, that their bad segments show up for everyone to see.

==== What constitutes a ban? ====
*A ban should be issued to users who break the rules in a way, that explaining them to them would not be feasible.
*Their submissions show disregard of the guidelines, in such a way that good faith cannot be assumed any more.
**Censoring people or stuff shown for pretty much all reasons
*Submissions were created to lessen the viewer experience.
*It shows, that the user never bothered reading the category descriptions.

==== How to issue a ban? ====
In #bans post a message with the ban reasons and link their profile on SBB. <code>#bans</code> is a private channel. The message should look like this:
(Recommending) ban for <nowiki>https://sb.ltn.fi/userid/7a7e6f513cd2a7a9abfd5c3dec7c8e2ea0e5e26f2683a83342ebad0f68d7754e/</nowiki>

Reasons:

Intro covering content:
<nowiki>https://sb.ltn.fi/video/kTZrV4M5Tcs/</nowiki>
<nowiki>https://sb.ltn.fi/video/BoQU3_4o90s/</nowiki>

Sponsor doesn't include segue:
<nowiki>https://sb.ltn.fi/video/NxYPNNftnNQ/</nowiki>
<nowiki>https://sb.ltn.fi/video/Fci_ALdEzGc/</nowiki>
Wait for another VIP's support with 👍. After receiving approval, head to SBC<ref name=":1" /> and ban the user. You may choose to hide categories. Confirm your ban with ✅.

==== What does the user experience? ====
The user will not notice they have been banned, as we issue only shadowbans. As long as the user still uses the same IP address, they will continue seeing their segments, but no one else will. Their views will stay at zero, so their time saved and related stats will stop changing.

==== How can I recognize a banned user on SBB? ====
Banned users will have an ❌ in the shadow hidden column of their segments on SBB.

=== Temporary VIPs ===
Permanent VIPs can grant temporary channel-specific VIP voting powers to users.

Temporary VIPs can

* Add/ Remove locks on segments
* Bring back downvoted/ shadowhidden/ hidden segments
* Remove locked segments
* Instantly remove any segment
* Instantly change the category of any segment

Cannot...

* Submit on locked videos
* Do anything non-voting that other VIPs would be able to do

This permission only lasts for 24 hours and can only be granted for one channel at a time.

Temporary VIPs will have their reports show up as "Report by Temporary VIP User" in <code>#submission-downvotes</code>

This can be done on sb-slash<ref name=":0" /> and SBC<ref name=":1" />

== Moderating Videos ==

=== Knowledge of Categories ===
Read the [[Guidelines|guidelines]] and feel free to ask in the discord after checking the wiki.

=== Manipulating Segments ===
Voting and category changing can be done with SBC<ref name=":1" />, Deedit's userscript<ref name=":2">https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879</ref> or on YouTube.
* Upvoting a segment will lock it. This means that it will always be shown and immune to downvotes, even from the submitter.
* Downvoting a segment will immediately remove it, no matter whose it is.
** Locked segments are marked yellow to warn the VIP, that this segment was approved by a VIP. If you aren't sure, search for the videoID/UUID in Discord or ask. Not all decisions are well documented.
* Undoing a vote will revert the segment's votes to what they were before your downvote or upvote. It will also remove other VIP's locks.
* If a segment is in a wrong category, you can change it directly on YouTube, SBC<ref name=":1" /> or sb-slash<ref name=":0" />
** Locked categories are colored yellow in the category selector. Be careful when changing to a locked category or submitting in one.

=== Locking Categories ===

* Review the entire video and make sure that all displayed segments are correct.
* Make sure to include a reason why segments should not be there if applicable.
* You can lock videos if you are concerned that segments will be spammed, before or after working on a video.
** It is explicitly allowed to lock popular videos at release to prevent spam.
* The most recent lock reason will be displayed.
*This can be done with sb-slash<ref name=":0" />, SBC<ref name=":1" />, SBBCool<ref>https://github.com/ducng99/SBBCoolHelper</ref> and sb.ltn.fi.lockCategories<ref name=":2" />

When users try to submit a category that is locked, they will receive the following message:
New submissions are not allowed for the following category: {category}. A moderator has decided that no new segments are needed on this video and that all current segments of this category are timed perfectly.

Lock reason: {reason}

If you believe this is incorrect, please contact someone on discord.gg/SponsorBlock or matrix.to/#/#sponsor:ajay.app
If the locked category is sponsor, the previous prompt will be expanded by this:
Maybe the segment you are submitting is a different category that you have not enabled and is not a sponsor. Categories that aren't sponsor, such as self-promotion can be enabled in the options.

=== Submitting Segments ===
Your segments should be perfectly accurate and follow the rules. This is because normal users cannot remove your segments and VIPs don't want to remove other VIPs' segments. If you are unsure, feel free to ask.

=== Abuse ===
Don't go around downvoting established segments. Odds are, you probably misunderstood the rules and could lose your VIP status if you are incorrigible.

=== Clearing Cache/ Purging Videos ===
Segments that have segments that are erroneously displaying even after they have been downvoted might need to have their cache cleared. Feel free to do this whenever but only if it does not resolve itself in a few refreshes. This can be done with SBC<ref name=":1" /> and sb-slash<ref name=":0" />

Videos that have been changed post-upload by the submitter (usually to remove a part of the video) and consequently have their segments offset should be cleared with "Purge Video". This can be done in SBC<ref name=":1" /> and sb-slash<ref name=":0" />. If there are segments that are still accurate enough, they can be un-hidden with a VIP upvote.

== SponsorBlock VIP UI ==
Shortly after becoming a VIP, your UI will highlight locked segments, similar to SBB.

Locked segments are usually submitted by VIPs or locked by VIPs. When submitting over a locked category, make sure that it wasn't purposefully excluded, either by checking the lock reason or asking the locking VIP in the discord.
[[File:Vipui-popup.png|none|thumb|Locked segments have a yellow downvote]]
[[File:Vip-ui-category-dropdown.png|none|thumb|Locked categories are highlighted in yellow]]

== Searching Segments ==
When searching for segments en masse, SBB is recommended but has an update delay of 10 minutes.

This can be mitigated with <code>[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181 sb.ltn.fi.forceupdate.user.js]</code> by TheJzoli to force get new segments and update existing ones

and <code>[https://gist.github.com/mchangrh/c693f8e1de2b6a5067ae9d5e994f6758/raw/sbltnfi-refresh.user.js sbltnfi-refresh.user.js]</code> by blab to force update a single segment

Alternatively sb-slash can be used to search for segments on videos

* /searchsegements - get all segments on video, regardless of votes or hidden status
* /skipsegments - get segments displayed on video
* /segmentinfo - look up information from the segment UUID including user agent
for quick/convenient moderation sb-slash's [https://github.com/mchangrh/sb-slash/blob/main/docs/vip.md /vip] command can also be used

== Reviewing Other Users For Permanent VIP ==
Applicants should have the <code>requesting VIP</code> role, otherwise approach them privately.

The most important thing for VIPs is to be consistent and receptive to feedback.

* When looking at their segments, we shouldn't give them a warning - see [[Guidelines]]
* They know what's good in their submission
* They know what's bad in their submissions
* They're involved and consistent.
* They should have at least 25 submissions
* They have to have submissions dating back at least a month.
* Their segments should be consistently good
* They should have a good grasp on any category they've made a submission with.

== Tool Feature Matrix ==
{| class="wikitable mw-collapsible"
|+Tool Feature Matrix
!Tool Name
!Voting
!Change
Category
!Locking
Category
!Warning
!Unwarning
!Banning
!Temp
VIP
!Clearing
Cache
!Purging
Videos
|-
|Browser Extension
|✅
|✅
|
|
|
|
|
|
|
|-
|SponsorBlockControl
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|-
|sb-slash
|✔️<sup>*</sup>
|✅
|✔️<sup>*</sup>
|
|✔️<sup>*</sup>
|
|✔️<sup>*</sup>
|✅
|✅
|-
|SBBCool
|✅
|✅
|✅
|
|
|
|
|
|✅
|-
|Deedit's Script
|✅
|✅
|✅
|
|
|
|
|✅
|✅
|}
<nowiki>*</nowiki> Actions done with sb-slash are not as anonymous, as they are logged to a VIP-only channel

=== Citations ===

Community

2023-05-24T10:53:24Z

AcesFullOfKings: /* Userscripts */ update github username. old redirect will eventually stop working

== Media ==
[https://github.com/cole8888/SponsorBlock-Flowchart SponsorBlock Flowchart] by E.Coli. Flowchart to help users choose the correct category when making submissions.

Please see the latest version on the [https://github.com/cole8888/SponsorBlock-Flowchart GitHub]
[[File:SB Flowchart small 1.10.1.png|none|thumb|500x500px|Flow chart to help users choose the correct category when making submissions.]]

== Websites ==
[https://sb.ltn.fi/ SponsorBlock Browser] by Lartza. Explore segments on a 5-minute delayed version of the live database

[https://mruy.github.io/sponsorBlockControl-sveltekit/ SponsorBlockControl-sveltekit] by Nanobyte. Vote on segments with UUID, also for VIP operations

[https://openapi.sb.mchang.xyz/ SponsorBlock Swagger] by mchangrh. Explore and try the SponsorBlock API.

=== Userscripts ===
Userscripts require a userscript manager like [https://www.tampermonkey.net/ Tampermonkey].

==== SponsorBlock Browser ====
[https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6 Userscripts] by Nanobyte

* Shows last update time ([https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.lastupdate.user.js Install])
* Color highlights segments that are similar ([https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.similarsegments.user.js Install])
* Color highlights categories ([https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.coloredcategories.user.js Install])
* Make startTime clickable ([https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.clickablestarttime.user.js Install])
* Paste YT link into videoID field ([https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.sponsorblock.paste.ytlink.user.js Install])

[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181 Userscripts] by TheJzoli

* Replace videoID with video title ([https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.videotitles.user.js Install])
* Clicking ellipsis will navigate to specified page ([https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.clickableellipsisnavigation.user.js Install])
* Hide any column you want ([https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.hidecolumns.user.js Install])
* Duplicate page navigation element above table ([https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.pagenavigationabovetable.user.js Install])
* Add button to userID page to copy that userID ([https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.copyuserid.user.js Install])
* "✂" button copies the link to the video's SBB page instead of video ID ([https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.copyvideopagelink.user.js Install])
*Fetches the segments and updated info for the video, so that you don't have to wait for the video page to update ([https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.forceupdate.user.js Install])

[https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879 Userscripts] by Deedit
* Vip tools for [https://sb.ltn.fi/ SBB]. Voting; Category change; Locking ([https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879/raw/sb.ltn.fi.lockCategories.user.js Install])
* Opens the video's page on SBB. ([https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879/raw/sb.ltn.fi.DBBOpener.user.js Install])
* Opens a video outside of its playlist. ([https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879/raw/PlaylistVideoOpener.user.js Install])
[https://github.com/mchangrh/uscripts/tree/main/sbltnfi Userscripts] by blabdude

* (VIP) Adds discord badge to users that are registered with sb-slash ([https://uscript.mchang.xyz/sbltnfi/sbltnfi-discord-badge.user.js Install])
* Removes trailing insignificant zeroes from Start, End and Length ([https://uscript.mchang.xyz/sbltnfi/sbltnfi-imprecise-times.user.js Install])
* Replace or redirect all sb.ltn.fi links to be preloaded with filters ([https://uscript.mchang.xyz/sbltnfi/sbltnfi-preset-replace.user.js Install])
* Fork of Deedit's sb.ltn.fi/video/-Opener with preset filters ([https://uscript.mchang.xyz/sbltnfi/sbltnfi-preset-video-link.user.js Install])
* Refresh individual segments ([https://uscript.mchang.xyz/sbltnfi/sbltnfi-refresh.user.js Install])
* Copy sb.mchang.xyz/UUID link. ([https://uscript.mchang.xyz/sbltnfi/sbltnfi-requiredSegments.user.js Install])
*Fork of Nanobyte's Clickable StartTime with more aggressive videoID searching ([https://gist.github.com/mchangrh/9507604353e37b6abc2f7f6b3c6e1338/raw/sbltnfi-clickable-starttime-fork.user.js Install])
*Fork of TheJzoli's videoTitles script with searching done through InnerTube ([https://uscript.mchang.xyz/sbltnfi/fork/sbltnfi-it-videotitle.user.js Install])([https://uscript.mchang.xyz/sbltnfi/fork/sbltnfi-oembed-videotitle.user.js With OEmbed API])
*Adds a big red warning to the top of the screen with requiredSegments are present ([https://uscript.mchang.xyz/sbltnfi/sbltnfi-requiredSegments.user.js Install])
[https://gist.github.com/x1yl/12156c5487fbd5fe5141f0c142143e0c Userscripts] by xtyl

* Replaces or redirect all sb.ltn.fi links to be pre-loaded with filters ([https://gist.github.com/x1yl/12156c5487fbd5fe5141f0c142143e0c/raw/sbltnfi-preset-replace.user.js Install])
[https://gist.github.com/caneleex/b0949e9d3f2ba312b7523579976c9f31 Userscripts] by Cane

* SBC/ SBB/ Playlist opener buttons in one script ([https://gist.githubusercontent.com/caneleex/b0949e9d3f2ba312b7523579976c9f31/raw/cane-sb-buttons.user.js Install])
[https://github.com/AcesFullOfKings/SponsorBlock-UserScripts Userscripts] by AcesFullOfKings

* Subtler category colours for sb.ltn.fi ([https://github.com/AcesFullOfKings/SponsorBlock-UserScripts/raw/main/colourTableCellsByCategory.user.js Install])

[https://github.com/ducng99/SBBCoolHelper SBBCoolHelper] by Maxhyt

[https://raw.githubusercontent.com/ducng99/SBBCoolHelper/master/SBBCoolHelper.user.js Install]

* VIP tools for SBB
** Voting
** Category Change
** Locking
[https://github.com/NoMoreAngel/userscripts Userscripts] by NoMoreAngel

* Adds time saved column for each segment ([https://github.com/NoMoreAngel/userscripts/raw/main/sbltnfi/sbltnfi-time-saved-column.user.js Install])

==== YouTube (SponsorBlock) ====
[https://gist.github.com/jiraph/e60d0a7ae7071f1f4ef060948d50a9a1 User(Styles)] by jiraph

* Styles thumbnail label to match YouTube's existing thumbnail badges.
* Styles dropdown list in the submission menu with each category's respective color.
*

== Bookmarklets ==
Opening SponsorBlock Browser page while on the YouTube page<syntaxhighlight lang="js">
javascript:(function(){window.open('https://sb.ltn.fi/video/' + new URL(document.URL).searchParams.get("v") + '/')})()
</syntaxhighlight>Opening SponsorBlockControl browse page while on the YouTube Page<syntaxhighlight lang="js">
javascript:(function(){window.open('https://mruy.github.io/sponsorBlockControl-sveltekit/browse/?videoID=' + new URL(document.URL).searchParams.get("v"))})()
</syntaxhighlight>Open video outside of playlist<syntaxhighlight lang="js">
javascript:(function(){window.open('https://youtube.com/watch?v=' + new URL(document.URL).searchParams.get("v"))})()
</syntaxhighlight>

== 3rd Party Ports ==
[https://github.com/ajayyy/SponsorBlock/wiki/3rd-Party-Ports Github Wiki 3rd Party Ports]

[https://docs.google.com/spreadsheets/d/1vxSx06dPs_X3WCCC0bMztmlxbg_ETzAmp7sL70HFIew/edit?usp=sharing SponsorBlock Port Matrix] by mchangrh. Supported endpoints, segment types and documentation versions for different ports/libraries

== Misc ==
[https://github.com/mchangrh/sb-slash sb-slash] by mchangrh. Interact with SponsorBlock over Discord

Community

2023-04-06T13:39:22Z

AcesFullOfKings: Add "Subtler Category Colours" to userscript list

== Media ==
[https://github.com/cole8888/SponsorBlock-Flowchart SponsorBlock Flowchart] by E.Coli. Flowchart to help users choose the correct category when making submissions.

Please see the latest version on the [https://github.com/cole8888/SponsorBlock-Flowchart GitHub]
[[File:SB Flowchart small 1.10.1.png|none|thumb|500x500px|Flow chart to help users choose the correct category when making submissions.]]

== Websites ==
[https://sb.ltn.fi/ SponsorBlock Browser] by Lartza. Explore segments on a 5-minute delayed version of the live database

[https://mruy.github.io/sponsorBlockControl-sveltekit/ SponsorBlockControl-sveltekit] by Nanobyte. Vote on segments with UUID, also for VIP operations

[https://openapi.sb.mchang.xyz/ SponsorBlock Swagger] by mchangrh. Explore and try the SponsorBlock API.

=== Userscripts ===
Userscripts require a userscript manager like [https://www.tampermonkey.net/ Tampermonkey].

==== SponsorBlock Browser ====
[https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6 Userscripts] by Nanobyte

* Shows last update time ([https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.lastupdate.user.js Install])
* Color highlights segments that are similar ([https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.similarsegments.user.js Install])
* Color highlights categories ([https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.coloredcategories.user.js Install])
* Make startTime clickable ([https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.clickablestarttime.user.js Install])
* Paste YT link into videoID field ([https://gist.github.com/MRuy/ca74d6a359c487d760f4a698e76fb0d6/raw/sb.ltn.fi.sponsorblock.paste.ytlink.user.js Install])

[https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181 Userscripts] by TheJzoli

* Replace videoID with video title ([https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.videotitles.user.js Install])
* Clicking ellipsis will navigate to specified page ([https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.clickableellipsisnavigation.user.js Install])
* Hide any column you want ([https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.hidecolumns.user.js Install])
* Duplicate page navigation element above table ([https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.pagenavigationabovetable.user.js Install])
* Add button to userID page to copy that userID ([https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.copyuserid.user.js Install])
* "✂" button copies the link to the video's SBB page instead of video ID ([https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.copyvideopagelink.user.js Install])
*Fetches the segments and updated info for the video, so that you don't have to wait for the video page to update ([https://gist.github.com/TheJzoli/8a4cd979d433b7359cdf61c238bc0181/raw/sb.ltn.fi.forceupdate.user.js Install])

[https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879 Userscripts] by Deedit
* Vip tools for [https://sb.ltn.fi/ SBB]. Voting; Category change; Locking ([https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879/raw/sb.ltn.fi.lockCategories.user.js Install])
* Opens the video's page on SBB. ([https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879/raw/sb.ltn.fi.DBBOpener.user.js Install])
* Opens a video outside of its playlist. ([https://gist.github.com/FlorianZahn/785599a860328fae0724ad5b2b3f7879/raw/PlaylistVideoOpener.user.js Install])
[https://github.com/mchangrh/uscripts/tree/main/sbltnfi Userscripts] by blabdude

* (VIP) Adds discord badge to users that are registered with sb-slash ([https://uscript.mchang.xyz/sbltnfi/sbltnfi-discord-badge.user.js Install])
* Removes trailing insignificant zeroes from Start, End and Length ([https://uscript.mchang.xyz/sbltnfi/sbltnfi-imprecise-times.user.js Install])
* Replace or redirect all sb.ltn.fi links to be preloaded with filters ([https://uscript.mchang.xyz/sbltnfi/sbltnfi-preset-replace.user.js Install])
* Fork of Deedit's sb.ltn.fi/video/-Opener with preset filters ([https://uscript.mchang.xyz/sbltnfi/sbltnfi-preset-video-link.user.js Install])
* Refresh individual segments ([https://uscript.mchang.xyz/sbltnfi/sbltnfi-refresh.user.js Install])
* Copy sb.mchang.xyz/UUID link. ([https://uscript.mchang.xyz/sbltnfi/sbltnfi-requiredSegments.user.js Install])
*Fork of Nanobyte's Clickable StartTime with more aggressive videoID searching ([https://gist.github.com/mchangrh/9507604353e37b6abc2f7f6b3c6e1338/raw/sbltnfi-clickable-starttime-fork.user.js Install])
*Fork of TheJzoli's videoTitles script with searching done through InnerTube ([https://uscript.mchang.xyz/sbltnfi/fork/sbltnfi-it-videotitle.user.js Install])([https://uscript.mchang.xyz/sbltnfi/fork/sbltnfi-oembed-videotitle.user.js With OEmbed API])
*Adds a big red warning to the top of the screen with requiredSegments are present ([https://uscript.mchang.xyz/sbltnfi/sbltnfi-requiredSegments.user.js Install])
[https://gist.github.com/x1yl/12156c5487fbd5fe5141f0c142143e0c Userscripts] by xtyl

* Replaces or redirect all sb.ltn.fi links to be pre-loaded with filters ([https://gist.github.com/x1yl/12156c5487fbd5fe5141f0c142143e0c/raw/sbltnfi-preset-replace.user.js Install])
[https://gist.github.com/caneleex/b0949e9d3f2ba312b7523579976c9f31 Userscripts] by Cane

* SBC/ SBB/ Playlist opener buttons in one script ([https://gist.githubusercontent.com/caneleex/b0949e9d3f2ba312b7523579976c9f31/raw/cane-sb-buttons.user.js Install])
[https://github.com/theonefoster/SponsorBlock-UserScripts Userscripts] by AcesFullOfKings

* Subtler category colours for sb.ltn.fi ([https://github.com/theonefoster/SponsorBlock-UserScripts/raw/main/colourTableCellsByCategory.user.js Install])

[https://github.com/ducng99/SBBCoolHelper SBBCoolHelper] by Maxhyt

[https://raw.githubusercontent.com/ducng99/SBBCoolHelper/master/SBBCoolHelper.user.js Install]

* VIP tools for SBB
** Voting
** Category Change
** Locking
[https://github.com/NoMoreAngel/userscripts Userscripts] by NoMoreAngel

* Adds time saved column for each segment ([https://github.com/NoMoreAngel/userscripts/raw/main/sbltnfi/sbltnfi-time-saved-column.user.js Install])

== Bookmarklets ==
Opening SponsorBlock Browser page while on the YouTube page<syntaxhighlight lang="js">
javascript:(function(){window.open('https://sb.ltn.fi/video/' + new URL(document.URL).searchParams.get("v") + '/')})()
</syntaxhighlight>Opening SponsorBlockControl browse page while on the YouTube Page<syntaxhighlight lang="js">
javascript:(function(){window.open('https://mruy.github.io/sponsorBlockControl-sveltekit/browse/?videoID=' + new URL(document.URL).searchParams.get("v"))})()
</syntaxhighlight>Open video outside of playlist<syntaxhighlight lang="js">
javascript:(function(){window.open('https://youtube.com/watch?v=' + new URL(document.URL).searchParams.get("v"))})()
</syntaxhighlight>

== 3rd Party Ports ==
[https://github.com/ajayyy/SponsorBlock/wiki/3rd-Party-Ports Github Wiki 3rd Party Ports]

[https://docs.google.com/spreadsheets/d/1vxSx06dPs_X3WCCC0bMztmlxbg_ETzAmp7sL70HFIew/edit?usp=sharing SponsorBlock Port Matrix] by mchangrh. Supported endpoints, segment types and documentation versions for different ports/libraries

== Misc ==
[https://github.com/mchangrh/sb-slash sb-slash] by mchangrh. Interact with SponsorBlock over Discord

FAQ

2023-03-18T11:29:41Z

AcesFullOfKings: /* How does voting work and what do certain amounts of votes mean? */

==What are the most frequent mistakes when submitting segments?==
*Not including the segue (smooth verbal transition to the [[Sponsor | sponsor]])
*Submitting [[Sponsor | sponsor]] segments on videos that are either solely about the sponsor '''or''' could show bias towards it (e.g. when using the sponsored product is an essential part of the video's content and the creator voices their opinion, viewers need to be aware of the sponsor disclosure)
*Mistaking [[Unpaid/Self_Promotion | self promotion]] for a sponsorship
*Segments at the very beginning not starting precisely at 0:00, but rather something like 0.0314159 seconds into the video. Similarly, segments not sticking to the exact end of the video when they should.
*Misunderstanding of the [[Intermission/Intro_Animation | intermission]] category. More often than not, it should not contain any spoken words, and it's not meant for just about anything that users find insignificant, like the creator saying "hello."
Please check out [[Advice_for_submitting | this page]] for more tips.

==I noticed an incorrect submission. What should I do?==
The first thing you can do is simply downvote it in the pop-up. If it's just the wrong category but correctly timed, you can select "Wrong Category" after clicking the pencil icon. Additionally, when the timing of an existing segment could be better, submitting your own correct segment in its place may reduce the amount of times the faulty one appears.

If you're on SponsorBlock [https://discord.gg/QnmVMpU Discord server], feel free to report it in the #incorrect-submissions channel, where a [[VIP]] can take a look at it. Even if the video is not in English, you can still give it a shot. Especially if you believe it’s a purposefully malicious spam, we would really like to be notified.

==Why am I getting an error when trying to submit a segment?==
400: Bad Request (Your inputs are wrong/impossible)
*Your segment is maybe 0 seconds long
*There is a minimum length for Sponsor segments
403: Rejected by auto moderator:
*A human moderator has locked the category or the complete video, all the segments that are needed are there and timed perfectly. If there isn't already a segment where you want to add one, try reloading the video. Make sure that you have activated all categories, as the segment you want to add is maybe in the wrong category. The video is locked to prevent spamming of bad segments that need to be removed later.
409: Duplicate: You already submitted this segment, delete the one you can still add and all should be good

==How is “non-music” supposed to co-exist with other categories?==
[[Music:_Non-Music_Section | Non-music]] exists separately from other categories and may overlap with them. In the end, the video should resemble the Spotify or any other mix version as close as possible.

==What are advanced tips for submitting?==
You can find many tips in [[Advice_for_submitting | this article]].


==How to browse the database and view all my submissions with details?==
*You can view the database and all submissions on this website: https://sb.ltn.fi/ (this should update every 5 minutes)
*You can download the entire database [https://sponsor.ajay.app/database here].
Note: Your public userID in the database is different than your private one in the SponsorBlock options tab.

==Can I edit/remove the segment that I uploaded?==
Once your segment is uploaded, you can still easily remove it or change its category by clicking thumbs down on the skip notice and choosing "Incorrect/Wrong Timing" or "Wrong Category" respectively. In case of your own submissions, your votes will have an immediate effect.

Editing timestamps of submitted segments is not possible, so in order to correct a segment downvote it and submit a new one.
==I think my segment might have been deleted. Why?==
One possibility is that other users downvoted it. If it was removed by a moderator however, possible reasons include:
*Some other submission in that place was a bit better (even if it’s just a fraction of a second, it does make a difference)
*It was against the [[Guidelines]]
*Any mistake mentioned in [[FAQ#What_are_the_most_frequent_mistakes_when_submitting_segments.3F | answer #1]]

==How does voting work and what do certain amounts of votes mean?==
Overlapping segments of the same category don't get shown all at once, but instead compete with each other, appearing to users one at a time. The amount of votes determines how likely your submission is to be shown over the other ones. You can read more about the algorithm and grouping similar segments [https://blog.ajay.app/voting-and-pseudo-randomness-or-sponsorblock-or-youtube-sponsorship-segment-blocker here].

When a submission reaches the score of -2 or lower, it gets removed and will not appear anymore for users, but can still be found in the database. It also takes two votes to change the category of someone else's segment. If you downvote your own segment, it will be immediately removed and you won't lose any reputation.

If a segment's has a padlock next to it, it means it has been locked and will be prioritized over any other segment. [[VIP | VIPs']] segments are always locked, due to them being trusted.

==Are there any moderators?==
People with the [[VIP]] permission can moderate submissions. You can recognise them in Discord by their [[VIP]] tag. Learn more [[VIP | here]].

==Can I use SponsorBlock on platforms other than PC?==
Yes. Aside from the web browser extension, there are various third-party ports, including mobile. See the list [https://github.com/ajayyy/SponsorBlock/wiki/3rd-Party-Ports here].

==How can I transfer my Vanced userID to the desktop extension?==
Warning: You can only keep one userID, so decide if you want to keep the your extension userID or your Vanced userID. Keep a backup of your private userID in a secure location. If you want to transfer your extension user to Vanced, you will have to reverse the process.

To transfer your userID from Vanced to the extension:
*In Vanced click on your user icon -> settings -> SponsorBlock settings -> "your unique userID"
*Copy this string and save it somewhere
*In your browser, click on the SponsorBlock icon in your toolbar and click on options
*Scroll down to "Import/Export your UserID"
*Back up the current userID and save it somewhere safe in case you want to switch back to it
*Paste your userID there and confirm the changes
*Your userID is now transferred. The popup will show stats based on what you have submitted from Vanced.

Some data cannot be transfered, like segments you've skipped and time you saved others, because it is only saved anonymized.

== What is the mute option when submitting? ==
Normally a segment would just skip to the end. The [[Mute_Segment |mute segment]] will mute the video and play the segment. Once you have reached the end of the segment, the video will be unmuted.

==Can I create skip segments just for myself?==
Yes. If you wish to have skip segments for your personal use, not caring about the rules, just select the timestamps and close the editing box. Make sure not to click "submit". They will be stored locally in your browser and skipped automatically. You can also export them with your options.

== What is considered content?==
Content is any part of the video which someone could find valuable to watch. Finding something a waste of time personally does not mean that someone else wants to skip it.
==Is there any AI involved?==
[https://github.com/andrewzlee/NeuralBlock NeuralBlock] is a neural network that detects in-video YouTube sponsorships, though current implementation within SponsorBlock is limited to a moderation tool which detects incorrect sponsor segments on English videos. Every SponsorBlock segment you see on YouTube has been made by a human (as far as we know).