Hi, thanks for all the great feedback on the last release. This release brings hide post functionality and improvements to the about instance page.

We also hit 20k active users! That’s an amazing milestone for only being live for about 2 weeks. I’m going to be working on a ‘New to Lemmy’ onboarding page as Connect is often the first place for new users. Also customization for swipe actions is high on my list to do.

What’s new

  • Smoother swipe navigation on certain pages
  • Fixed typo in Settings page (Affects -> Effects)
  • Made scrolling up smoother in full width view
  • Added ability to hide posts (it’s both the last swipe action and on the hamburger menu)
  • Added a list of communities to the instance about pages
  • Added user avatar to the drawer header
  • Vibrate on comment collapse/uncollapse

Bugfixes

  • Fixed a bug with getting next page is the entire first page is filtered
  • Fixed a bug for users with >100 subscriptions
  • Fixed a bug with sort values not taking effect -Changed the app name on the homescreen to just ‘Connect’
  • Added a notification outside of drawer
  • Fixed a bug where sometimes comment replies wouldn’t show the comment being replied to
  • Addressing some logo feedback, I’ve removed the outer white ring

edit: 1.0.58 hotfix is waiting on Google Play approval now which fixes a couldnt_load_comment bug.

Links:

-kuroneko

  • KuroOPM
    3·
    1 year ago

    Is that on a certain instance? I just tried it on a couple servers and it seems working

    • s6original@lemm.ee
      5·
      1 year ago

      Seems everywhere to me. Page briefly displays before displaying “couldn’t get content”.

      • Xepher@lemm.ee
        3·
        1 year ago

        Having the same issue here. Can’t load comments from any instances I’ve tried. My home instance is lemm.ee if that matters.

        • KuroOPM
          10·
          1 year ago

          Ok thanks! I’m rolling out a hotfix now (should be live in about 2 hours). I see lemm.ee is on API version 0.18.1-rc.4 so my suspicion is any instance on that version will have this issue. (The issue was that Connect was trying to load too many comments at one time, which was okay prior to today).