I run the midwest.social instance as well as the undernopretext.social mastodon instance
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.
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”.
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.
2 cats really isn’t too different than one cat. I mean, yeah, you’ll pay for another vet bill from time to time but it’s usually not that big a deal. If you can afford it I’d say go for it.
Source: have 3 cats