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.

  • sub_ubiEnglish
    10·
    11 months ago

    Proud to be on the official test server 🥲

    • DessalinesOPMEnglish
      10·
      11 months ago

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

  • Omega_HaxorsEnglish
    00·
    11 months ago

    Yes yes yes yes yes yes yes yes I can finally make those shitty instances go bye-bye

          • Omega_HaxorsEnglish
            00·
            11 months ago

            Yeah the latest update gives you the ability to block instances outright, so if you’re an antifascist you can block all the .de instances and not have to deal with weird posts constantly showing up from there whenever you talk about the nazis.

  • TiredNerdDadEnglish
    00·
    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