Things have been pretty broken today and the site is running incredibly slow in general. I'm struggling to navigate posts, and things have been awfully quiet which makes me think something with federation has stopped working with Lemmy again (I can see my comment from earlier today on Mastodon but not Lemmy).
there is indeed something weird going on with lemmy. i noticed some feeds from lemm.ee are down, and the logs from my instance are filling up with bot rejections from lemmy.world, ie they are blocking bot traffic. i thought i read something about the new version of lemmy breaking some inter-lemmy fed traffic.
the error messages piling up are bad for my 'bin instance due to the retry methods used... extra processing, disk space starts to fill up.. resources just start piling up so i'm having to manually dump things regularly for the last 24-36 hours.
feasible kbin.social is also having some of the same problems i am
things have been awfully quiet which makes me think something with federation has stopped working with Lemmy again
Things haven't been in sync for a day or two at least. Looking at a post from both kbin and lemmy (specifically startrek.website), there are times when not all of the posts are there, or there are comments missing, or the votes are just stuck. And this morning all/hot was almost completely static for hours.
There've been some stability issues with kbin.social for a couple days now. Been having trouble loading threads and even just voting on things sometimes doesn't work. Hopefully it gets resolved soon!
Have noticed that, too. Most haven't been consistent or repeatable enough to report, but these seemed like they were. Hopefully, Ernest has time to take a look at them soon enough.
Yeah. It started yesterday for me.
Read something, I think, on another thread about Ernest, the admin, being away with family for the holiday. Might be somewhat limited functionality for a little bit. But, he's been pretty on top of things over the last few months. I'm sure he'll get it sorted out when he gets back.
That's the default error text, it's been showing up for any downtime for a few months now. I think Ernest probably set that once for a server upgrade a while back and never changed it lol.