I believe anything prior to that timestamp will not federate. New stuff should.
I run the midwest.social instance as well as the undernopretext.social mastodon instance
I believe anything prior to that timestamp will not federate. New stuff should.
Try select * from instance where domain = 'popular.instance';
and see the last time it was updated via the updated
column. I’ve been having to update that column with update instance set updated = now();
because once that timestamp becomes older than 3 days your instance assumes it’s “dead”.
and anti American
Based
In my case docker didn’t have a default max size that logs would stop at, so they just grew and grew exponentially. I also had the highest log level turned on to debug something so it was constantly logging a bunch of data.
Dark brandon strikes again!
Removed by mod
You have to install it manually, but it auto updates
I feel like the Fediverse is kinda immune to this because it’s not profit-driven and each instance can limit their user count to below the threshold for a lawsuit.
No problem! I had the same issue and was losing my mind trying to fix it. It still doesn’t update the timestamp like it should automatically so I’ve been doing it myself.