- cross-posted to:
- jerboa@lemmy.ml
- cross-posted to:
- jerboa@lemmy.ml
cross-posted from: https://lemmy.ca/post/942473
I have a fork of Jerboa to help with any login issues for those with accounts still on 0.17.x, until either the servers upgrade or until a newer version allows connecting to both 0.18 and pre 0.18 servers.
Later tomorrow I will include a version with the app name changed so that it can run alongside dessalines’ version.
- Lionir [he/him] ( @Lionir@beehaw.org ) English6•1 year ago
I wonder - why not just use the older APK? It still works just fine.
- abclop99 ( @abclop99@beehaw.org ) English5•1 year ago
Because if you’re not logged in, it will try to load lemmy.ml and crash.
I still got it to work by spam tapping in the right places to open the log-in page.
- Lionir [he/him] ( @Lionir@beehaw.org ) English3•1 year ago
What? Why does it crash? Did they just completely removed websockets so the applications are entirely incompatible between versions of Lemmy?
I reinstalled 0.34 and there was maybe 5 times where it would crash within a second or two of app launch. Eventually it was stable enough to let me log in to beehaw though and it’s been fine since
- DarbyDear ( @DarbyDear@beehaw.org ) English1•1 year ago
To answer your question about if they removed websocket support (a couple of days late, so you might already have the answer), it looks like that’s exactly what happened.
- Lionir [he/him] ( @Lionir@beehaw.org ) English2•1 year ago
I get they did that. I just kinda thought the UI would stop using it, not that it would kill all clients. It’s just a bit off but I guess they wanted to rip the bandaid off quickly as Lemmy popularity soared.
- DarbyDear ( @DarbyDear@beehaw.org ) English2•1 year ago
Yeah, I don’t know if it’s how I would approach the situation if I had more dev resources, but as a (primarily) 2-person outfit, I can see why they took that route. It’s really easy to fall into the trap of “mark it as obsolete and create a tech debt item to remove it completely,” then never have time to go back for it. Next thing you know, you finally address it a year or two later and find out that you broke someone’s workflow