Yes, that is adding controls and using a database from the SponsorBlock server.
What I mean is a plugin cannot see the video. Like you can’t write
if(screen == adScreen) {
then skipToNextSegment();
}
The plugin isn’t reading the video, it is getting info from a database. For AI or machine learning to work ad injection, which might change for every user, doing what SponsorBlock is doing is not enough.
Looking online at similar situations people had their membership canceled by management. Other cases showed bring able to enter by a phone number, by their old tag, or ID verification. Looks like it happened for people whose app kept on crashing or a work phone that wouldn’t allow installs.
Which gym would just keep charging you if you said you can’t get in?
Thanks for this.
When Google said they were stopping 3rd party cookies, I thought it was just a simple security setting. The new system, Protected Audience, seems like 3rd party cookies without the whack-a-mole approach of listing every cookie advertisers can take, especially since there is nothing stopping data collectors from extracting data from it, like what Mozilla said in the article.
Hopefully there are fake data dumpers or cleaners for Protected Audience which would reduce the effectiveness of this system but looking how the Chrome team treats browser extensions, I doubt it.
This doesn’t differentiate different types of English but I will post it any just in case it is useful to you.
Losing privacy for convenience has been happening. We use GPS on our smart phones for better directions. We install listening devices to add things to shopping carts and to play music by voice. We install cloud security cameras at home. We accept free WiFi in stores which gives them our cell phone info and our location. We use digital cash instead of physical cash. We buy things online rather than going to the store. Every device, like a toaster, has a MAC address.