@Gargron Earlier today around 12:00 UTC I did successfully fetch https://conf.tube/videos/watch/4102f53a-3f91-46c1-bb9b-fb954990f023 and comment on it. But around midnight UTC I tried to fetch the keynote and it failed with 403.
Has anyone of the publishers or peertube admins changed anything in that period? @mlemweb @rgggn @sl007
@Gargron It also worked for me back then, and now my instance has it cached anyways.
But if something had direct visibility at the first fetch attempt, that fact is cached (forever?) by Mastodon, correct?
Thanks for looking into it!
Right, this is my talk and it is one of only 3 videos showing up. Click here to check -> @apconf
Let me explain:
We collected all videos on peertube unlisted.
A new user thinks of this as "unfederated".
Then when all talks arrived we set them public.
A new user thinks, this means "federate public" but it did not.
Mine is a replacement talk for another one dropped out and so I published the 3 last ones directly public …
downside of republication: All links to the video (post-id) in posts her or on will break unless there are any redirects. But this will only become worse over time.
upside of republication: AP interaction, especially commenting, is an important part of this remote-federated #apconf. Only comments under the talk are discoverable.
My 2 cents: nuke it and republish 😥
The question with reupload was _before_ the workaround was found, I think it is fine as it is now.
@sl007 I'm against it. Especially the Spiritly Talk and the Talk about the isolation of Gab reached far beyond the conference audience!
Probably just unlist them and reupload them public? (ah and note it in the video description?) Than links won't break and all instances will federate.
@Gargron @schmittlauch @liaizon @mlemweb @rgggn @apconf @cwebber
I can't contribute anything to debugging, thank you all for your work on that. I agree with @eest9 that we shouldn't delete and re-upload, the videos have been shared too many times to go back and fix all of the links.
I propose that we update the descriptions on conf.tube with links to the SocialHub topics for each talk, and between that, the instances that have been fixed on mastodon, & #apconf2020 we'll be fine
@nicksellen Not sure if you are on tech duties for the instance instance.
Not a huge deal, but there was an issue with @apconf videos, thread here https://mastodon.social/@mastohost/104950285222324034
Anyhow if someone could run the command @ Gargron mentioned above, it would allow the APConf videos to appear in our timeline. Thx
@nicksellen Not sure if you are on tech duties for the instance this week.
Not a huge deal, but there was an issue with @ firstname.lastname@example.org videos, thread here https://mastodon.social/@mastohost/104950285222324034
Anyhow if someone could run the command @ Gargron mentioned above, it would allow ALL the APConf videos to appear in our timeline. Thx
@mewmew moderation interface -> accounts -> search for @.email@example.com user (without the dot) -> ban it -> unban it
@liaizon @sl007 @mlemweb @Gargron
Unfortunately it's likely not the only instance affected, and we cannot rely on every instance admin doing this.
It appears that this issue wasn't only present several days ago, but also just some hours ago – at least I do not know why my single-user instance should've tried fetching the keynote earlier than this evening where I manually triggered the fetch.
in no way meant political, bu t about
"be conservative in what you do [send over a protocol] but liberal in what you accept" :
So I wonder why peertube does federate it at all.
I would not expect that as it says "unlisted, only visible to people knowing the link" …
But I agree that "both sides need to investigate that." @schmittlauch
Yeah, a bit weird, sorry.
This is a privacy concern indeed or it needs to be made clear to the enduser with other captions and better labels!
Unlisted videos do federate by default - my understanding is that this is to be able to benefit from bandwidth offload? I didn't see a concrete use case for this, though.
However, as of v 2.3.0, there's an instance-level preference (federation.videos.federate_unlisted) that allows admins to prevent unlisted videos on their instance from federating, which is why the linked issue was closed.
It is fine in the sense that it is already public addressed and that also just deleting the instances cache might work.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!