Ummmm… this works amazingly well.

I generated an API key, and ran the docker command; that’s it… done, working perfectly.

I’ve never used sponsorblock before, but it’s hilarious how well this works. It’s like an aggressive jump cut 🤣 and the poor segue to the sponsor segment doesn’t even survive.

You may have misinterpreted what I said; I probably wasn’t clear enough.

If NSFW content isn’t available through a 3rd party app, I’m assuming that usage will fall (as the user looks elsewhere), hence less overall API requests.

I’m not trying to say that because the API responses won’t contain as many NSFW posts, it’ll save data or anything (still sending a full “page” of responses at a time).

Your point still stands however! If the user leaves the 3rd party app and goes straight to the 1st party app instead, yeah it’s a wash and they are serving the requests anyway.

The point of this is to:

• Reduce the number of API requests from whatever 3rd party apps are left; this reduces server load and costs.
• Coerce users into trying the 1st party app and tolerating it so they can watch NSFW content. This may cause some users to abandon the 3rd party app and just settle for the 1st party app.

I doubt it has much to do with advertising.