Hi Boost gang! I’ve just uploaded a new version. This is the changelog:

  • Improved Create Post screen, with image upload and automatic title suggestion from url
  • Edit posts including text, title, image or link
  • Block instances (For instances running Lemmy 0.19). In posts, long press community name or 3-dots -> Block -> Block instance
  • Scaled and Controversial sort (For instances running Lemmy 0.19)
  • Support for Lemmy links (!community@instance and @user@instance)
  • Autocomplete communities after typing ! when composing text
  • Better performance for images embedded in comments
  • Removed karma count from profiles (Lemmy 0.19 does not have karma)
  • Fix reporting comments from inbox
  • Bug fixes and small improvements

I would appreciate it if you could test the new features and leave your feedback in the comments.

Thanks for your support!

Rubén

  • @PandaEnglish
    1•5 months ago

    I’m not sure if it’s the new version, but for some reason my account on this instance (programming.dev) doesn’t seem to work properly in Boost, whereas it worked fine before (before meaning earlier this week).

    When I look at my feed (which is set to ‘Subscribed’) it seems to show posts from all communities instead. And when I try to make a post or comment it says something about the login being invalid. I can still see my profile in Boost, though, and I can even open them for editing. Edit: when I try to post something through the app I get a ‘401 Invalid Login’ error message even though I’m logged in.

    It works fine on the other instance I’m in so if seems to be specific to this instance? (I’m posting this from the website, because Boost won’t let me post it from there).

    Thanks for this great app. I loved the Reddit version and I am loving this one as well!

    • RubénOPMEnglish
      2•5 months ago

      Lemmy invalidates all login sessions after an instance migrates to Lemmy 0.19. This means you will need to login again in Boost.

      • @PandaEnglish
        2•5 months ago

        Ah thank you (and thanks for the quick response!)! That indeed fixed it and it explains why it still works on my account on the other instance.