this post was submitted on 14 Jun 2023
7 points (100.0% liked)

Fediverse

17776 readers
45 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS
deadsuperhero@lemmy.ml
wakest@lemmy.ml
7
[solved] Subscribing to a community on a different instance is so annoying! (lemm.ee)
submitted 1 year ago* (last edited 1 year ago) by Hedup@lemm.ee to c/fediverse@lemmy.ml
19 comments fedilink hide all child comments
 

So far for me the process is very convoluted:

  1. I go to https://browse.feddit.de/ and find the community.
  2. Then I need to copy it's name.
  3. Then I need to go to my particular instance (lemm.ee)
  4. Then I type manually in my browser address bar lemm.ee/c/
  5. Then I go back to https://browse.feddit.de/ and copy the address of the original instance of the community.
  6. Then I go back and add the original instance address to already typed thing in step 4 like this lemm.ee/c/@
  7. Then I can finally subscribe!

Oh my God! Please, tell me there's a better way of doing this!

EDIT: There is a better way! Solution is to ... use the search function in your instances home page and select community (if it exists already) and search. This way I don't need to go to browse.feddit.de anymore. And links will take me straight the the communities "reflection" in my own instance, where I can subscribe.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] Hedup@lemm.ee 0 points 1 year ago (1 children)

Wait, you can force your instance to start federation with another instance!? Did I understande you correctly?

[โ€“] brunox@feddit.cl 2 points 1 year ago

Not exactly force. It's by design. Instances don't federate with each other unless a user of one wants to communicate with the other (via subscription, or commenting, or whatever).

But instances can block each other and if that happens, there's no way you can access from your instance.

What usually happens is that big instances (like lemmy.ml), just by the mere fact that they are big, are probably already federating with your instance anyway so you may not have encountered this situation.