Table of Team-Specific Communities

Division
Atlantic BOS BUF DET FLA MTL OTT TBL TOR
Metropolitan CAR CBJ NJD NYI NYR PHI PIT WSH
Central ARZ CHI COL DAL MIN NSH STL WPG
Pacific ANA CGY EDM LAK SJS SEA VAN VGK

List of Team-Specific Communities:

Troubleshooting

If a community appears as a 404 page when you click it, it likely means that the community is being hosted outside of the instance you are currently using and that nobody in your instance has viewed or interacted with that specific community yet. In order to address this, you will need to copy-paste the specific handle for the community (for example, !tampabaylightning@lemmy.world) into your searchbar so that your instance can “learn” that it exists, after which the community should display via linked URLs without issue. Hopefully this is addressed by the lemmy devs and streamlined in the near future.

  • ewe@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    I think they’re working on it, but this has to get better for Lemmy to take off. There’s so much confusion while trying to share communities.

      • ewe@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        Yep, I’m hoping that post blackout a lot of the people that started new communities will start advertising their community.

        I think one thing that could really help would be “official” browser extensions for Chrome and Firefox that turn lemmy links from a instance specific URL to their instance URL automatically so it “just works”

        e.g. your browser sees https://lemmy.world/c/winnipegjets and it automatically changes it to https://{your-defined-instance-domain}/c/winnipegjets@lemmy.world

        Until then, we need to get EVERYONE using the right syntax for links like OP did on this post with his updates: e.g. [Winnipeg Jets](/c/winnipegjets@lemmy.world) >> Winnipeg Jets