When I open links to other communities in the Lemmyverse, they don’t open in Jerboa. They open in chrome. As a result, I’m not logged in and can’t subscribe or interact. I’ve found lots of communities this way but it’s a hassle to subscribe to them.
I was just thinking about this. The issue may be more complicated than it looks.
Currently Jerboa handles the links of only a handful of instances. As Lemmy as a whole grows and more and more instances pop up, it’s just unrealistic to have the app handle 50 million server hosts.
Can opening links be something handled internally, at least initially, like maybe checking against the home instance’s list of federated servers?
Lemmy links have the form https://host/c/name. Sniffing the /c/name would be enough for Jerboa to guess.
It gets even trickier when you remember that other federated instances might be mastodon or peertube or Misskey or kbin, etc.
This, for me, is one of the most frustrating parts of using Jerboa.
My instance (programming.dev) isn’t evem on the built-in list.
What about using a “lemmy:” schema?
This is a known issue, you can find the corresponding issue on GitHub:
