What's up with some communities here having [community]@lemmy.world but not just [community]

https://lemmy.world/c/asklemmy@lemmy.world

https://lemmy.world/c/asklemmy (404 not found)

35 points · 14 comments · view on lemmy.world

14 Comments

eggnog@sopuli.xyz · 16 pts · 3y (6 replies)

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.

MentalEdge@sopuli.xyz · 24 pts · 3y (4 replies)

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.

fatcat@discuss.tchncs.de · 5 pts · 3y (1 reply)

Do we know if this can be fixed with an upcoming news release of Lemmy?

MentalEdge@sopuli.xyz · 12 pts · 3y

Already fixed, but not yet released.

DrYes@lemmy.world · 3 pts · 3y

Is there a fix?

admin@exploding-heads.com · 2 pts · 3y

That does not sound good

DrYes@lemmy.world · 2 pts · 3y

I don't know shit about Lemmy but I think you can't create a community unless logged into that instance.

stux@geddit.social · 11 pts · 3y (1 reply)

That's a lemmy bug..

Somehow the 'local' community gets the hostname extension and it won't federate or search well anymore

DrYes@lemmy.world · 7 pts · 3y

I hope it can get fixed in the DB or somewhere because I feel like asklemmy will be one of the bigger communities.

DrYes@lemmy.world · 4 pts · 3y

I also get a "subscribe pending" on /c/asklemmy@lemmy.world but all other communities seem to subscribe quickly.

sparky@lemmy.pt · 3 pts · 3y (2 replies)

This has happened to a bunch of the communities I created on Lemmyworld. I’ve been trying to ask for help - have created some threads about it and tried DMing the admins - but have never gotten a reply. Not sure what recourse I have, but I get a lot of DMs from users telling me it’s broken.

sparky@lemmy.pt · 3 pts · 3y

It does look like the admins will have to address this judging by the GitHub issue: https://github.com/LemmyNet/lemmy/issues/3075

sparky@lemmy.world · 1 pts · 3y
[ removed ]
V4uban@lemmy.world · 3 pts · 3y

The first one seems like an error

Maffrow@lemm.ee · 2 pts · 3y

Looks like the fix for this is implemented in release 0.18. We just need to wait for all the instances to upgrade.