The community got the required number of votes to force me to add PieFed support which is what this release will be focused on.

This has the potential to be a huge change. At the time of writing, I’m still doing exploration work so I’m not sure how long it will take. It could take a couple of days or a couple of weeks depending on what I find.

In the meantime, I did fix some bugs.

Changelog so far

  • Fix a bug where when you open a post, the spinner will appear to stutter for a moment.
  • Fix a bug where pulling to refresh on the post screen will cause all comments to refresh even if they have not changed.
  • Fix a bug where inline images will sometimes not load until the screen is refreshed.
  • Fix a bug where “Prev” button doesn’t load the page if pressed on page 2 when Infinity mode is off.
  • Add support for PieFed.

Update

Wrapping up PieFed support. Current release ETA is tomorrow (July 15th, evening). The main known bug at the moment (that I will not address) is that certain fields on PieFed use HTML instead of Markdown. The fix isn’t hard, it just requires the app to include some dependencies that will increase the app size. Once PieFed is more stable, I’ll add support for HTML then but for the time being I will hold off on HTML support.

  • mintiefresh@piefed.caEnglish
    4·
    3 days ago

    Thanks!

    I’m really excited to see piefed support coming.

    It feels like the right time with all the new piefed instances popping up. Right now I’m using Voyager because they added support a few weeks ago.

    But having support here will be great to give us more options.

  • Wrufieotnak@feddit.org
    1·
    3 days ago

    Hi, I seem to have a problem since today: when I edit a comment, it is shown as failed in the user page with

    unknown error, 400 key:"

    Strangely it shows the edited comment when I am in the post directly, but if I read it while coming from the inbox and clicking on “context” there, I see the old unedited comment.