I gave it some thought and in my opinion this isn’t a bug. I think a lot of gifs do not loop but users are used to gifs looping so the app auto-looping gifs should be considered a feature.

To handle edge cases like this, I think it’s better to just add a setting to allow the user to choose between looping gifs automatically or to use the GIF loop metadata. I added an item to the roadmap for this.

Will fix in a patch update.

The cause for this one is PieFed doesn’t behave like Lemmy. For the Lemmy API, you can navigate to a post using comment ID alone. PieFed requires a post id and a comment id.

Urg. I blame PieFed for this one. The API documentation clearly says that Posts and Comment objects have a field named updated but the server actually returns it as edited_at. This value is used by the client to determine if a post/comment needs to be re-rendered.

Update Will fix in a patch update.

8 hours every day :D. But Imy sleep schedule is really messed up. 😅

Should be fully released now!

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.

I don’t mind Jira that much.

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.

Grok, is this real?

Mb

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.

Ohhhhh that’s a window…