The new major version of Lemmy is now ready, and we need your help with testing. Most importantly it uses HTTP for API requests now, which is much more efficient than websocket. Additionally Two-factor-auth is supported. There are also countless other improvements and bug fixes.

You can register on any of the following servers to start testing, no approval required. You can post to your hearts content to find out if anything is broken. The test instances only federate with each other to avoid affecting production instances with spam.

If you encounter any bugs that aren’t present in 0.17, open an issue and mention in the title that it happened with a release candicate version. Over the next days we will publish new RC versions to fix bugs that will invariably pop up.

Instance admins can try the new version by using Docker images dessalines/lemmy-ui:0.18.0-rc.2 and dessalines/lemmy:0.18.0-rc.1. Make sure that working backups are in place. For production instances its better to wait at least some days for the major issues to be fixed.

  • Ulu-Mulu-no-die
    link
    English
    15
    edit-2
    2 years ago

    Appending the char “!” to the password gives the error “SyntaxError: JSON parse: unexpected character at line 1 column 1 of the JSON data” - same screenshots posted by @Lodion - that’s on Enterprise (haven’t tried other instances yet).

    Removing the ! let me create my user just fine.

    Edit: oh just saw mod message, will wait for next build then try again.

    Edit2: adding the ! to the password now works

    • @[email protected]
      link
      fedilink
      English
      32 years ago

      Oh that kinda seems like a bad sign regarding proper data validation. Hopefully it’s just a small bug and not part of a larger issue.

      • @atimholt
        link
        English
        12 years ago

        I heard someone say that you can’t make your password too long. Does not bode well. I use a unique password, at least.

      • Ulu-Mulu-no-die
        link
        English
        12 years ago

        It was a small bug, apparently a bad PR merged by mistake.