@Coaster It's a bit strange. In diaspora, the post itself gets sent to the sender's followers's pod(s) when the message is created. Posts are always served from the reader's pod. However, the images in the post remain on the sender's pod and are served from there.

This has some side effects, like messages don't go to new pods or pods that didn't have anyone following the sender at the time the message was sent; and if the sender's pod goes down the images are lost.

Solving the way messages move around in a federated network like Diaspora is one of the main challenges to the design of the system. ActivityPub chose some different options than Diaspora (and actually federation isn't in the ActivityPub spec). BlueSky does it completely differently.

There are tradeoffs to each one. For example, Bluesky doesn't permit non-public posts, but all posts are available to everyone all the time.

Thanks for the details. I'm not sure i understand about the images because all my images are shown even tho my original server is dead in the water, so they also must be saved on all the pods along with the posts.

Btw, I just made a PDF of my whole posting history from that dead pod. It's necessary to scroll through the posts and expand everything before saving for the PDF to show everything. I thought it was gone forever. At any rate, it's a relief to salvage it.

I wonder what the hell happened to diasporasocial? I even mailed the podmin and did not get a reply.

I’m concerned that something unfortunate has happened.

Me too.