The steps to reproduce don’t seem to have been tested but the current theory is that if a user is federated to a server that has an admin with the same name, and then that user is banned, then it may cause the admin to be un-admined I guess due to an update that doesn’t correctly distinguish the local and remote users.
Honestly, it’s annoying but may not be a showstopper for upgrading to 0.18
You can fix it by changing the flag in the database, and it’s not giving the admin permissions to another user which would be a big security problem.
Hi @Dave@lemmy.nz my Jerboa app (Android) has auto updated overnight and now I can no longer log in that way as it requires 0.18. Guess I’m not the only one. Did you decide yet if you want to upgrade to 0.18?
I did not know that! Thanks for letting me know. I will make upgrading a priority, though we will probably need to turn on registration applications as the cloudflare bot detection doesn’t seem to be working
Yeah it’s a bit annoying that they didn’t deprecate it instead of just ripping it out.
Anyway, I see you’ve updated it to 0.18 :) Hopefully all goes well!
There was a technical reason. This version removes websockets, which has performance improvements and solves a lot of outstanding issues.
Unfortunately the current captcha relies on websockets. The option is actually still there, it just causes an error on the registration page, stops registration from showing, and still doesn’t actually show a captcha.
Long story short, it’s just broken rather than deliberately removed (though originally they planned on dropping it which is why no effort went into solving the issues.
Didn’t know about the admin lockout bug, that sounds serious.
The steps to reproduce don’t seem to have been tested but the current theory is that if a user is federated to a server that has an admin with the same name, and then that user is banned, then it may cause the admin to be un-admined I guess due to an update that doesn’t correctly distinguish the local and remote users.
Honestly, it’s annoying but may not be a showstopper for upgrading to 0.18
You can fix it by changing the flag in the database, and it’s not giving the admin permissions to another user which would be a big security problem.
Hi @Dave@lemmy.nz my Jerboa app (Android) has auto updated overnight and now I can no longer log in that way as it requires 0.18. Guess I’m not the only one. Did you decide yet if you want to upgrade to 0.18?
I did not know that! Thanks for letting me know. I will make upgrading a priority, though we will probably need to turn on registration applications as the cloudflare bot detection doesn’t seem to be working
Yeah it’s a bit annoying that they didn’t deprecate it instead of just ripping it out. Anyway, I see you’ve updated it to 0.18 :) Hopefully all goes well!
There was a technical reason. This version removes websockets, which has performance improvements and solves a lot of outstanding issues.
Unfortunately the current captcha relies on websockets. The option is actually still there, it just causes an error on the registration page, stops registration from showing, and still doesn’t actually show a captcha.
Long story short, it’s just broken rather than deliberately removed (though originally they planned on dropping it which is why no effort went into solving the issues.