-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Non-federated remote live does not start #6111
Comments
Hello, When you fetch a remote video, you don't subscribe to the account/channel/instance and so the origin instance doesn't send related video events like |
That's what i thought... Maybe just fetch again the remote data on window reload? So that if the user just make f5, the live will start. Or maybe is it possible to just subscribe to a single video throught AP? |
No it's not possible as you can only subscribe to actors in AP |
@Chocobozzz , Is think i have a related bug with Peertube v6.2.0-RC1. On my freshly updated instance, on the "recent video" page, i have a live started 2 month ago: https://videos.john-livingston.fr/videos/recently-added If i remember well, I opened this live by seaching its url in the search bar. My instance was not federating with the original instance when the live occured. Here is the link to the live on my instance: For the record, i followed the instance starting at june the 9th (but the live was before, in april): |
I'm not sure it's related, the live is also broken on the origin instance: https://videos.john-livingston.fr/w/6ZnQrdr4jwT6RT9E8nCofZ |
Oh yes, you are right. I did not notice the other day. I'm closing this issue. |
Describe the current behavior
If i open a remote live on my instance, by copy-pasting the url: the video won't start when the live begins.
Steps to reproduce
The video stay marked as "non started", event if the live started.
I manage to fix this by adding a like to the video, then refreshing the page.
Describe the expected behavior
Live should start at some point.
Additional information
PeerTube instance:
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/
):The text was updated successfully, but these errors were encountered: