The backlog of community suggested features is huge and I am slowly burning through it woohoo.

Full changelog

  • Add support for featured posts on Piefed instances.
  • Add setting to wrap comment headers if they are too wide. Default: on.
  • Add setting to have “Hide read” on when the app is launched. Default: off.
  • Add feature to highlight new comments. Can be enabled/disabled in settings. Default: On.
  • Change default setting for FAB quick action: None -> Hide read.
  • Fix some link parsing issues.
  • Fix a bug where community is “reset” and position/sort order is lost when app is killed and recreated.
  • Fix an issue where video players are not getting deallocated correctly.
  • Fix a bug where the comments footer disappears if “show navigation bar on post” is enabled.
  • Björn@swg-empire.de
    1·
    4 months ago

    Managing read and hidden messages on the client will result in many unnecessary calls to the server to retrieve posts that won’t be displayed. That’s especially bad for small underpowered servers or servers with many (Summit) users.

    When the read posts are filtered out on the server side they do it already when retrieving them from the database. That is much easier on the resources and also means fewer data sent to clients, which should be good for people on metered connections.

    • idunnololz@lemmy.worldOPM
      3·
      4 months ago

      The app allows you to use server side “hide read posts” so it doesn’t stop users from using the server-sided implementation. But, some features in the app do not work well this the server-sided implementation.

      • Björn@swg-empire.de
        2·
        4 months ago

        The trouble with the setting from Lemmy-Web is that you cannot toggle the hiding and showing on the fly. But they added that as dynamic filter options to the API a few versions ago. Those filters even work independent of what the user has set in Lemmy-Web.

        So you could send those options over, depending on what the user has selected in Summit. And it will send exactly those posts over the user wants to see. And if the server is too old to support the filters they should just be ignored and Summit can fall back to its own implementation or what is selected in Lemmy-Web.

        I honestly think they never should have let the Lemmy-Web option be saved on the server. It should have been UI-only. That is what has landed us in this mess in the first place. Hope they remove it with 1.0 because it’s just confusing.