Going to https://lemmy.ml/c/usmlr gives a 404, but https://lemmy.ml/c/usmlr@lemmy.ml works.
There's also quite a bit of lag in federation, with most other instances not even having the last changes I made to the description. Only lemmy.world does, but I also moderated and post in the community from that instance, so that may be why.
- https://lemmy.world/c/usmlr@lemmy.ml/data_type/Post/sort/New/page/1
- https://beehaw.org/c/usmlr@lemmy.ml/data_type/Post/sort/New/page/1
- https://lemmy.one/c/usmlr@lemmy.ml/data_type/Post/sort/New/page/1
- https://sh.itjust.works/c/usmlr@lemmy.ml
- https://kbin.social/m/usmlr@lemmy.ml/newest
I would assume beehaw simply won't receive the posts I make from my lemmy.world account, because defederation.
9 Comments
theory@feddit.uk · 4 pts · 3y
Its a bug
baronvonj@lemmy.ml · 3 pts · 3y
Any idea what it is about the community that is triggering the bug? I see other communities are working just fine.
theory@feddit.uk · 4 pts · 3y
If im correctly informed, its to do with remote moderators. Reality is it's just that the DB has hot itself into a screwed up state, i think they have a fix for it in the next version
CosmicSploogeDrizzle@lemmy.world · 2 pts · 3y
It's the remote moderator bug. Should be fixed in 0.18
https://github.com/LemmyNet/lemmy/issues/3075
baronvonj@lemmy.ml · 0 pts · 3y
fantastic, thanks. I don't think I ever would have found that myself. Doesn't appear to be the case that the automatic DB check is in v0.18 though, as it still fails on https://enterprise.lemmy.ml/c/usmlr.
RoundSparrow@lemmy.ml · 1 pts · 3y
Lemmy.ml has now been upgraded to 0.18, can you test again please?
baronvonj@lemmy.world · 2 pts · 3y
It's working now!
RoundSparrow@lemmy.ml · 1 pts · 3y
Cool!
EuphoricPenguin22@normalcity.life · 2 pts · 3y
My best guess, if you can even see this comment, is that Lemmy.ml is still under strain. It seems like it's causing all sorts of issues, issues that aren't really a problem on just about any other instance.