this post was submitted on 12 Jun 2023
87 points (100.0% liked)

Hockey

115 readers
1 users here now

Rules

List of Team-Specific Communities:

Metropolitan Division

Atlantic Division

Central Division

Pacific Division

founded 3 years ago
MODERATORS
 

Noticed a distinct lack of a community for the Bolts, so I went ahead and created one at tampabaylightning@lemmy.world. It got me thinking about other team communities, so I thought it might be helpful to aggregate them all into one post.

EDIT: I fixed the community links, so you should no longer be booted from your instance when clicking them ๐Ÿ˜‰

List of Team-Specific Communities:

If you run or know of any team specific communities, feel free to comment them below and I'll add them to the list!

you are viewing a single comment's thread
view the rest of the comments
[โ€“] Ginjutsu@lemmy.world 4 points 1 year ago (1 children)
[โ€“] ewe@lemmy.world 4 points 1 year ago* (last edited 1 year ago) (1 children)

One thing...If you link to the community using the following notation:

c/seattlekraken@lemmy.world

instead of the full

https://lemmy.world/c/seattlekraken

then it will take you to the community, but keep you on your instance (e.g. you are on lemmy.ca, but looking at c/seattlekraken on the lemmy.world instance)

I'd recommend using that in the links instead of the actual link to the instance with the domain in front. I think this only works from posts, not from comments, for whatever reason. It's weird and I'm still trying to figure it out.

[โ€“] Ginjutsu@lemmy.world 3 points 1 year ago* (last edited 1 year ago) (1 children)

Hmm, I tried it out, but it seems to add a /comments/ string to the URL before the c/seattlekraken@lemmy.world in the link, rendering it unusable. Interestingly enough, the same technique works fine when viewing the post from the main community page (before opening the post to view comments).

[โ€“] ewe@lemmy.world 2 points 1 year ago

Yeah, I can't get it to work either. I thought that was the way it was supposed to be, but I'm mistaken, or there's a bug, which is not unlikely, I suppose :)