tested commenting across instances on one of the conf.tube videos to figure out what the current state of affairs are
image 1: my single user #mastodon instance
image 2: mastodon.social after cache has been cleared by @Gargron
image 3: https://conf.tube #peertube instance
https://conf.tube/videos/watch/bf1309c1-0f5e-4fa1-9b58-fc240f369684;threadId=646
@liaizon on your single user instance are you following the account and if so was it before the video was even posted? Because it looks like your instance just hasn't fetched any apconf content because it didn't know about it. Whereas for social almost certainly already had a subscriber and so knew about the content and so could render it
@darius seems you missed the drama. if you want to have context here is the thread
@liaizon ohhh. Yeah I know exactly that problem. I had to change the federation model of my rss converter when I realized it was doing that with posts.
Some additional context here
https://mastodon.technology/@Argus/104938685784717422
But the fact that many people came together this night to work on solutions means more to me than the drama itself ;)
Instance admins can do
Account.find_remote('apconf', 'conf.tube').statuses.where(visibility: :direct).each { |s| RemoveStatusService.new.call(s) }
Thank you, everybody :
cc @rgggn !
Just btw: Inventing you to watch my talk https://conf.tube/videos/watch/4102f53a-3f91-46c1-bb9b-fb954990f023
(replacement for one that dropped out)
It was recorded after the issue appeared but off course before uploading it ;)
Trying to describe the mastodon peertube problem from the perspective of a user new to the fediverse.