>It seems that a lot of users will upload video which is by default published [and then they change it to private] //
So to avoid that sort of unexpected public-ing (ie publishing) only one extra scrape would be needed. Or, if they knew the period over which the setting was normally changed then they could just delay the scrape until most would have already been changed.
I imagine though, in part, the 'fun' is catching inadvertent publication and morality is no t considered.
It actually has nothing to do with "fun". As I mentioned in my other comment, we don't expose our database publicly and nobody but us can see that a video is unlisted.
It would beat the purpose of our service would we delay our identification, and it would actually require some significant engineering efforts in order to introduce such capabilities into our system with significant economical impact on our business.
>It seems that a lot of users will upload video which is by default published [and then they change it to private] //
So to avoid that sort of unexpected public-ing (ie publishing) only one extra scrape would be needed. Or, if they knew the period over which the setting was normally changed then they could just delay the scrape until most would have already been changed.
I imagine though, in part, the 'fun' is catching inadvertent publication and morality is no t considered.