Timeouts might be from the server struggling since the reddit blackout is bringing in a lot of users at the same time right now. I'd wait a few days and see if the issue disappears or maybe a second account on a lesser known instance might help.
I’ve noticed (although on the .ml instance) that even whenever GET requests go through fine (albeit a bit slow) POST requests don’t actually return a response. After 60 seconds they will timeout, even if the operation actually does complete successfully. This happens mainly on voting and making comments from what I see.
I'd imaging it is a massive influx of users periodically overloading it.
I think its best to just use the lemmy web instance interface to subscribe to communities on all kinds of instances, and then they just show up in Jerboa. :)
Timeouts may be because you are using an overloaded instance like lemmy.ml when you should spread out on other instances. :)
At least for me, I noticed subs worked but wouldn't show up in the list UNTIL I restarted the app.
It is also happening to me, both on the app and the Web UI
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.
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK0x400c96c96acbC6E7B3B43B1dc1BB446540a88A0141taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuVaddr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutm