Right.
It would if done naievely; one seemingly-simple fix for all the problems I've seen in this thread: have multiple video versions as an explicit part of the API. You can link to a specific version, youtube can clearly show a flag saying "there's a newer version of this video available, do you want to watch that instead?", it can show comments and likes for all versions in one place (with a badge saying "this comment was made on an old version" if appropriate), etc
In the context we're talking about, do you believe the comments on video A (10 minutes of maths lecture with a typo in one of the digrams) would be hugely different from the comments on video B (10 minutes of maths lecture with that typo corrected); so much so that it's worth throwing out all the early comments and starting from scratch? Or are you thinking of some other use-case?
> I don’t want to additionally have to pay attention to whether we watched the same video or not.
Good news for you then! Making "video version number" part of the API means that you can filter those out programatically too :)
If it happens anyway, view counts could be disaggregated into "total" and "since last update".
I've seen a number of social network groups being sold for their audiences and then rebranded to sell questionable things. I've even seen something similar done to some YouTube channel I once subscribed to: its owner (new or not, can't really tell this time) changed its name/images/whatever, removed all the videos and started publishing things that I never wanted to be in my feed. Things will only get worse the moment YouTube allows to change videos under the same URL.
And if one's reaction is, "re-uploading a video should reset all views and likes to zero", then re-uploading now has little advantage over making a new video.
What's wrong with uploading a new video "Original Title [Update Nov 2018]", and linking to that in the description?