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 - [email protected]
- Arizona Coyotes - [email protected]
- Boston Bruins - [email protected]
- Buffalo Sabres - [email protected]
- Calgary Flames - [email protected]
- Carolina Hurricanes - [email protected]
- Chicago Blackhawks - [email protected]
- Colorado Avalanche - [email protected]
- Columbus Blue Jackets - [email protected]
- Dallas Stars - [email protected]
- Detroit Red Wings - [email protected]
- Edmonton Oilers - [email protected]
- Florida Panthers - [email protected]
- Los Angeles Kings - [email protected]
- Minnesota Wild - [email protected]
- Montreal Canadiens - [email protected]
- Nashville Predators - [email protected]
- New Jersey Devils - [email protected]
- New York Islanders - [email protected]
- New York Rangers - [email protected]
- Ottawa Senators - [email protected]
- Philadelphia Flyers - [email protected]
- Pittsburgh Penguins - [email protected]
- San Jose Sharks - [email protected]
- Seattle Kraken - [email protected]
- St. Louis Blues - [email protected]
- Tampa Bay Lightning - [email protected]
- Toronto Maple Leafs - [email protected]
- Vancouver Canucks - [email protected]
- Vegas Golden Knights - [email protected]
- Washington Capitals - [email protected]
- Winnipeg Jets - [email protected]
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, [email protected]) 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.
Gah, this is the kind of thing that kills adoption. I can browse to the Caps community on https://lemmy.world, no problem. I see other lemmy.world communities on lemm.ee that I’m using and subscribed to. But I cannot get [email protected] to show up in the app or in search on the website. I tried another team community (I forget which) and had the same experience. But I’ve been able to add other lemmy.world communities to my subscriptions, and I know they work. Lemmy.world is listed as linked on lemm.ee, and vice versa. Basically everything says it should be working, but it isn’t, so it’s probably just some temporary issue.
I know once the server ‘finds’ it the first time, it should work fine, but right now it’s just frustrating - and I’m pretty patient.
Edit: Got it. Apparently I had to hit “next”.