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
      6·
      11 months ago

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

      • Joliflower@lemmy.mlEnglish
        02·
        11 months ago

        Start monetizing with features and donations. Being Foss doesn’t exclude this

  • nar@lemmy.mlEnglish
    8·
    11 months 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?

    • davel@lemmy.mlEnglish
      7·
      11 months 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?

    • 7heo@lemmy.mlEnglish
      54·
      11 months 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…

    • Dessalines@lemmy.mlOPMEnglish
      11·
      11 months ago

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

  • pixelscript@lemmy.mlEnglish
    3·
    11 months 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
        1·
        11 months 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
          1·
          11 months 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
            2·
            11 months 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?

    • Nooz3@lemmy.mlEnglish
      1·
      11 months ago

      I think using an authenticator app capable of generating codes using SHA256 might do the trick if you have any possibility to try that.

  • Samsy@lemmy.mlEnglish
    2·
    11 months 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.

    Edit: last one got fixed with new jerboa update

    • Che Banana@lemmy.mlEnglish
      21·
      11 months ago

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

    • yo_scottie_oh@lemmy.mlEnglish
      0·
      11 months ago

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

      • Samsy@lemmy.mlEnglish
        2·
        11 months ago

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

  • blawsybogsy@lemmy.mlEnglish
    31·
    11 months 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.

  • ryn@lemmy.mlEnglish
    1·
    11 months ago

    I got randomly signed out this morning, maybe this has something to do with that.

  • yamaonan@lemmy.mlEnglish
    21·
    11 months ago

    Has anyone experienced trouble logging in through Jerboa app? Jerboa crashes every time I try to log into this instance, but other instances log in fine.

    • pixelscript@lemmy.mlEnglish
      3·
      11 months ago

      Creators of Lemmy, owners of this instance, and creators of the Jerboa app are all the same people. As I understand it, Jerboa won’t be getting an update until they’re happy with the stability of the update to Lemmy itself. Lemmy is getting all the focus first. Also, no sense in pushing a client update for a server update that itself is not finished.

      Getting really annoyed at that error toast in Jerboa, though, not gonna lie. And not being able to post on mobile. At least I can still read posts and comments, though. Hopefully the patch will release soon.

      • el_abuelo@lemmy.mlEnglish
        21·
        11 months ago

        Yeay this was the update that killed Jerboa for me.

        Now on Voyager which seems much nicer. And actually works.

        • pixelscript@lemmy.mlEnglish
          2·
          11 months ago

          Thank you for the suggestion of Voyager, I have installed it and it looks quite nice!

    • Vladomo@lemmy.mlEnglish
      1·
      11 months ago

      Yes, the exact same was happening for me. Jerboa would crash and android would show me the notification “this app has a bug” whenever I tried to login. Now using Eternity for Lemmy and that is working smoothly.

  • Faresh@lemmy.mlEnglish
    1·
    11 months ago

    When I open lemmy, it automatically seems to go to the global screen, but still displays the “subscribed” tab as being selected.

    I’m subscribed to neither the piracy, nor the world news nor the gay news communities.

  • TiredNerdDad@lemmy.mlEnglish
    1·
    11 months ago

    Thought I’d mention a problem (re: Apps will likely break (only for lemmy.ml)) I am developing an app and this one request stopped working:

    https://lemmy.ml/api/v3/community/list?type_=Subscribed&auth=[MY_AUTH]&username=[MY_USERNAME]&limit=50

    Any other type_ works. This one used to return only a users Subscribed communities but it just returns an empty array {"communities":[]}. When you load it up in a browser it works. I’m driving myself crazy

  • SlicingBot@lemmy.mlEnglish
    1·
    11 months ago

    How much longer will it be before I can finally log in and use boost or liftoff. Is there a timeline for a fix? Both have been broken since the update.