In case I'm running the server from the main branch, did I already get the fix or do I still need to update on July 6th?
@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.
@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.
You can fetch the follower count, you can fetch the people who participated in polls, but you can’t fetch likes & boost statistics as well as posts made in the past on another server?
Excuses! It’s easily possible. Even on a client basis.
I use @michael's #FediFetcher to do this. You can run it as a GitHub action, server, or desktop computer. Basically, set it up and forget about it. It chugs along backfilling new follows/followers, replies to posts, and more.
FediFetcher is a tool for Mastodon that automatically fetches missing replies and posts from other fediverse instances, and adds them to your own Mastodon instance. - nanos/FediFetcher
@apicultor @Mastodon It's crazy how bad this is being handled honestly
1. We have no indication of the severity
2. There is a two hour window where we're supposed to keep refreshing to see if the patch for what all we know is a 10.0 CVE score security issue
@Mastodon
Realize I am really ignorant of this stuff ... as a person on a Windows computer using Mastodon in a browser, do I need to do anything?
Can I also assume my android app will also auto-update like all other apps on my phone?
Did I mention that I'm ignorant on all aspect of this issue?
@TopKnot @Mastodon no, this is an announcement for instance administrators, they are the ones that need to update.
For us regular users this means that probably some hours after this our instance might have a bit of downtime while it is being updated, which will depend on your local administrator's time availability (keep in mind that most admins are volunteers with their own jobs and such, so the time can be away from office hours)
@arunshah240 @Mastodon direct message does exist as a privacy option for each message, alongside public, unlisted and followers-only.
Quote-posting isn't in plans for Mastodon, but exists in other compatible options, like Calckey, which some instances use.
You can already direct message people on Mastodon!
But I agree, it needs an WebRTC-esque chat that’s compatible with Pleroma, Akkoma, and all the other Fedi platforms that have already implemented it.