Since our last release earlier this month, we’ve had ~30 commits to Lemmy.

Major Changes

  • Added comment and post reporting in the front end, and cleaned up the reporting API.
    • Note: these are local-only currently, reports are not yet federated.
  • The JWT secret is now auto-generated by the database.
    • Note: this will log out all users, so users will have to log in again.
  • Lots of smaller UI fixes listed below.

Upgrade notes

Servers

If you’d like to make a DB backup before upgrading, follow this guide.

To upgrade your instance to v0.13.0, simply follow the instructions in the documentation:

Changes

Lemmy Server

General

  • Adding a user agent. Fixes #1769
  • Ansible changes (#1781)
  • Clean up reporting (#1776)
  • Implement webmention support (fixes #1395)
  • Move jwt secret from config to database (fixes #1728)
  • Set a 10 char minimum password length.
  • Dont pass accept-encoding header to pictrs (ref #1734) (#1738)

API

  • There are no breaking API changes, only the addition of reporting endpoints.
  • A full list of the API changes can be seen on this diff of lemmy-js-client: 0.12.0 -> 0.13.0 .

Federation

  • Rewrite fetcher (#1792)

Lemmy UI

  • Adding bn, ml, and cs langs
  • Reporting (#434)
  • Splitting login and signup pages. Fixes #386 (#431)
  • Fixing image in newtab. Fixes #382 (#430)
  • Navigate away from login page if already logged in. (#429)
  • Add username validation message. Fixes #387 (#428)
  • Password strength meter (#427)
  • Fix community display name overflow. Fixes #390 (#425)
  • Fix logout bug. Fixes #391 (#424)
  • Fix up post, profile and community forms. Fixes #409 (#423)
  • Adding markdown audio and video embeds. Fixes #420 (#421)
  • Adding Si simplifier (#418)
  • Fix profile paging. Fixes #416 (#417)
  • Use my fork of inferno-i18next. Fixes #413 (#415)
  • Add version to package.json . Fixes #411
  • je_vv@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    3 years ago

    The theme (darkly or the web browser one) are not respected), and web looks horribly white, :(

    Had to use “dark reader” extension… I’m using librewolf 92.01, but this hadn’t happened before, :(

    • Dessalines@lemmy.mlOPM
      link
      fedilink
      arrow-up
      3
      ·
      3 years ago

      2 ways to change it:

      • Use a browser that supports dark mode, and make sure your theme in your user settings is Browser Default (which it should be by default.
      • Manually change your theme in settings to darkly.
      • je_vv@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        3 years ago

        I think I found the issue. Only darkly is working for me, and I have to refresh or course… Somehow LibreWolf (Firefox derivative) with default dark theme, is not picked by Lemmy. I’m using materia dark theme on the system, and it’s what LibreWolf is picking… So, that’s what’s not working. Darkly does it though…

        • Dessalines@lemmy.mlOPM
          link
          fedilink
          arrow-up
          1
          ·
          3 years ago

          The prefers color scheme that browsers have now, only has light and dark mode currently.

      • je_vv@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        3 years ago

        It was sort of weird, I did that on the the front page and seemed to work, then move to my subscriptions and stopped working. Same when moving to settings to review, and going back to front page, etc… It seems to be working now though… Hopefully I just keep reloading when losing the theme again, and that’ll be it, :) Thanks !

      • Echedenyan@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        3 years ago

        Yes, I logged in on mobile using Fennec F-Droid.

        My session was logged off in the beginnig as you explained there.

        Edited:

        Just to test I relogged in again and the issue is maintained.

        • Dessalines@lemmy.mlOPM
          link
          fedilink
          arrow-up
          1
          ·
          3 years ago

          I’d need to see console logs, there’s no other way I could figure out the error. In your screenshot you have no post title, and that’s required (and it should tell you that).

          • Echedenyan@lemmy.ml
            link
            fedilink
            arrow-up
            1
            ·
            3 years ago

            It is suggested from the link I put in the URL. The version before didn’t require me to do that if was suggested if I remember correctly, but anyways it is right that even these things are not told.

            I will try double-window to check log with other app.