Hacker News new | ask | show | jobs
by mrtksn 1039 days ago
Technically, everyone pays for connecting to the network. I wouldn't say it's unethical to slam YouTube with full speed downloads but at the same time I wouldn't judge YouTube if they take measures against it.

I'm using a browser extension to show full size of images on social media when hover and Instagram went crazy about it, warning about unusual activities and threatening to lock my account. I looked into it to see if the extension does any scrapping behind but no, it all seems fine. My assumption is that Meta detects requests happening in wrong order which might indicate data scrapping due to the non-standart client behaviour.

So, measures and countermeasures. I guess it's up to YouTube to implement their counter measures and push the scrappers to implement theirs but overall at some point they should be able to limit downloading to the playback*2 speed because a legitimate consumption wouldn't happen any faster on a legitimate client.

But honestly, downloading shouldn't be restricted. The contents are protected by laws anyways and most people have legitimate reasons for downloading videos. It could be for archiving purposes because the video has some value for you, it could be for analysis or it could be about creating content based on the vide content(like downloading a movie trailer to extract parts for you movie review video). The content in YouTube is not created in vacuum and once published they create the new environment where new videos will be made and this creative freedom is important unless we want the current videos be the last videos ever made.

1 comments

> I'm using a browser extension to show full size of images on social media when hover and Instagram went crazy about it, warning about unusual activities and threatening to lock my account. I looked into it to see if the extension does any scrapping behind but no, it all seems fine.

I've used such an extension and found dragging the curser over your screen might fire like 25 requests. You might simply be rate-limited.

Maybe, I just speculate over the reason of course but I haven't noticed anything strange like that. That said, the pattern of requests from the client should be obvious to the backend, the preventive measures can be designed around it and the rate Is one of the obvious signals.

Removed the extension anyway