Mastodon⚠️ We are planning to release important security fixes for #Mastodon on July 6th, between 13:00 and 15:00 UTC. They will be available for the 4.1, 4.0 and 3.5 versions as well as a nightly release, to make the upgrade as small and painless for everyone as possible. Be ready to upgrade!
Nie 🏳️🌈 
@Mastodon Is it available to change this? It will improve comfort of using mastodon
Aranjedeath@Nie_6969 @Mastodon part of the problem is here, you can subscribe to this bug for updates: https://github.com/mastodon/mastodon/issues/34
Benjamin@Aranjedeath @Nie_6969 @Mastodon That may be a different issue. When following a user who hasn’t been seen by the server before you’ll typically only see their posts from that point onward, their profile won’t show the posts from before you followed them (the server discovered them).
Whereas that message refers to a user who has migrated and since posts currently cannot be migrated (natively) and so they direct you to the original profile/server to see those posts.
@BenjaminNelan thank you for differentiating, I did know that when I posted (contained within the phrase "part of the problem"). Once you have the software and operational infrastructure to backfill posts... It is not hard to add additional situations where you do so.
@Aranjedeath I agree that it could be done this way and I would prefer it than the current system.
Though may affect how those backfilled posts could be interacted/distributed. Backfill = cache linking to existing ActivityPub objects. In the case of a migrated account where the remote server no longer exists you effectively have zombie posts.
@Aranjedeath Having said that - I just did an experiment with my self-hosted server where I cached old posts from my old account then edited the database to change the owner to the migrated user's new account and... it works just fine...
No idea if there's side effects of doing this, about to try it on a post that has replies. I definitely thought there was more going on under the hood though.