Hi Everyone!

We’re now running the latest lemmy 0.19 release, you can see more details here: https://lemmy.ca/post/11378137

Note that you will need to re-enable 2FA on your account, all users had it turned off as part of this

You will most likely need to log out and back in for your client to work properly.

  • DerisionConsulting@lemmy.ca
    link
    fedilink
    English
    arrow-up
    9
    ·
    11 months ago

    Is there any way to turn off the gold highlight on new comments? It makes things harder to read, and it’s also quite ugly.

    • Otter@lemmy.ca
      link
      fedilink
      English
      arrow-up
      5
      ·
      11 months ago

      Yea I’ve noticed that too, I have been refreshing the page to get rid of them

      • DerisionConsulting@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        11 months ago

        I am using Lemmy.ca without loading any different themes, and it looks like the ugly gold does not highlight new comments anymore. Did the admin team change something?

        The only remaining ugly-gold comments I have seen are ones that have the admin shield on them.

        Edit: Never mind, this comment now shows as ugly-gold for me, as did another that I saw that was 8 minutes old.

        • m-p{3}@lemmy.ca
          link
          fedilink
          English
          arrow-up
          5
          arrow-down
          1
          ·
          11 months ago

          I’m looking into building a temporary custom theme for both darkly and litely that removes this highlight, at least until there’s an option to disable that feature.

    • TheWaterGod@lemmy.ca
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      11 months ago

      This is the thing I’m happiest to see and I hope it helps Lemmy grow more. Being able to block the NSFW/porn instances is such a quality-of-life improvement. I’ve got nothing against porn, but it’s a bad look if anyone can see your screen and every third post is nudity (even if it’s blurred).

      • m-p{3}@lemmy.ca
        link
        fedilink
        English
        arrow-up
        6
        ·
        11 months ago

        Same, I still want to see some non-pr0n NFSW stuff so that really helps.

      • zcd@lemmy.ca
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        1
        ·
        11 months ago

        Oh this already exists, you can block all NSFW posts

        • TheWaterGod@lemmy.ca
          link
          fedilink
          English
          arrow-up
          10
          ·
          11 months ago

          I’ve seen that option but unfortunately not every NSFW post is NSFW because of nudity. Like some of the post in the Ukraine community are marked NSFW for war reasons.

  • Pxtl@lemmy.ca
    link
    fedilink
    English
    arrow-up
    6
    ·
    11 months ago

    The highlight on new comments is ugly as sin. Do not want.

      • FiveMacs@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        11 months ago

        Me not knowing wtf you guys are talking about with this ugly gold thing that has never shown on my jerboa program on my phone

  • Troy@lemmy.ca
    link
    fedilink
    English
    arrow-up
    6
    ·
    11 months ago

    I am really liking Scales, Auto Expand Media, and Open in new Tab. Very nice QoL improvements.

  • Avid Amoeba@lemmy.ca
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    11 months ago

    I got Jerboa 0.0.54 via the Play Store. F-Droid seems to still be on 0.0.52.

    Update

    The Subscribed view consistently fails to load additional posts. When I tried to add a screenshot to this post it gave me an “incorrect_login” toast. Adding text seems fine. 🤔

    Adding a pic via the web app works fine:

    Update 2

    It seems like they were both fixed today:

    They haven’t been released yet.

    Update 3

    And now w patiently await 0.0.55 to reach the stores.

    Update 4

    Aaand released:

    Uploading images works. So does the Subscribed view.

    It looks like this concludes the saga of the 0.19 release and Jerboa. 😅

    • grte@lemmy.ca
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      11 months ago

      F-Droid seems to still be on 0.0.52

      You may need to update you repositories. It’s been on .54 for a couple days.

      [edit] Scratch that, I had added a repo which had the updated version sooner and forgot about it.

  • Avid Amoeba@lemmy.ca
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    11 months ago

    Auto expand media is awesome! Shitpost scrolling on the desktop just got elevated.

  • Arghblarg@lemmy.ca
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    11 months ago

    Cool!

    However, I notice upvote/downvote and community block actions appear to break when using old.lemmy.ca on desktop (guess whomever maintains that theme has work to do… just noting here).

    EDIT: Whoops, my bad for not reading further down, others have reported. Thanks.

  • Jay@lemmy.ca
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    11 months ago

    old.lemmy.ca is having issues with the update as well. voting doesn’t seem to always work, and I couldn’t post from it. Not a huge deal, there’s always the normal mode.

  • Avid Amoeba@lemmy.ca
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    11 months ago

    Note that Jerboa 0.50 which is still the latest in the Play Store is broken with Lemmy 0.19. The newly released 0.53 should work but it’s not on the stores yet.

    Suggestion:

    Check that the compatible Jerboa version is on the Play Store before upgrading Lemmy. That way non-technical users like my wife won’t see breakage. Or alternatively upgrade several days after the official Lemmy release.

    • m-p{3}@lemmy.ca
      link
      fedilink
      English
      arrow-up
      6
      ·
      11 months ago

      Yeah, lesson learned :/

      I’ll compile a list of apps and see how we can track which one are ready for any API breaking changes before we do the server update.

      • Avid Amoeba@lemmy.ca
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        11 months ago

        I’d just delay the update for a few days up to a week. That would give a chance for most maintained apps to release updates via their respective channels. Then I wouldn’t have to care and check for specific apps.

        • Shadow@lemmy.caOPM
          link
          fedilink
          English
          arrow-up
          6
          ·
          11 months ago

          The app developers were warned like a month ago that this would be a breaking change, they had lots of time to release patches and there’s been a few large instances on the beta of 0.19 for well over a week.

          IMHO It’s not really sensible for us to go test the apps and then hold back on upgrading just because one of the dozen apps isn’t compatible yet.

          • m-p{3}@lemmy.ca
            link
            fedilink
            English
            arrow-up
            2
            ·
            11 months ago

            What’s even worse is that the Jerboa developer is one of the Lemmy dev, he could litterally see this coming a mile away :/

            But on the other hand he’s at the mercy of Google making the update available whenever they feel like it.

          • Avid Amoeba@lemmy.ca
            link
            fedilink
            English
            arrow-up
            1
            ·
            11 months ago

            It’s why I wouldn’t test at all. I’d just wait a bit. Or I’d update after Lemmy.world updates. 😅 Little extra work that way.

        • Avid Amoeba@lemmy.ca
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          11 months ago

          Importantly, the signatures of the F-Droid build is different than the one from Github, is different than the one for the Play Store. As a result, you can’t update an app installed from one of these sources with a build from another. 😮‍💨

  • droopy4096@lemmy.ca
    link
    fedilink
    English
    arrow-up
    4
    ·
    11 months ago

    Voyager seems to be OK after upgrade, Eternity however spits 404 errors on upvotes etc

        • Otter@lemmy.ca
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          11 months ago

          My understanding is that every app and frontend should have required a quick log out/log in after this upgrade since the authentication stuff was upgraded. So it might be good to do that on Voyager as well, or keep an eye out for issues

          It’s annoying though I agree