Peertube doesn't federate Update when video reach is changed from "Unlisted" to "Public" #6441

New issue

Open

opened 2026-02-22 12:54:57 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-22 12:54:57 -05:00

Owner

Originally created by @Nicthurne on GitHub (Feb 1, 2026).

Describe the current behavior

If a video has been set to "unlisted" and instances in the fediverse know about this video, they will respect the setting. However, if this video then gets set to "public" afterwards, these instances do not receive an update and therefore still believe that the video is "unlisted".
See this Mastodon conversation.
This is not ideal, as it is not intuitive to Peertube users. Ideally, an update activity should be federated to let instances know that the visibility has been updated.

Steps to reproduce

Publish a video, initially set to public or unlisted, and wait for a remote fediverse instance to fetch it
Set the video to "unlisted"
Set the video to "public"

Describe the expected behavior

Expected would be for remote instances to know that the video has been changed from "unlisted" to "public", and therefore show it to everyone.

Additional information

PeerTube instance: https://peertube.wtf/
- URL: https://peertube.wtf/
- Version: 8.0.1
- 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/):

Originally created by @Nicthurne on GitHub (Feb 1, 2026). ### Describe the current behavior If a video has been set to "unlisted" and instances in the fediverse know about this video, they will respect the setting. However, if this video then gets set to "public" afterwards, these instances do not receive an update and therefore still believe that the video is "unlisted". See [this Mastodon conversation](https://toot.matereal.eu/@schmittlauch/104951296471912007). This is not ideal, as it is not intuitive to Peertube users. Ideally, an update activity should be federated to let instances know that the visibility has been updated. ### Steps to reproduce 1. Publish a video, initially set to public or unlisted, and wait for a remote fediverse instance to fetch it 2. Set the video to "unlisted" 3. Set the video to "public" ### Describe the expected behavior Expected would be for remote instances to know that the video has been changed from "unlisted" to "public", and therefore show it to everyone. ### Additional information * PeerTube instance: https://peertube.wtf/ * URL: https://peertube.wtf/ * Version: 8.0.1 * 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/`):

deekerman added the

Status: Waiting for answer

label

2026-02-22 12:54:57 -05:00

deekerman commented

2026-02-22 12:55:09 -05:00

Author

Owner

@Chocobozzz commented on GitHub (Feb 16, 2026):

Hello,

Please see https://github.com/Chocobozzz/PeerTube/issues/7175#issuecomment-3144879868

these instances do not receive an update and therefore still believe that the video is "unlisted".

Did you check logs and instance jobs to ensure it doesn't send the Create/Update activity when the video is not unlisted anymore?

@Chocobozzz commented on GitHub (Feb 16, 2026): Hello, Please see https://github.com/Chocobozzz/PeerTube/issues/7175#issuecomment-3144879868 > these instances do not receive an update and therefore still believe that the video is "unlisted". Did you check logs and instance jobs to ensure it doesn't send the `Create`/`Update` activity when the video is not unlisted anymore?