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.
Its a bug
Any idea what it is about the community that is triggering the bug? I see other communities are working just fine.
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