I’m pretty confident that you are wrong.
I’m pretty confident that you are wrong.
Invidious and YouTube piped (and LibreTube) by default load the videos server-side, as opposed to GrayJay, NewPipe or Smarttube.
It has advantages (mostly that your IP address is not shared with YouTube, and it allows users from countries where YouTube is blocked to still access it) and inconvenients (much harder to keep up when YouTube actively seeks to block them).
LibreTube is also a good one. Basically an app for piped
Browsers based on chromium do not have to follow exactly what the main branch is doing. If they want to keep supporting MV2 or support different rules for MV3, they can. Albeit it’s a bit cumbersome.
It would be crazy expensive to run an attack of this size for years.
There is no way a DDoS on the website in affecting the crawler. Also, running a DDoS attack of this size costs a lot of money (if you rent the network, if you own it it costs money as lost sales). No one is giving AI control over a DDoS network to just fuck around.
There is no domain name associated with the IPs.
Most importantly, usually, DDoS attacks use infected devices (PCs, mobile phones, smart fridges, shady browser addons etc…) to get many ip addresses and devices/locations and attack from everywhere at once.
That’s wrong. Youtube dislike has its own database, and infers the bumber of dislikes based on the number of dislike it got and its userbase.
The plug-in stopped working because youtube changed its layout. It’s coming back.
I think you meant this one: https://m.youtube.com/watch?v=8JrqH2oOTK4
I use TrackerControl. It doesn’t block ads in browsers, however, so I use Firefox and ublock origin there.
Fair enough, that’s interesting. I assume this only applies to the non-web clients. On the web, it would not be possible. You can verify by looking at the outgoing network requests on this random video for example: https://invidious.privacyredirect.com/watch?v=qKMcKQCQxxI