In anticipation of Lemmy’s upcoming 0.19 release, and to work out any final issues, we’re going to deploy a test release on lemmy.ml within the next few days.

We’re doing this testing on lemmy.ml only, so that we can encounter any issues before the release, and to make sure the upgrade process is smooth for other production servers.

Some of the following will happen during the process:

  • Apps will likely break (only for lemmy.ml)
  • Lemmy.ml may experience some downtime for the upgrade to complete (ideally no more than an hour).
  • If anything goes wrong, we may have to restore from a database backup, meaning content made in between backups may be lost.

If all goes well, we’ll have an official announcement for the release after this testing period.

I apologize for the difficulties this might cause. At most this will be a week of hair-pulling, but its vital that we catch any issues before telling other servers to upgrade.

    • Dessalines@lemmy.mlOPMEnglish
      1·
      2 years ago

      haha, we appreciate the patience. We’re not a massive company with teams of people, just a couple of FOSS programmers.

      • Wes_Dev@lemmy.mlEnglish
        0·
        2 years ago

        Thanks everyone for the server and service. It’s appreciated. If I wasn’t broke and jobless at the moment, I’d be happy to kick over some monthly money on Patreon or Kofi or whatever people are using these days.

  • auth@lemmy.mlEnglish
    0·
    2 years ago

    When I vote on a story while not logged in, it silently fails on 0.19-rc8

    • Dessalines@lemmy.mlOPMEnglish
      0·
      2 years ago

      The release? 🤞 not more than a week, as long as we don’t run into major issues.

    • highduc@lemmy.mlEnglish
      0·
      2 years ago

      This happened to me once, shortly after joining lemmy. I even took a screenshot as proof :) Glad somebody else can confirm it’s actually a thing.

    • Dessalines@lemmy.mlOPMEnglish
      0·
      2 years ago

      I think someone we’ve seen this bug a long time ago, but its difficult to replicate.

  • pixelscript@lemmy.mlEnglish
    0·
    2 years ago

    I seem to have been screwed over by TOTP.

    Hearing that this update was supposed to make borking your account harder to do when setting it up, I enabled it. Put the secret in my authenticator app, got my six digit code, and away I went.

    Now, a few days later, having changed nothing on my end, Lemmy.ml won’t accept my TOTP code. My session token on desktop is expired so I can’t remove it now.

    Currently my only lifeline to this account is my logged in session in Voyager, which, as far as I can tell, cannot access the TOTP setting. (Or any profile setting, for that matter… am I just stupid?)

    No email to recover from, either. That’s on me, I guess. Ugh.

    Not sure what my recourse is, if I even have any.

      • pixelscript@lemmy.mlEnglish
        0·
        2 years ago

        Connect, Sync, and Boost all told me to go kick rocks.

        Evidently, whatever happened, it doesn’t seem to be an issue with your platform.

        • silas@programming.devEnglish
          0·
          2 years ago

          Ok, and you’re getting a new 6-digit code from your authenticator app every time you attempt to log in?

          • pixelscript@lemmy.mlEnglish
            0·
            2 years ago

            Yes.

            I noticed my authenticator app (KeePassXC) offers the ability to customize the TOTP parameters (SHA function, time step, code size). But no combination of settings seems to produce a valid code.

            I assume Lemmy uses the suggested defaults in the RFC 6238 standard?

  • Samsy@lemmy.mlEnglish
    0·
    2 years ago

    I have two accounts, one on feddit.de which runs stable all the time. But my older account here on lemmy.ml seems broken in the last week:

    • I can’t see my own new posts in profile, comments work.
    • post and comment upvote-count is at zero.
    • log in with jerboa let the app crash.
    • yo_scottie_oh@lemmy.mlEnglish
      0·
      2 years ago

      I was having this issue initially as well, but today I noticed my posts are back. Are yours back, too?

      • Samsy@lemmy.mlEnglish
        0·
        2 years ago

        I read your comment, checked my profile, and you are right, posts are back.

    • Che Banana@lemmy.mlEnglish
      0·
      2 years ago

      I keep getting the “failed to verify JWT token” and am using a mobile browser to log in/post.

  • nar@lemmy.mlEnglish
    0·
    2 years ago

    I was just wondering: Instead of testing these potentially disruptive changes on the main website, why wouldn’t you make some testing instances where people can try everything out, like voyager, enterprise, and ds9 were back in the day?

    • 7heo@lemmy.mlEnglish
      0·
      2 years ago

      Yep, I’ve been enraged by this decision from day one. This is depressingly amateur. Let people join, let other developers make very cool apps, and then introduce a deeply breaking change in a minor version, and deploy it on the most active instance, with mere days of warning. Or “How to destroy all the progress made by Lemmy, in one small change”.

      I get it if the devs and admins of Lemmy.ml are paying too much out of their own pocket, and if they want users to literally go away, to mitigate that cost.

      But doing it in such an in such an insidious, demoralizing way, as opposed to being transparent with the costs and announcing (drastic) measures to mitigate that cost, is literally destroying most of the progress made so far, and driving most users back to reddit.

      As of today, the list of most active servers of the fediverse has only one Lemmy server (Lemmy.world), in ninth position, and that is the only Lemmy server in that list, over four pages… The Lemmy instances used to be in the middle of the first first 10 instances, with Lemmy.ml leading the way.

      Now, I guess the devs didn’t want to take those drastic measures, and tell people to they would be closing down their accounts, ordered by creation date, until the costs become bearable again. Because that would mean “admitting the Lemmy.ml experiment to show the world that people are, when given the opportunity, rising to the challenge, and putting in the effort, in true communist fashion, is actually a failure”. People aren’t ready for communism. Communism requires education, intelligence, and empathy/compassion. Our western societies are fostering the opposite traits. When we become educated, intelligent, and empathic or compassionate, it is in spite of our societies, not thanks to them.

      Now, a few people opened instances, but it wasn’t enough, and fast enough, when the “reddit migration” happened, to absorb the insane influx of users to Lemmy.ml.

      So I guess it is what it is, but it’s still sad and depressing…

    • davel@lemmy.mlEnglish
      0·
      2 years ago

      I don’t think this is a bad suggestion, but it’s worth noting that lemmy.ml is explicitly intended not to be the “main” Lemmy, or even a major one: What is lemmy.ml?

  • blawsybogsy@lemmy.mlEnglish
    0·
    2 years ago

    EDIT: all good, I worked it out, I found some other api docs.

    Is the ModeratorView listing type in this release? If so what feed view is it available in? I can’t see it in the lemmy.ml webUI at the moment, nor in the API docs, but the code is merged.

    • 𝘋𝘪𝘳𝘬@lemmy.mlEnglish
      0·
      2 years ago

      You can finally block lemmygrad and hexbear as a whole for your account without having your instance’s admin to defederate them.

        • 𝘋𝘪𝘳𝘬@lemmy.mlEnglish
          0·
          2 years ago

          it doesn’t block comments from instance users, only posts

          Which is enough for me.

          which could already be archived by using apps

          And that’s the thing here: You don’t need any apps anymore because it is implemented serverside. I am also not a fan of apps in general (they don’t fit my “workflow”).

        • 𝘋𝘪𝘳𝘬@lemmy.mlEnglish
          0·
          2 years ago

          Naming other instances (especially those two instances) is illegal now I guess 🤣

          But I am pretty sure everyone knows what “those two” instances are, anyways.

          • Omega_Haxors@lemmy.mlEnglish
            0·
            2 years ago

            Blatant displays of anticommunism are not allowed on lemmy ml

            It’s the bare minimum they do to ensure it doesn’t just become another nazi bar instance.

            • 𝘋𝘪𝘳𝘬@lemmy.mlEnglish
              0·
              2 years ago

              If those two instances are seen as problematic by the mods of an official community I wonder why lemmy.ml is not defederated from them. lemmy.ml is defederated from so many weird/extremist instances, why not from those two?

              But this is the announcement community, we should not discuss this here since it’s off topic.

              • Omega_Haxors@lemmy.mlEnglish
                0·
                2 years ago

                ml is basically the omni-instance, the only places it’s defederated from are those which outright should not exist on the federation. I’m talking unmoderated, hate speech galore, and CSAM posted on the daily. The only thing ml defederates from outside that are porn instances. I joined a NSFW instance and tbh not missing out on much, it’s mostly commercial spam and a lot of… questionable stuff.

    • Die4Ever@programming.devEnglish
      0·
      2 years ago

      I think scaled sort and instance blocking are the biggest new features, lots of little tweaks and bug fixes too

    • CannotSleep420@lemmygrad.mlEnglish
      0·
      2 years ago

      Some that come to mind:

      • Scaled sort, which takes community size into consideration when looking for top posts
      • User will be able to block instances without the need for their home instance to defederate
      • The new flow for enabling 2FA makes it harder for users to accidentally lock themselves out of their accounts
      • There will be a feed option to just see posts in communities you moderate (as opposed to subscribed, local, and all)
      • Controversial sort
      • You can import and export account settings as JSON, making switching instances easier