Why does this community need '@lemmy.ml' even locally?
Why does this community need '@lemmy.ml' even locally?
Community to discuss US Major League Rugby [https://www.majorleague.rugby/]. Schedule [https://www.majorleague.rugby/schedules/] Standings [https://www.majorleague.rugby/schedules/] The Rugby Network [https://therugbynetwork.com] 1. No spoilers! See here [https://join-lemmy.org/docs/en/users/02-medi...
Going to https://lemmy.ml/c/usmlr gives a 404, but https://lemmy.ml/c/[email protected] 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/[email protected]/data_type/Post/sort/New/page/1
- https://beehaw.org/c/[email protected]/data_type/Post/sort/New/page/1
- https://lemmy.one/c/[email protected]/data_type/Post/sort/New/page/1
- https://sh.itjust.works/c/[email protected]
- https://kbin.social/m/[email protected]/newest
I would assume beehaw simply won't receive the posts I make from my lemmy.world account, because defederation.
You're viewing a single thread.
It's the remote moderator bug. Should be fixed in 0.18
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.
Lemmy.ml has now been upgraded to 0.18, can you test again please?
It's working now!
Cool!