Peertube: Allow uploading a new version of a video

[12people]

I've been wanting to create videos summarizing certain topics that are continually updated as more news on the topic comes in. This is unusual for videos, as Youtube has never allowed such a thing, but common for blog posts.

I would really appreciate an "Upload new version" feature, which would replace the video in question with another video, maintaining the same link and the same comments. Older versions could be archived and available from a screen listing previous versions.

[Krafting]

good idea!

[dedesite]

+1. I've got this problem with Youtube also. For example, I uploaded a video, then share it with a link and then realize that I forgot something or that something was wrong in the "cut" etc. On youtube, you need to upload a new video and share the new link, which is a shame for "marketing".

[Chocobozzz]

Video file updates are generally not allowed because there can be abused: for example a viral cat video can be replaced with some kind of propaganda etc. We could however add the ability to specify a link to the new version of the video, so users are redirected with a confirm modal: A new version of this video is available, would you like to watch it? or something like that.

[dedesite]

Video file updates are generally not allowed because there can be abuses: for example a viral cat video can be replaced with some kind of propaganda etc.

Oh, I never though about that ! That's kind of a problem indeed.

We could however add the ability to specify a link to the new version of the video, so users are redirected with a confirm modal: _A new version of this video is available, would you like to watch it?_ or something like that.

It seems to be a great idea :D

[12people]

@Chocobozzz

The downside I see with a redirect dialog is that, by submitting a new version, you suddenly lose all conversations under a video as well as all ratings. The uploader then has to make a choice whether correcting a simple fact in a video or adding new content as an update on a situation is worth losing all of that.

I agree that there is potential for abuse. The way that social networks have dealt with this is by adding an "Edited" date to the post. The way blog posts often deal with this is by prefacing content with details on what was changed and how.

I think that, if it was clearly stated under the video when the latest version was uploaded, and older versions of the video were still accessible from an "Older versions" page, that would go a long way toward curbing abuse

Along with that, instance admins could have a rule against uploading new versions that vastly differ from the original, and abuse of that rule could be treated the same way as rules against spam, porn, and offensive content. As older versions would be publicly accessible, anyone could report abuse.

[therahedwig]

Perhaps you could send a notification to users who liked and did other things to the video(like adding to a playlist, commenting) whenever the video updates. Maybe have a user config option that if they'd like every update will invalidate the actions they did with it(might need some coordination with other Fediverse software). This is mostly necessary for likes and playlists, comments might do with 'this was for an older version of the video' added to them...

For embedded things, what you could do is that an embedded video will try to point at the version that is at the moment of embedding the last, and that getting the latest version always will explicitely require using a specific url or option or something. That way embeds that are pointing at a viral cat video will keep pointing to the cat video and not to the update with questionable content, while embeds that the embedder explicitely wanted to point at the last version(like the creator's blog) will use the last possible version.

Maybe take a look at how other Fediverse stuff implements updates. Like, Mastodon doesn't, but I recall others do handle updates.

[silvernode]

Maybe there can be multiple additional uploads to a single video page that you can add on later. They just autoplay in sequence of the upload date to make 1 stream of content. This will make it seem like one long video when actually it's several. The seamless connection is all on the video editor to make everything flow.

[lsde]

While I understand concerns regading video authenticity, there should be a method for an admin to replace a video though.. Maybe just a script to do it manualy?

From my poking around it should be something like:

• manually create a new torrent and infoHash from a new file as per:
  https://github.com/Chocobozzz/PeerTube/blob/29d4e1375fdac88595347184c3d1b214804794b0/server/models/video/video.ts#L1816
• update "videoFile" set infoHash="blabla" where "videoId"=5537; (also other fields if necessary)
• replace an original file with a new version in data/videos

Im I right or is something missing? @Chocobozzz
thx

[Chocobozzz]

@lsde Admins can already do it: https://github.com/Chocobozzz/PeerTube/blob/develop/support/doc/tools.md#create-import-video-file-jobjs

[lsde]

Aha! thx @Chocobozzz
btw, is there a way how to programatically remove a resolution?
say I decided to replace lowres versions with highres ones with better encoding params, so they are smaller. therefore no reason to keep the lowres.

[fflorent]

@lsde Admins can already do it: https://github.com/Chocobozzz/PeerTube/blob/develop/support/doc/tools.md#create-import-video-file-jobjs

@Chocobozzz It doesn't seem to work anymore. Should I create a dedicated issue?

[Chocobozzz]

Yes please with server logs, job logs, CLI options and video mode (HLS or not?)

[fflorent]

My issue is now fixed, the new video file replaced the old one.

As I use Docker, might be fixed thanks to https://github.com/Chocobozzz/PeerTube/issues/2613

[hexydes]

You could make this an administrator option. For example, I might want to run a community with limited creators where there is a lot of moderation of the content (and user uploads turned off by default). In this case, it might be a HUGE draw to getting creators on the instance over YouTube, where replacing your video is basically a death-sentence for traffic.

Definitely understand the potential for abuse, and on a wide-open instance it's a terrible idea. But I can definitely present a case where it'd be a huge benefit and attraction point over YouTube.