Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.
Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.
Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK0x400c96c96acbC6E7B3B43B1dc1BB446540a88A0141taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuVaddr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutmI 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:
