@schmittlauch Can we do this? @leah & @rixx ?

@eest9 @schmittlauch @leah Which video is giving you problems? I just posted test comments on one of them and it worked just fine.

@rixx @eest9 @schmittlauch and I don't see how the command should fix that. What was the initial problem at all? Did someone renamed an existing account or....?

@leah @rixx @eest9 Has this progressed and been resolved?
Example video is https://conf.tube/videos/watch/6289920f-4e35-4141-ab6f-379b357849ec

Background: When uploaded initially, the videos were posted with a DM-like visibility but without anyone on your instance being allowed to see them. For whatever reason, this Publish activity was still sent to all follower instances like chaos.social.
Mastodon now has this visible-to-noone property cached and does not support mutable updates.

@leah @rixx @eest9
The command above is supposed to delete all direct-visible posts so they can be re-fetched with their public visibility they have right now.

@schmittlauch @rixx @eest9 may I ask why every instance admin should now update their database instead of reuploading the stuff with the right permissions on your side? Sounds like the much easier way to me.

@leah @rixx @eest9 That has been considered, but unfortunately the links had been already spread outside the Fediverse e.g. at Hacker News and stuff.
It's a complicated decision to make, the organisers (which I am not part of) decided to leave things as they are and providing an additional forum as backup.

I guess nobody expects all instance admins to jump and do that just by themselves. We can just ask our own admins for this favor, acknowledging the extra amount of work this causes and
->

@leah @rixx @eest9 try to prevent such problems in the future.

@leah @rixx @eest9 The most simple way is to just ban and unban the @.apconf@conf.tube user, that'd take ~ 1 minute of work.

(Claiming that downstream instance admins shouldn't have to handle this is still a valid opinion of course)