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:
- Anaheim Ducks - !goducksgo@lemmy.world
- Arizona Coyotes - !azcoyotes@lemmy.world
- Boston Bruins - !bostonbruins@lemmy.fyi
- Buffalo Sabres - !sabres@lemmy.world
- Calgary Flames - !calgary_flames@lemmy.ca
- Carolina Hurricanes - !anes@lemm.ee
- Chicago Blackhawks - !blackhawks@lemmy.world
- Colorado Avalanche - !avalanche@lemmy.world
- Columbus Blue Jackets - !bluejackets@lemmy.world
- Dallas Stars - !dallasstars@lemmy.world
- Detroit Red Wings - !detroitredwings@midwest.social
- Edmonton Oilers - !edmontonoilers@lemmy.ca
- Florida Panthers - !floridapanthers@lemmy.world
- Los Angeles Kings - !kings@lemmy.world
- Minnesota Wild - !wildhockey@lemmy.world
- Montreal Canadiens - !habs@lemmy.world
- Nashville Predators - !predators@lemmy.world
- New Jersey Devils - !devils@lemmy.world
- New York Islanders - !nyislanders@lemmy.world
- New York Rangers - !nyrangers@lemmy.world
- Ottawa Senators - !ottawasenators@lemmy.ca
- Philadelphia Flyers - !flyers@midwest.social
- Pittsburgh Penguins - !penguins@lemmy.world
- San Jose Sharks - !sanjosesharks@fanaticus.social
- Seattle Kraken - !seattlekraken@lemmy.world
- St. Louis Blues - !stlouisblues@midwest.social
- Tampa Bay Lightning - !tampabaylightning@fanaticus.social
- Toronto Maple Leafs - !leaf_nation@lemmy.ca
- Vancouver Canucks - !canucks@lemmy.ca
- Vegas Golden Knights - !vegasgoldenknights@lemmy.world
- Washington Capitals - !caps@lemmy.world
- Winnipeg Jets - !winnipegjets@lemmy.world
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.
Yeah, that’s because the direct link takes you to a different server.
Instead, copy the link, and in your instance click on the search icon up top, and do a search for it there. That’ll give you a link relative to your server/instance. Click that and you’re good.
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.
Yup, it’ll be a great thing for new folks trying out Lemmy when this gets sorted out.
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 tohttps://{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 JetsThat style link only works if your instance already has someone subscribed to it. For now, only the search box will cause your instance to learn new communities.