There was a bug in the v1.67.1 release that was fixed in v1.67.2. Can you confirm of you are using v1.67.2 of the app?
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.
Test