Anybody else having problems with commenting on #apconf2020 videos from Mastodon? When trying to fetch a video like https://conf.tube/videos/watch/6289920f-4e35-4141-ab6f-379b357849ec from Masto by URI, I get a 403 error.

/cc @rgggn @sl007

#apconf

@schmittlauch @rgggn@floss.social @sl007 It seems this video has been posted with what in Mastodon translates as direct visibility

@Gargron like a direct message? @rgggn @sl007

@schmittlauch @rgggn@floss.social @sl007 Yeah.

@schmittlauch @rgggn@floss.social @sl007 Current JSON representation on the origin seems to be public. I wonder if visibility on PeerTube videos is mutable and someone fetched the URL before it was made public? Mastodon does not support updates like that.

@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

@schmittlauch @mlemweb @rgggn@floss.social @sl007 That one works for me right now.

@Gargron @schmittlauch @mlemweb @rgggn@floss.social

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 …

@sl007 @Gargron @schmittlauch @mlemweb @rgggn @apconf oh shit, so there it no way to fix this I don't think other then reuploading them, that sucks

@liaizon No, the current state is fine. The issue appears when instances have already fetched them earlier and have them cached.
See https://toot.matereal.eu/@schmittlauch/104951275943026732 for a workaround @sl007 @Gargron @mlemweb @rgggn @apconf

@schmittlauch @liaizon @sl007 @mlemweb @rgggn@floss.social @apconf Wakest is right though the only reliable way to make them public on all places that might have them cached is re-posting them.

@schmittlauch @sl007 @mlemweb @rgggn @apconf

@Gargron can you delete the cache for mastodon.social specifically for conf.tube? would that work? since its probably the biggest instance that is currently messed up like this

@liaizon @schmittlauch @sl007 @mlemweb @rgggn@floss.social @apconf Done