It often happens that a given lemmy link didn’t match with my own login from another instance. This causes troubles to comment and participate in the thread. This is what I have learned so far. Is there a better method of doing this? Browser extension suggestions are welcome.
Context:
- Have an account
@username
on instancelemmy.test
and being logged in - Given a lemmy link
lemmy.example.com/post/12345
- Want to comment as
@username@lemmy.test
onlemmy.example.com/post/12345
Expected behavior:
- Opening links from
lemmy.example.com
automatically recognizes login fromlemmy.test
, commenting and voting done without problems
Actual behavior:
- Instance
lemmy.example.com
expects logins only from its own server, not other federated servers likelemmy.test
Manual fix (for web browsers):
- Check for the “federation link” (the icon with five-colored star, is there a name for this?) from linked URL’s page. (If the icon does not exist, check Observations below)
- Open “search” from own instance (
lemmy.test
> search) - Enter the “federation link” at search bar.
- First result should be a URL that’s compatible with the own instance: e.g.
lemmy.test/post/98765
Observations:
- If the link and its OP shares the same instance domain (
@user@lemmy.example.com
posting to!community@lemmy.example.com
), then the federation link should be the link itself (please confirm if this is actually true). - If not, then the “federation link” has to be obtained.
- INCLUDE HTTPS before domain, otherwise it won’t appear in the search:
https://lemmy.example.com/post/12345
OK
lemmy.example.com/post/12345
NOT OK
There is a button with fediverse icon that can be used to go to the post’s link in the the original instance. Share that link instead. People that want to open it on their own instance can paste the link in their instance’s search bar to find the local federated copy. A bit awkward but at least it works.
Is there technical reason it has to be the original instance’s link instead of any other server being linked to? Federation and all, I see it as having an additional node before destination, but it’s not a broken link regardless.
The original url is basically the real post ID, which can be used to identify the same post regardless the instance you’re currently in. AFAIK there are efforts to make deep linking work without copy pasting the original instance’s url, so hopefully things are getting better in the coming months.