Ah yeah, the password length was the issue. Summit truncates to 60 characters because it was a limit for Lemmy apparently. I’ll can do a dot release in a bit.

I can test with a 128 char password in a bit.

I just tested signing into both piefed.world and piefed.social with two different accounts, different usernames and passwords and both worked. Can you triple check to verify?

update I signed up for another account on piefed.social just to triple check and I was able to sign into that one too.

Update 2 tried signing in with user name and also with email separately and confirmed both work.

Thanks for reporting. Fixed in v1.67.0.

Good response. Thank you!

I am not able to reproduce this bug. Are you still able to reproduce this bug on the latest version of the app?

deleted by creator

Thanks for reporting this issue. I am able to reproduce the bug. The issue will be fixed in the next release.

These are M3 fields even though they do not look like it.

All text fields within the app are already M3 text fields even if they do not appear like it. If there are any visual bugs, please attach a screenshot of the screen and what the issue/bug is.

Ah i see. Ill add it to the roadmap

I already submitted a fix. Hope it goes through.

Urg, my submission to the play store got rejected. I’m going to need to make some modifications to the release to get comply with app store policies.

It looks like some of the optimizations I did broke custom post feed actions which is likely what you are crashing from. I’m going to release another hotfix in a few minutes.

A fix is on the way.

Summit will not allow me to post URLs or images.

No matter the image, URL, post, instance, etc.

Thanks for reporting. Looking now.

Added to the roadmap.

This feels more like a feature that the Lemmy server should implemented. At best the client can provide the information, but I think having Summit enforce post limits would be a terrible idea.

As for showing some sort of infographic for post frequency, I can’t immediately think of any way to implement this without it feeling a bit naggy/annoying to the end user. With Summit’s focus on configurability, I’m sure users will want to be able to turn such a feature off and if all the heavy posters simply turn it off then I don’t feel like it would be worth implementing.

I’m going to veto this idea for now unless someone can come up with a better way to implement this.

Thanks!