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!

  • @forwasteEnglish
    1•2 years ago

    In theory I’m pretty sure it should be working like that but it seems for whatever reason this community needs the extra @lemmy.world. My guess is its a bug that’s causing it to behave like that. Every community I see can be reached with https://(instance)/c/(community).

    The unfortunate growing pains with Lemmy seems to be everyone trying to understand how the Fediverse works while also having to work with bugs that cause it to not function as intended.

    • [email protected]MEnglish
      2•2 years ago

      I’m honestly not sure if this one is on Lemmy or on me, but I think it’s confusing for sure!

      • @forwasteEnglish
        1•2 years ago

        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.

        • [email protected]MEnglish
          1•2 years ago

          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.

          • @forwasteEnglish
            1•2 years ago

            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.