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

Chat

7499 readers
7 users here now

Relaxed section for discussion and debate that doesn't fit anywhere else. Whether it's advice, how your week is going, a link that's at the back of your mind, or something like that, it can likely go here.


Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Master@beehaw.org 6 points 1 year ago (1 children)

!startrek@startrek.website is the link but it'll probably be easier to just go here.

https://beehaw.org/search/q/%20startrek/type/Communities/sort/TopAll/listing_type/All/community_id/0/creator_id/0/page/1

Which you can then select the one you want and it will take you to a link like this.

https://beehaw.org/c/startrek@startrek.website

Notice how it references the original link? the ! tells the site to view the community locally instead of opening it in it's native location.

[–] 2muchcaffeine4u@lemmy.fmhy.ml 2 points 1 year ago* (last edited 1 year ago) (1 children)

It seems like it should be straightforward, but it doesn't appear to be working very well.

I just saw a community I wanted to follow. My account is in lemmy.fmhy.ml, and the community is in lemmy.world.

The link to the community is this: https://lemmy.world/c/sql

Following formatting standards, the link for me to be able to join SHOULD be https://lemmy.fmhy.ml/c/sql@lemmy.world correct?

But when I type that in I get "404: couldnt_find_community". This is true every time I try to simply change the community name. In fact I have not been able to go to a single community using the URL formatting in this way.

Am I misunderstanding something?

[–] Threen@aussie.zone 2 points 1 year ago

The trick I use is to double-search for it

On your instance, search for the full URL of the original community, then search again for just the community name

So for you:

It is not ideal, but it has worked on my instance every time