Thunder App

2813 readers

15 users here now

An open-source, cross-platform Lemmy client for iOS and Android.

This community is intended to discuss features and feature suggestions for Thunder; as well as friendly, respectful talks about Lemmy in general.

Please use the GitHub repository linked below to submit bug reports, so keeping track of them is easier, and make sure to search first if you already can find an issue for your report.

If there are any developers who would like to contribute, feel free to reach out on GitHub!

General Links
Website: Link
GitHub Repository: Link
Matrix Space: Link

Android Releases
IzzyOnDroid: Link
Google Play: Link

iOS Releases
Apple App Store: Link
TestFlight Beta: Link

Related Communities
Nightly Community: Link

founded 1 year ago

MODERATORS

darklightxi@lemmy.world

poolitzer@lemmy.world

darklightxi@lemmy.ca

micahmo@programming.dev

Password limit is set to 60 characters (programming.dev)

submitted 1 year ago by snowe@programming.dev to c/thunder_app@lemmy.world

18 comments fedilink hide all child comments

It seems like the password limit is set to 60 characters so I’m unable to login to my instance. There probably should be no limit in the app because each server could have different limits set.

you are viewing a single comment's thread
view the rest of the comments

[–] darklightxi@lemmy.world 1 points 1 year ago

I think that check must be bypassed for admin passwords, or it was instituted after I created programming.dev

That could be a possibility - we can do some tests to verify if that’s the case. I found this related issue which might indicate that all auth flows through the same logic.

Even if that was the limit, it still should be enforced by the backend on login, not on the frontend

Unfortunately, that might not be the case. Dessalines mentioned in this comment that the backend doesn’t truncate overly long passwords, and throws an error instead. Although, as you mentioned, this might be bypassed for admin users.

Either way, I think we can take a deeper look at this and verify this information! Feel free to create a new issue for this on GitHub if you’re able to so that we can track this issue better.