On a long video, we may watch it in several times. It might be worth to resume it automatically, and display a small loading bar below the video miniature (to see when we previously stopped the video).
The only thing I'm unsure: do we store this information on the server (for logged users) or in the local storage?
Server
Cons: privacy -> admin instances could know what videos their user have watched
Pro: We can resume a video we watched on our mobile device or on another computer
Local storage
Cons: We can't resume a video we watched on another device/web browser
Pro: Would be available for all users, not only logged in
Maybe we could add a checkbox in user preferences, but I would like to keep it as simple as possible.
Local will be difficult to do because we can watch the same video on more than one instance.
@DavidLibeau Even if we choose the server option, we cannot cross federation and store data in your origin instance. You'll have to "learn" to stay on the instance you registered on :)
(Or a browser extension might provide such feature).
Server side can be useful for later, to make stats about what a viewer watched or not.
Theses data can be erased after few days.
Cons: privacy
wouldn't it be trivial to figure out what videos users have watched anyway, by looking at the webtorrent connections?
Or like.... the list of pages requested in your web server logs.
wouldn't it be trivial to figure out what videos users have watched anyway, by looking at the webtorrent connections?
If you're the admin, in theory you can hack peertube to see what IPs has announced which video file, and save this data somewhere, but you won't really be able to know how long and if the user watched the video.
Or like.... the list of pages requested in your web server logs
Yes, if you enable nginx byte range requests logging, you might be able to know what IPs has consumed which video file, but it would be more difficult than just executing a SELECT in a SQL table. Moreover, it's not because the IP downloaded the data that they watched it while with this feature the admin would know at what timestamp the user stopped the video.
But these are interesting arguments, thank you!
Let's implement this on server side, with a button to clear the history.
@Chocobozzz is this just a notification about the time point I last stopped watching the video, or is it automatically resuming?
Both solutions are good, but for music for example, it would be better to not resume the video but just name the time point of the last time I was on this video
is this just a notification about the time point I last stopped watching the video, or is it automatically resuming?
It is automatically resumed
I think the resume information should expire at some point, after a day or so, don't you ?
I think the resume information should expire at some point, after a day or so, don't you ?
no, I hate when it isn't remember I saw a video event if one year old.
and you can do it on the database with a sexy cron
Most helpful comment
Let's implement this on server side, with a button to clear the history.