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.
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK0x400c96c96acbC6E7B3B43B1dc1BB446540a88A0141taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuVaddr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutmThe first time someone on an instance enters the name of a community, is when the instance goes and looks for it. Until then, that particular community is not federated to the local instance, and it is as if it does not exist.
Searching for a community in Jerboa, does not seem trigger this establishing of a connection.
Yep, sadly that happens, currently I just go to my instance's website, search it there (wait a few seconds because it takes a while) and subscribe there. I'll see it reflected in Jerboa soon enough.
I've noticed the same on the web UI. Searching a non-local community more often doesn't work than does.
I've found this mainly happens when trying to search for communities on other instances
I'm guessing this arises from that community not being shared with your home instance yet? Or some similar desync issue.
Yup. Instances don't start syncing until someone requests it.