I can’t reproduce this issue. Can you verify you are on the latest version of the app? If you are still experiencing this issue on the latest version please post or DM me your settings as it might be setting related.

To copy your settings go to Settings > Import & Export settings > Copy settings for debugging.

This is already supported. It’s in Settings > Misc > Animation Level. Setting it to minimum should disable most if not all animations. If I missed any feel free to reply with any animations you noticed that were not disabled.

Thanks for reporting this issue. This is actually a bug with the client despite you having the “hide read” web setting turned on. It’s just that having that setting on surfaces the bug. I will fix it in the next release.

Looks like this is due to some inconsistency between lemmy and piefed. Lemmy considers 1 to be the default comment depth while PieFed considers 0 to be the default comment depth. Will fix in the next release.

Sorry that was the wrong setting. The correct one is in Settings > Posts feed > Post appearance> Post header style.

Settings > Posts feed > Posts feed header version.

You can use the old header style. Go to settings > post feed > post feed header style. Choose original.

The original ace Attorney trilogy is pretty good with humor, some people enjoy the humor in the somnium files, yazuka zero’s side content is pretty funny.

Thanks!

That is weird.

Thank you!

Good to hear!

I actually had the foresight to add this in all the way back when designing the settings for the post feed. The settings just aren’t visible to the user. I’ll add them in in the next release.

Will fix. Thanks for reporting!

It just works (well enough)!

Ohhh. Tap the title or anywhere near the top.

I highlighted the hotspots in the screenshot below

You can also revert back to the old layout in settings. I will also make a note of this in case I choose to tweak the UI later.

Which subscribed list button?

This should be fixed in the latest version. Please check for the update on the play store (or github).

Thanks for reporting. Will fix in the next release.

Sorry about that. Should be fixed now.