Looks like the fix for this is implemented in release 0.18. We just need to wait for all the instances to upgrade.
could it be that they were made by someone from a different instance? so on their end it specified lemmy.world but then resulting in that specification for everyone.
Its a bug. I caused this to happen with one pf my communities by editing it with a remote account.
This causes it to get stuck in a state where its no longer marked as a local community.
This also breaks federation.
Is there a fix?
That’s a lemmy bug…
Somehow the ‘local’ community gets the hostname extension and it won’t federate or search well anymore
I hope it can get fixed in the DB or somewhere because I feel like asklemmy will be one of the bigger communities.
I also get a “subscribe pending” on /c/asklemmy@lemmy.world but all other communities seem to subscribe quickly.
