It was owner/operator activity today over at midwest.social instance that had me digging around on the ‘activity’ table. reference: https://midwest.social/post/369505

You will also see users of that instance reporting Lemmy site failures/errors in comments on that posting.

If indeed it is mainly used for debugging, it might make sense to have a parameter to not write data to it at all. In cases of cloud computing where database storage is limited and/or resources cycles of storage I/O or CPU load by PostgreSQL, turning off activity table logging in the code could save some site operators money and fit on smaller systems.