The focus of this release is to add support for importing/exporting tables from the database of the app.

A lot of preferences/data, especially those that allow you to add to a list, are built on top of tables. Tables allows the app to scale better when lists can grow very long. Some features that use tables include drafts and bookmarked communities.

Currently while the app allows users to import/export settings, the app does not give the user any way to import/export anything backed by tables. This means not everything can be carried over by importing/exporting settings.

This release aims to give users a way to preview the database within the app and export them and import them with a high level of configurability.

This feature is a prerequisite of a larger feature which will be announced later.

Changes so far

  • Fix a bug where links do not open correctly if the default browser app is Firefox.
  • Fix a bug where the post feed header does not update when switching instances.
  • Fix a bug where rate limit errors are not recognized correctly.
  • Fix a bug where “mark posts as read on scroll” doesn’t mark a post as read if the height of the post is taller than the screen.
  • Improve performance of “mark posts as read on scroll” slightly.
  • Updated community search result to show the full community name with instance.
  • Add support to import/export preferences/app data that are stored in tables.
  • Remove malformed markdown fix which tried to correct malformed headlines by inserting a space between ‘#’ and text if there wasn’t one.
  • Change open instance behavior. If the instance opened does not match the current account, the guest account is used automatically. This is to prevent the app from getting into a weird state.
  • idunnololzOPM
    9·
    8 days ago

    I want to complain about this so I’m doing to do it in the comments instead of the post.

    While in the post I use the wording “Fix a bug” for the firefox issue, really it’s more accurate to say that I added a workaround because Firefox did not adhere to Android standards and the way they handle external requests to open URLs is IMO unreasonable. In any case this issue will be fixed in the next release (that is until Firefox app decides to change how they handle URLs again). (Yeah I’m salty I had to search for a solution for 30 minutes to this problem).

    • drzoidberg
      2·
      7 days ago

      I’m sorry! I never World have said anything if I knew it was cause Firefox was being a dick of an app!

    • neatducky@lemmy.zip
      3·
      8 days ago

      I was contemplating making a post about the firefox issue before i did some searching and figured out it was a long-standing firefox bug. Glad there was a work around though! Would this fix also apply to Firefox Focus (which faces the same problem since it uses firefox as a base)? Its alright if it doesn’t, since i can get firefox to do what focus does if needed.

      • idunnololzOPM
        3·
        8 days ago

        I did not test with firefox focus. I can test with it later today.