Announcements

765 readers

1 users here now

Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.

You can also find major news on join-lemmy.org

founded 5 years ago

MODERATORS

[email protected]

286

Lemmy 0.18 is ready for testing (lemmy.ml)

submitted 1 year ago by [email protected] to c/[email protected]

61 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 5 points 1 year ago (1 children)

This is a UI issue. As a temporary solution, you can modify the post (maxlength) using your browser's dev tools until lemmy devs implement a fix.

[–] citizen67 1 points 1 year ago* (last edited 1 year ago)

I'm not having any luck with that solution. Can you please explain further?

The v0.18 test instance is already showing maxlength="50000" in the post body textarea and still failing with invalid_body_field for any posts over 10K chars. The github issues above mention that it's the backend that is limited to 10K.