They will still be visible to federated instances as they have a local copy. But any new posts or comments will not federate.
this post was submitted on 04 Jun 2025
98 points (99.0% liked)
Fediverse
34234 readers
284 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)
founded 2 years ago
MODERATORS
And any new instance will not have a copy.
Ah that makes sense. So federation implies copying essentially, and not merely linking. Thanks!
For a practical test, search for kbin.social (and then ctrl+f for it also to get the direct results). Or, just look at a community: !kbinMeta@kbin.social
The only thing that appears missing is the ~~avatars~~ images. Though I assume the text content is doomed in the long-run when it comes to new instances, as I doubt re-federation (3rd-party federation) is a thing. Unless of course, someone manually crossposts said content.
I am in no way techy, but from what I gather because the posts are federated they are also stored on the other instances as well, so posts are still visible. In the post announcing the shuttering of .ee they specifically mentioned adding a note on your profile to link to your new profile, so people can find your new profile after that shut down. That implies to me that everything not intentionally scrubbed remains open/visible long after the shut down of the original source.
Again, though, not techy, so I may be vocalizing from my posterior
That's pretty much it.
Every instance that was subscribed to those communities will retain their local copy of the posts/comments and remain visible. You can even still comment on them, but only users on your instance will see them (i.e. without the home instance for the community being online, they won't federate beyond your local instance).
The only hiccup is image posts. Different instances have different configs for creating local thumbnails of images, and community icons/banners aren't cached, so it'll mostly be text-only copies of the content.
And any comments or posts to other communities by .ee users that have images hosted on.ee will be broken.
My guess is that the posts and comments will still be visible but if you click on a username or a post it'll just redirect you to an error page
Piefed has a community migration feature: https://piefed.social/post/667044
Basically, find the piefed.social copy of your community and then look for the 'move to piefed.social' link in the sidebar.
All the images disappear, since they are just links on remote instances.
A copy of all the accounts, comms, posts and comments stay on any instance around to recive them, but they are not fetchable.
When Yiffit shutdown, Wander archived everything. Though I am not sure how or where... But it kinda tells me that without manually doing something with it, it will probably be lost.
Then again, the other day someone had replied to a post on a community on Yiffit. Can't log in to the instance, or make new top level posts, but navigating directly to an old link still apparently works and you can reply and everything. 🤷🏻♂️
Can't log in to the instance, or make new top level posts,, but navigating directly to an old link still apparently works and you can reply and everything. 🤷🏻♂️
Keep in mind these are only visible to users of your instance.
oh good point (and not entirely obvious).