Yes, that might actually be the activitypub table in the database. You can safely delete older entries, like from two weeks ago or older. Otherwise it just keeps growing with the logs of all activitypub objects that the server has sent out received.

Thanks for the transparency! I don't mind, mistakes happen, but I understand it's frustrating and a bit problematic with the lost content.

There was a post about that on a Lemmy admin community a few days ago. Someone with a ~1k userbase was eating up a GB/day on average. IIRC, there were lots of logs, but also if I understand correctly, every server stores mirrors of the data from anything users subscribe to. That could eat up a lot of data pretty quickly as the fedeverse scales up.

If you wanted to suggest a shift for improved scalability, maybe servers could form tight pacts with a few who mirror each other's content, and then more loosely federated servers load data directly from the pact. A compromise between ultimate content preservation and every larger server having to host the entire fedeverse.

So basically, a few servers would form a union. Each union would be a smaller fedeverse (like cells in an organ), and they'd connect to other organs to form the fedeverse/body.

Also, are users who joined in the past few days affected? I suppose they might need to sign up again.