Now pouring in a Lemmy near you, let me be the first to welcome you to /c/wine, a community for oenophiles, sommeliers, vintners, and more. Come share in our love of the nectar of the gods!
Now pouring in a Lemmy near you, let me be the first to welcome you to /c/wine, a community for oenophiles, sommeliers, vintners, and more. Come share in our love of the nectar of the gods!
I’m honestly not sure if this one is on Lemmy or on me, but I think it’s confusing for sure!
Yea tbh I took a look at your profile and saw all the communities you moderate and noticed ones with “@lemmy.world” are unreachable with things like “lemmy.world/c/vinyl” but others like “lemmy.world/c/languages” work just fine. Did you name them all in the same way or did you add “@lemmy.world” to some but not others. I think it may be the latter which is where the problem occurs.
I didn’t explicitly add the @lemmy.world when I created them. It might have something to do with my main account being on another instance, @lemmy.pt? Not sure. But at any rate it doesn’t seem to affect much once people are subscribed. It looks the same as any other @lemmy.world community from another instance, but I see now it looks a bit weird from inside lemmy.world. I… don’t know how to fix it now, I can’t edit the community name and if I try to create just /c/wine for example, it fails silently. So hopefully as it is now won’t be a problem as we already have subscribers. Still learning as I go here, too.
Interesting. In that case, I think the most likely explanation is that when someone from a different instance than the one that hosts the community makes the community it adds the extra @(instance) to the end. Whether thats a bug or a feature only the devs know i guess lol.
Finally got some answers: https://lemmy.world/comment/485314 Admins looking into it