Add support for PieFed.

Full changelog

  • Add support for PieFed.
  • 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.

Update

Fix some bugs and re-releasing as v1.67.1

  • Add some default PieFed instances to the login form auto-complete.
  • Fix a bug where you can’t log into PieFed with a password with more than 60 characters.

Update 2

Release should be fully rolled out now.

Update 3

Fix more bugs and releasing the fixes as v1.67.2.

  • Fix a bug on PieFed where updating a comment/post will not refresh the comment/post.
  • Fix a bug where uploading an image will fail with an error.
  • Fix a bug on PieFed where opening a comment will sometimes error.
  • Fix a bug on PieFed where Webp files cannot be uploaded.

Update 3

Fix more bugs and releasing the fixes as v1.67.3.

  • Fix a bug that prevents updating posts/comments on instances that do not allow content to use the Undetermined language id.

Update 4

Fix more bugs and releasing the fixes as v1.67.4.

  • Fix a bug where sending a comment to a post will cause weird behavior. Eg. comments being orphaned randomly.
  • Fix a rare bug where a website might be mis-identified. Eg. a regular website being identified as a lemmy server.
  • idunnololz@lemmy.worldOPM
    2·
    20 days ago

    Oh I just realized that you are getting a 504, not a 404. This means that the lemmy.zip server isn’t returning anything back.

    Can you try changing the user-agent, then restart the app and see if that fixes the issue?

    To change the user-agent, go to Settings > Misc > Client user-agent. I would try Test user-agent and Test user-agent 2 first but you should try them all until it works.

    • almost1337@lemmy.zip
      3·
      19 days ago

      For whatever reason 1.67.4 seems to have resolved things? Maybe just the app actually restarting was the fix. I’ll definitely give the user agent switch a try if I see the same issue again.

    • almost1337@lemmy.zip
      1·
      16 days ago

      Following up on this one, I am still seeing this issue intermittently, but doing a force stop and restarting the app does fix it.