If I am looking at a post on another instance, how do I best find the corresponding post on beehaw?
For example if I am on https://lemmy.ml/post/1181103 how do I most efficiently open it in beehaw so I can interact? There is a sidebar that says
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !fediverse@[email protected]
I have not been able to follow these instructions successfully. idk about anyone else.
But what if I was looking for something that was not one of the most recently posted items? Do I just have to manually scroll?
Is there any corresponding identifier of the post that is consistent between instances? There must be, right? How else could they all interact otherwise.
Any help would be welcome as I am constantly ending up on other sites and this is very cumbersome.
I think the easiest way is to take the link for the post you want to interact with (so https://lemmy.ml/post/1181103) and put it in the search (the spyglass to the left of your username). I just tested it and this should pull up the post so you can interact with it on Beehaw.
Reminder that if you don't see anything, give it a few minutes to pull the information and then try again. Instances we haven't interacted with before can take a minute since the information needs to be pulled.
Thanks that does work! I am sure it didn't work before on multiple attempts... Maybe the filters at the top were toggled differently either by default or I changed it by accident.
It seems like there should be a smoother way to do this, like a browser extension or something if needed. I tried adding a custom search in firefox but it doesn't work on beehaw due to special characters in all relevant queries. idk if there is a way to get firefox to process all those.
Might be timing then, since it loaded for me immediately - you got the request going and then it was ready when I searched.
I know the Lemmy devs have a huge load of things to focus on with the current (unexpected) influx of users, but hopefully this is something they'll work on improving somewhere down the line so it will be smoother or at least say it's still searching so you don't think it failed