Skip YouTube video sponsors (server side portion)
Find a file
2020-03-20 20:14:20 +00:00
databases Added indexes and mmap to the private db 2020-03-04 15:17:50 -05:00
src added request debug log without condition 2020-03-20 20:14:20 +00:00
.gitignore Updated gitignore 2019-12-29 00:24:51 -05:00
config.json.example Added first time submission notifications for discord. 2019-12-28 00:29:14 -05:00
index.js added request debug log without condition 2020-03-20 20:14:20 +00:00
LICENSE Create LICENSE 2019-08-19 20:59:10 -04:00
package-lock.json Switched to better sqlite 2020-01-24 21:37:16 -05:00
package.json Switched to better sqlite 2020-01-24 21:37:16 -05:00
README.MD Update README.MD 2020-02-25 22:16:22 -05:00

SponsorBlock Server

SponsorBlock is an extension that will skip over sponsored segments of YouTube videos. SponsorBlock is a crowdsourced browser extension that let's anyone submit the start and end time's of sponsored segments of YouTube videos. Once one person submits this information, everyone else with this extension will skip right over the sponsored segment.

This is the server backend for it

Server

This is a simple Sqlite database that will hold all the timing data.

To make sure that this project doesn't die, I have made the database publicly downloadable at https://api.sponsor.ajay.app/database.db (formerly https://sponsor.ajay.app/database.db). You can download a backup or get archive.org to take a backup if you do desire. The database is under this license unless you get explicit permission from me.

Hopefully this project can be combined with projects like this and use this data to create a neural network to predict when sponsored segments happen. That project is sadly abandoned now, so I have decided to attempt to revive this idea.

Client

The client web browser extension is available here: https://github.com/ajayyy/SponsorBlock

Build Yourself

This is a node.js server, so clone this repo and run npm install to install all dependencies.

Make sure to create the databases in the databases folder out of the database schemas.

Rename config.json.example to config.json and fill the parameters inside. Make sure to remove the comments as comments are not supported in JSON.

Run the server with npm start.

API Docs

Available here