4 ms·
Can’t they just fingerprint the incoming requests based on a litany of variables such as headers ip etc to prevent this “scraping”? Sorry I don’t follow
by moneywoes 3y ago
Can’t they just fingerprint the incoming requests based on a litany of variables such as headers ip etc to prevent this “scraping”?
Sorry I don’t follow
- matheusmoreira 3y agoSure. We can also control those variables. Youtube-dl has a small javascript interpreter to figure out the audio and video URLs that YouTube generates for every client. In this thread it was also pointed out that people can use headless chrome. It's simple. If they allow public access to their site at all, there's pretty much nothing they can do to stop any of this.