this post was submitted on 23 Jun 2023
6 points (100.0% liked)
Jerboa
10298 readers
2 users here now
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.
Built With
Features
- Open source, AGPL License.
Installation / Releases
Support / Donate
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.
Crypto
- bitcoin:
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK
- ethereum:
0x400c96c96acbC6E7B3B43B1dc1BB446540a88A01
- monero:
41taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuV
- cardano:
addr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutm
Contact
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yea I'm fine with waiting. I was more curious why ver .33 is no longer working, unless it was actually just ver .35 and labeled wrong. Like I said, I'm an idiot with stuff lol. Literally the first time I was even on github.
Thanks for answering.
0.0.33 isn't working anymore because Jerboa's default instance (Lemmy.ml) has already been updated to 0.18 for testing purposes and trying to connect to a 0.18 instance causes Jerboa 0.0.34 and older to crash.
We are in a rather silly state where we can't use Jerboa 0.0.35 to log in to instances other than Lemmy.ml and can't use Jerboa 0.0.34 when we haven't been logged in before updating. ๐ฌ