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.

We failed to publish the update last Friday as scheduled, so this update contains more changes than usual. We also added @dullbananas as maintainer for the Lemmy backend repo.

@matc-pub reduced the amount of data that needs to be fetched by the browser for rendering lemmy-ui, by loading only translations which are actually used.

@flamingo-cant-draw added a URL Blocklist, to prevent link spamming.

@SleeplessOne exposed Lemmy errors in the Rust API. In lemmy-ui he added a badge for number of local subscribers to a community and added a UI to see and edit community visibility. In the leptos UI, he made the UI use the lemmy-client crate for API requests.

@Nutomic fixed synchronization of featured posts. He added a ‘delete content’ checkbox for account deletion which was missing from previous releases. He also fixed various bugs related to password reset, signed fetch from Mastodon, search listing type, password reset and 2FA. He updated the federation library with security improvements. Added dont require leading ! or @ for webfinger resolve. Fixed video thumbnail generation.. Added including an apub hashtag with a post.

@Dessalines added a new API endpoint for users to hide posts. He made various moderation improvements, such as removing content from local communities when a remote user is banned or purged, viewing mod action history and report history for specific posts and comments. Additionally he added an alt_text field for posts, and a new user setting for vote display mode. Also added extra fields to PostReport and CommentReport views. Has also, along with @MV-GH, been making many improvements to Jerboa.

In personal news, @nutomic’s daugher will be born next month. Afterwards he will take a break from Lemmy to take care of her for some months.

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.

  • ludrol@bookwormstory.social
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    2
    ·
    8 months ago

    Thanks for a lot for the update. I wouldn’t say that auto apub hashtags is a good change. IMO they will spam the mastodon hashtags and should be implemented properly and extensively with customization and optionality.

    I would say that this should be made into an RFC and current implementation removed before next realase.

    I see a lot of mod tools improvements. That’s great to hear.

    • Die4Ever
      link
      fedilink
      English
      arrow-up
      7
      ·
      edit-2
      8 months ago

      I think this might convince the Mastodon devs to fix their rendering of Lemmy posts, and then this will be a good thing

      also Lemmy itself might find a way to make use of hashtags

    • Omega_Haxors@lemmy.ml
      link
      fedilink
      English
      arrow-up
      7
      ·
      edit-2
      8 months ago

      I personally think it’s a good idea overall and would take it a step further. It should hashtag “lemmy”, the instance it was posted on and the comm it was posted to. That way when you’re on mastodon you can subscribe to a lemmy comm by subscribing to its hashtag.

      Being able to have the (almost)[Mastodon lacks downvoting] full Lemmy experience from a completely different website is what makes the federation so great.

      • ludrol@bookwormstory.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        8 months ago

        Yes, I don’t oppose the hashtags as a concept. I am just saying that they should be fleshed out in a RFC before they would be implemented half way into production.

        As is stands current implementation is sub optimal.