Here is our regular update that explains what we have been working on for the past two weeks. This should allow average users to keep up with development, without reading Github comments or knowing how to program.

In case you missed the announcement, this week we launched a redesign of join-lemmy.org together with our first annual funding drive. Please consider donating to support Lemmy development.

We are also readying another release candidate 0.19.0-rc.4. As usual it is available for testing on voyager.lemmy.ml and by installing the Docker image on your server. There are no breaking changes this time as we are preparing for the final release. It has been one month since we announced the major breaking changes for 0.19. In that sense we would like to know from developers of Lemmy clients and frontends if their projects are ready for 0.19, as we are planning to release it within the next weeks. There is no specific release date, but we will first update lemmy.ml to a release candidate, and if it works well publish the new release shortly after.

@nutomic is implementing a proxy for remote images, so that clients don’t have to connect directly to remote servers and avoid leaking personal information. He also added support for Arabic and Cyrillic usernames and community names. Additionally he made various smaller changes and code rewrites, such as ordering reports and registration applications by oldest first.

@dessalines has implemented numerous minor bug fixes and enhancements. This includes disabling voting for bot accounts, a change to the hot rank to avoid content getting pushed off the feed after mass downvoting, and more. Also added an Platform filter for the join-lemmy.org/apps page, and fixed a memory issue.

@phiresky is extending the /api/v3/site/federated_instances endpoint to include error count and time of last successful send for each linked instance. This will allow determining the exact state of federation between all instances.

@SleeplessOne1917 made two minor improvements to 2FA code input and to the search page.

@hackerncoder relaxed the check for valid displaynames to allow more unicode symbols.

Support development

@dessalines and @nutomic are working full-time on Lemmy to integrate community contributions, fix bugs, optimize performance and much more. This work is funded exclusively through donations.

If you like using Lemmy, and want to make sure that we will always be available to work full time building it, consider donating to support its development. Recurring donations are ideal because they allow for long-term planning. But also one-time donations of any amount help us.

  • aeharding@lemmy.worldEnglish
    35·
    1 year ago

    Thanks for your hard work!

    we would like to know from developers of Lemmy clients and frontends if their projects are ready for 0.19

    Voyager is ready :)

  • Admiral Patrick@dubvee.orgEnglish
    10·
    1 year ago

    Tesseract is ready, though current release is still in backwards-compatible mode for 0.18.x (none of the new 0.19 API features are enabled, but all primary functionality is tested against 0.19.0).

    However, it does have issues with the /comment/report/list and /post/report/list endpoints as well as /user/report_count. However, those are also throwing the same HTTP 400 errors as with Lemmy-UI 0.19.0-rc.4 (tested against voyager.lemmy.ml).

    The first two throw a 400 with the error not_an_admin even though I am moderating a community.

    I assume those are known issues?

  • aprnu@feddit.chEnglish
    9·
    1 year ago

    Thanks for the update.

    sidenote: just want to let you know that ampersand symbol [&] used in post titles does not display correctly (browsers, not apps)

  • Max-P@lemmy.max-p.meEnglish
    8·
    1 year ago

    Boost for Lemmy doesn’t appear to be, last update was in September.

    I’ve been using a custom proxy to rewrite auth for Boost to work since my accidental 0.19 update. It’s been working great considering how quick and dirty it is.

    My partner also reports the Mlem chokes completely on 0.19’s JSON response. I suspect fields were added and it’s not coded to ignore extra fields when deserializing. I haven’t confirmed it’s still present on rc4, I’ll update my instance and report back. Edit: confirm Mlem still doesn’t work even with the proxy hack. Without the hack it can’t authenticate at all. Latest git main branch might, this is based on the 1.1 current release which is about a month old.

  • gkd@lemmy.mlEnglish
    4·
    1 year ago

    Serious thanks for all of your hard work, as well as everyone else working on Lemmy through software of running instances.

    Memmy is ready 👍

  • darklightxi@lemmy.worldEnglish
    4·
    1 year ago

    Thanks again for all the updates!

    In that sense we would like to know from developers of Lemmy clients and frontends if their projects are ready for 0.19, as we are planning to release it within the next weeks.

    Thunder is ready to go!