I don’t know whether that’s because someone has to subscribe before posts are made for them to propagate (I was apparently the first subscriber to the new community on lemmy.today), or whether they’ll propagate after someone subscribes and it just takes time for the posts to move over, or whether there’s some sort of problem.
EDIT: Also, given that the community is now hosted on PieFed, maybe the sidebar description should be updated from “Welcome to Internet is Beautiful Lemmy and Mbin community.” to “Welcome to Internet is Beautiful Lemmy/Mbin/PieFed community.” or similar :-)
EDIT2: Two days later, old posts are visible, so it looks like it just takes a while to propagate.
My understanding is that this “replicate a community with old posts on another instance” is some feature that was added to PieFed that I assume that @sag@lemm.ee used.
It has an image. The submitting user uploaded it to lemmy.ml’s pict-rs instance (which is what happens on your home instance when you use the “upload image” button).
That was potentially a problem for users on lemm.ee, because when they upload images, they upload the images to the lemm.ee pict-rs instance, and when lemm.ee goes down, the images will stop being available.
However, as you can see, here’s the PieFed version of the post:
And the image there is hosted on media.piefed.social. That is, this PieFed community migration feature will apparently preserve a copy of anything that lemm.ee users have posted to this community.
Still going to be a problem if lemm.ee users have posted images to other communities (say, for example, !AskLemmy@lemmy.world), since when lemm.ee goes down, those images will become inaccessible, but at least it means that this community will retain content.
Does mean that PieFed’s community migration might consume a lot of disk space on the PieFed instance, though…
Looks like it’s !InternetIsBeautiful@piefed.social
Note that there are posts visible on piefed.social’s view of the community; it looks like posts from the original community were migrated:
https://piefed.social/c/internetisbeautiful
However, I don’t currently see posts there on lemmy.today’s view of the community:
https://lemmy.today/c/internetisbeautiful@piefed.social
I don’t know whether that’s because someone has to subscribe before posts are made for them to propagate (I was apparently the first subscriber to the new community on lemmy.today), or whether they’ll propagate after someone subscribes and it just takes time for the posts to move over, or whether there’s some sort of problem.
EDIT: Also, given that the community is now hosted on PieFed, maybe the sidebar description should be updated from “Welcome to Internet is Beautiful Lemmy and Mbin community.” to “Welcome to Internet is Beautiful Lemmy/Mbin/PieFed community.” or similar :-)
EDIT2: Two days later, old posts are visible, so it looks like it just takes a while to propagate.
Interesting. Let’s see if it federates, I didn’t expect a backup of posts anyway!
My understanding is that this “replicate a community with old posts on another instance” is some feature that was added to PieFed that I assume that @sag@lemm.ee used.
https://piefed.social/post/667045
EDIT: Oh, awesome! It looks like this feature also replicates the pict-rs-hosted images.
So, for example, take this post:
https://lemmy.today/post/30543446
It has an image. The submitting user uploaded it to lemmy.ml’s pict-rs instance (which is what happens on your home instance when you use the “upload image” button).
That was potentially a problem for users on lemm.ee, because when they upload images, they upload the images to the lemm.ee pict-rs instance, and when lemm.ee goes down, the images will stop being available.
However, as you can see, here’s the PieFed version of the post:
https://piefed.social/post/805357
And the image there is hosted on media.piefed.social. That is, this PieFed community migration feature will apparently preserve a copy of anything that lemm.ee users have posted to this community.
Still going to be a problem if lemm.ee users have posted images to other communities (say, for example, !AskLemmy@lemmy.world), since when lemm.ee goes down, those images will become inaccessible, but at least it means that this community will retain content.
Does mean that PieFed’s community migration might consume a lot of disk space on the PieFed instance, though…