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 More changes:

  • 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.
  • Björn@swg-empire.de
    2·
    23 hours ago

    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:

    • Björn@swg-empire.de
      1·
      1 day ago

      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.

  • DundasStation
    4·
    2 days ago

    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?

          • Kwdg@discuss.tchncs.de
            2·
            9 hours ago

            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

  • limerod@reddthat.com
    1·
    3 days ago

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

    • idunnololz@lemmy.worldOPM
      8·
      3 days ago

      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.