Support adding custom video privacy

[kontrollanten]

Describe the current behavior

No response

Steps to reproduce

1. Create a plugin with a custom video privacy: videoPrivacyManager.addConstant(544, 'Super secret')
2. Apply the privacy to a video
3. Fetch the video
4. See a HTTP 500 with error Unknown video privacy 544 to know if the video requires auth

Describe the expected behavior

Extend the video privacy API like:

videoPrivacyManager.addPrivacy(544, 'Super secret', (user, video) => {
  if (user.id === 1) return true;

  return false;
})

Or a solution that would fit our case much better:

videoPrivacyManager.addPrivacy(544, 'Super secret', (user, video) => {
  if (user.id === 1) return video;

  const replacementVideo = peertubeHelpers.videos.loadByUrl(FIXED_URL_TO_A_REPLACEMENT_VIDEO);

  return replacementVideo;
})

In the latter case the plugin author can choose to return another video, but I assume this won't fit into the current structure. The same functionality would be possible to solve by using a filter hook.

Additional information

• PeerTube instance:

  • URL:
  • Version: 6.0.3
  • NodeJS version:
  • Ffmpeg version:

• Browser name, version and platforms on which you could reproduce the bug:

• Link to browser console log if relevant:

• Link to server log if relevant (journalctl or /var/www/peertube/storage/logs/):