You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an account on social.wxcafe.net (version 2.2.0) and I'm following a locked account on mastodon.social (version 2.2.0) but the followers-only (pre-follow) toots from the locked account remain invisible to me.
The locked account was created more than 10 months ago.
A locked account on yet an other instance (version 2.2.0), created a month ago does not have this problem however.
I searched or browsed the repo’s other issues to ensure this is not a duplicate.
(there si probably a duplicate but I can't find it)
The text was updated successfully, but these errors were encountered:
Yes, this is part of how mastodon works. If your instance never got the private toots when they were made (because noone on your server was following this person) then they won't get them later
It's a shame. Can you point me to any (protocol) documentation that states this and that won't be fixed ?
I mean, it breaks the principal of federation if creating a new server means everything is half broken. It just encourages people to stay centralized. I mean this is really bad.
@jpdeplaix nothing is "half broken". You'll just see new private posts. It hasn't, so far, encouraged anybody to "stay centralized"
backfilling private and public posts would be technically possible, it's not a protocol limitation, it's just not something mastodon does currently. #34 is the root ticket for this possible improvement.
I have an account on social.wxcafe.net (version 2.2.0) and I'm following a locked account on mastodon.social (version 2.2.0) but the followers-only (pre-follow) toots from the locked account remain invisible to me.
The locked account was created more than 10 months ago.
A locked account on yet an other instance (version 2.2.0), created a month ago does not have this problem however.
(there si probably a duplicate but I can't find it)
The text was updated successfully, but these errors were encountered: