Thanks, we are aware: https://discuss.online/post/1294119
this post was submitted on 09 Sep 2023
5 points (100.0% liked)
Neurodivergent
359 readers
1 users here now
Welcome
A community of individuals with neurodivergent issues or know a neurodivergent person.
Do not avoid sharing or helping because you do not want to associate your account with personal details.
It's healthy to talk and healthy to help others. Create an alt account if it helps. Folks need encouragement.
Rules
- Don’t spam
- No personal and/or confidential information
- No threatening, harassing, or inciting violence
Similar channels
- [Arctic Autism: [email protected]](/c/[email protected])
- [Autism: [email protected]](/c/[email protected])
founded 1 year ago
MODERATORS
Alright.
Have you tried removing the instance and adding it back?
I’m not doing anything different that could cause this. I’ll investigate.
I redownloaded Jerboa and added all accounts except for this one. It was impossible to even open it because the app would crash within half a second.
I also use Jerboa and can confirm this: the app crashes shortly after trying to connect to discuss.online.
I tried to add discuss to the Liftoff app, but it says that the instance cannot be found.
I tried that on Connect, and I'm unable to sign back in. I've unable to use any apps with this instance for at least 2 days. The website seems to work ok weirdly but that's not ideal for me for accessibility reasons.
Good to know, I did apply an update about that time. I’ll look into a rollback.
Any new updates?
There's a stickied instance post about issues with 3rd party clients https://discuss.online/post/1294119
Oh, thanks. I can't really look at it because the instance doesn't open on the app.
Hah sorry, I should've thought of that. Long story short: This instance is running on latest Lemmy beta version. Lemmy made a recent change to the beta version which breaks 3rd party apps like Jerboa. DO tried to rollback their version but it failed. We now have to wait until the 3rd party apps release an update that works with Lemmy beta(or future v0.19 when released).
The most recent update from instance owners saying the same thing:
After some additional digging through the Lemmy diff for beta.5 to beta.8 (and then looking through the PRs that were merged to create this diff), the issue is indeed with the Lemmy code and is even called out in one of the PRs,. What this means is that the 3rd party clients that are not able to access the site will need to update their code to fix things on their side (or else they will be broken when v0.19 is released and all other instances update to it).
Ah, well, good luck with that.