This release adds some mod tools for PieFed to the app (some mod tools are still missing because they are not supported by the API yet).

This release also makes significant changes under the hood. These changes are meant to keep the app snappy. The app goes through lots of updates and features are added left and right so some occasional refactoring is necessary to ensure the app does not get too bloated.

Changes to the internal portions of the app is also why this release took a bit longer. These changes can cause bugs if not done correctly and I had to dogfood the app for a while before I was confident enough to release the update.

Full changelog

• Add support for modlogs on piefed.
• Add support for reviewing and accepting/rejecting registrations.
• Add support for [spoiler] tags.
• Fix some bugs with finding text on the post screen.
• Optimized save/restore post feed when app is killed and restored. This adds a slightly longer delay when the app is restored after it's been killed by the OS but it should reduce the number of network calls and improve snappiness once the app is restored.
• Show HD image toggle in more situations.
• Fix a bug where the loading spinner never disappears on a post even though internally the post has failed to load.
• Fix a bug where "No comments" is not shown when there are no comments.

Update
v1.80.1

• Fix a bug where long tapping on an image will load the thumbnail and not the original image.

Update
v1.80.2

• Fix a bug where sometimes resuming the app, the post feed will fail to restore.

Update
v1.80.3

• Fix a bug where link posts with a thumbnail incorrectly try to load the link and not the thumbnail.
• Fix a bug where community icons sometimes flicker.
• Fix a bug where viewing an image of a post will no longer default to the thumbnail if it has been cached.
• Reverted change where opening a post from the post screen will open it in the same post window. This was causing confusing back navigation problems.

Update
v1.80.4
I accidentally didn't build the correct code because the code was written on another computer and I also accidentally shipped some test code. Doing another release to correct these.

Update
v1.80.5

There was a one line code change that I missed when cleaning up after experimening with something that was increasing crash rates. My bad.

Good to see more piefed features! Thanks!

Great, thank you!

How does a longer app restore delay reduce network calls and improve smoothness? I fail to see the correlation.

Sorry the note is a bit misleading. The change that was made just happens to do both of these things.

The low level detail is that app caching logic was moved into a lower layer. Some caching logic was moved to the layer that was doing the network calls to fetch posts.

When the app restarts, that layer restores the cache so it can rely on the cache for some of the network calls. This is why there's less network calls.

Because the cache is at a lower level, more work has to be done to process the data which is why its slower. I can also do like a multilayer caching solution but I didn't think it was necessary.

I'm unable to see the full resolution of images from image posts anymore. It looks like it's loading just the thumbnail version instead of the actual image. Anyone else experiencing the same thing?

You can't see the full resolution anywhere or is it only on certain screens?

When I directly open the image from my feed, it shows the lower quality image. But when I open the post first and then open the image, I get the higher quality version.

Here's a screen recording.

Cool. I was able to reproduce the issue. I'll release a fix soon.

Just got the update and the bug has been squashed! Thank you!

Edit: Just updated Lemmy to 0.19.17 and the error is gone. So it wasn't a Summit issue.

I have a strange one. Since 1.80 I can't go to posts by their canonical link anymore. Like the link to this changelog on update. Or when clicking a post link in a comment or post. The error message is pretty useless.

Client error. Code: 400. Message: Couldn't find post.

Now, I would have imagined such a bug to stirr up more people. But since nobody else is complaining I assume that it's just a problem on my end.

To test it out, here are a few post links:

• https://swg-empire.de/post/6491078
• https://lemmy.world/post/44536250

While testing this I noticed that when I hit the back button from the error or the post (when it's a local link) I go back to the post list and not to the comment where I clicked on the link.

Thanks, I had the same problem and it's fixed now.

But now when I open an image there is a small moment where the screen goes dark (literally just a few frames). This is only happening when opening an image for the first time. Ich guess it is loading the full sized image. If I remember correctly the previous bevaviour was to first show the thumbnail and then the hd version. Can this be made the bahaviour again, even the smal black flash is quite distracting.

I tried recording but it didn't show up in the screen capture, though I can reproduce it on without problem

I can fix this. Thanks for reporting.

Will revert this change.

Font size sliders are buggy. Its moving up and down when i adjust the slider. I already reported this in github. Kindly look into it.
Here is the screen record of that bug.

On all (and presumably other subs) The app seems to never update the sort order.

Wait a few hours and a sort by top looks like this:

Even closing and reopening doesn't affect it (including applying the hide read posts).
Changing instances or quitting the app does make it fetch the new order.

I'm waiting for my application to be approved so I can test on your instance however I teated on 3 other instances and I couldn't reproduce the issue. Can you check if this is only an issue on your instance?

I'll start a test on dbzer0 but it'll take a while for the sort to change

I think I have reproduced it on dbzer0. Two posts incorrectly sorted right after a refresh, on top-daily sort.

I the process I changed vote display to show score, which seems broken on compact mode.
Right after toggling the setting it looked like this to me:

After a restart it just showed both votes separately anyway, seemingly ignoring the setting. That's why the screenshot above uses a different layout.

I think I know what is happening. You are not doing a pull to refresh I assume so when the app fetches the latest vote scores it isn't updating the cached values. The sort order is correct, just the post scores are out of date. I can look into a fix.

Oh actually I figured out there was a bug that was causing this. Will fix in the next release as it's a UI error. The sorting order is correct, just the post scores are out of date like originally suspected.

Thanks for reporting!

Edit Edit: Yeah you are definitely right, it doesn't show the updated votes, the order doesn't change. I was probably seeing new posts mixed in.

Edit: Actually you may be right, I'll have to wait some more for testing.

That sounds odd. The cases I saw definitely had updated scores. I usually read all 400+ ones yet they clearly have new ones that reached 400 since I read.
And restarting the app changes the sort order compared to before, while the votes stay the same.

The vote numbers may be getting fetched in the way the app updates old info when feeds have been open for a while, but the sort order is definitely wrong.

Pulldown refresh and exiting and reopening the feed both don't fix it.

Yeah the bug is that fetching posts from the server isn't causing the scores to update. I found the cause and fixed it going forward.

Will fix in the next release.

Hey! Thanks for the awesome app, it's been my favorite Sync replacement and became my new main client :)

I have one possible bug to report. I have multiple accounts, and want one to use All as the homepage, and the other to use Subscribed. But the account-specific settings seem to change the global default (the override isn't showing up in the "changes" view), no matter what I try.

Am I doing something wrong?

Thanks again for all your efforts!

This isn't supported at the moment. I'll add this to the roadmap.

Awesome, thank you!