The 0.18 version of Lemmy was announced. This will solve many issues.
But we can’t upgrade yet because the captcha was removed, and captcha relied on Websockets, which are removed in 0.18 so despite the devs agreeing on my request to add captcha back, this will not be until 0.18.1. Without captcha we will be overrun by bots.
Hopefully this 0.18.1 will be released soon, because another issue is that the newest version of the Jerboa app won’t work with servers older than 0.18. So if you’re on Lemmy.world, please (temporarily) use another app or the web version.
Thanks for keeping the bots out! I’m still successfully using Jerboa, btw.
you’re probably not using the latest version from the GitHub repo then
I’m and it works with lemmy.world, I still get the disclamer about Lemmy version, but still work regardless, what is it happening here?
Try logging out and then logging back in on lemmy.world
If that locks me out I won’t.
The new version from GitHub will give a warning, but mostly works with an outdated Lemmy version. That’s how I’m typing this very comment.
It does have a few actions that result in an immediate crash on outdated servers, but posting, commenting, following communities and reading notifications work.
Oh, and you must be logged in already. New logins do not work.
I am. It gives me the warning and crashes a lot, but it works a little.
It crashes far too much without 0.18 for me; resorted to using the web view.
Successfully using the latest Jerboa and posting here from a different instance :)
Probably because you’re already logged in from the previous version? On a clean install it won’t be able to login, it will literally tell you that the instance needs to be at 0.18.0.
Ahh. That’s really not good. In a time where we are expanding we have broken captcha resorting in instances protecting themselves from bots breaking the best Android app. Wonderful.
I am, but here we are
Is the version on GitHub more recent than the one in the Play Store? The changelog in the Play Store said the update would make Jerboa ready for 0.18 and that’s the version I have installed.
It was old (33) last evening when I checked. This morning it’s up-to-date, but I’m obviously not applying it.