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.
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 caps@lemmy.world 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”.
I get it man, it can be pretty frustrating when things don’t “just work”. I’ve noticed some inconsistencies with federated content updating on time as well, but a lot of stuff like this is to be expected as Lemmy experiences these growing pains. It’s been getting better slowly but surely, so I’m willing to stick through it.