-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
History Import Timestamps (import date, vs watched date) #13
Comments
Thank you for bringing this up! When synchronizing with the browser history, it will use the time at which you have last visited the page of the video according to your browser. When synchronizing with the Youtube history, it will use the current time for newly discovered videos. There unfortunately no easy solution to using the actual timestamp when syncing with the Youtube history since this is information that they do not expose. I am hence closing this issue for now but will post an update in case I ever find a better solution. |
Isn't that information visible (and thus parsable) when vising the 'history' page on YouTube.com? I do see it listed above each group of videos. |
But that categorization is only on a per-day basis, so it is not sufficient to pinpoint the actual time when a video has been watched. |
True. But still significantly more informative than having no idea when it was viewed at all ;) |
Are the categories consistent though? Or does it switch to "last month" or "last year" once you go back sufficiently far? It is also a little tedious to implement this so I am afraid that I am holding off from implementing it based on incomplete information. |
The naming convention is well-defined. There are exactly 4 formats, so 4 pattern matches needed: The other reason this would be much better is because, as I understand it, it would cause multiple PCs to have consistent histories. As it is currently implemented, importing from 2 different PCs would cause them to have different histories (because each would show the watch date whenever that PC happened to sync last). If it was based on the parsed info actually shown, they would always be the same, regardless of when that PC last imported. |
That is good to know, but I am afraid that I am unfortunately unable to invest my spare time into adding this feature at the moment, my apologies. I would be happy to review a pull request that adds this feature though. |
Understood. I've never seen even a line of browser addon code, so I'm afraid it would require some studying on my part too, which I'm unfortunately not in place to do at this particular moment. Still, I'd propose not closing this issue, as it's not actually solved, & perhaps one of us (or someone else looking at these issues in the future) might come along & agree with the idea ;) |
Fair enough, reopening. Anyone who wants to give it a shot, the part that would need to be updated is quoted below. youtube-watchmarker/background.js Lines 624 to 685 in 1c79ffd
|
When first installing this extension & importing previous watch history, it seems to set the watch timestamps to the current time (aka the import time), rather than the actual watch time.
The text was updated successfully, but these errors were encountered: