Here is an update that explains what we have been working on recently (apologies for not having these for a few months, summer vacations and all that). This should allow average users to keep up with development, without reading Github comments or knowing how to program.

@privacyguard added Single-Sign-On (SSO) support to lemmy (this still needs some UI work and testing, but the bulk of the work is done). Special thanks to Privacy Portal for working on this!

@carlos-cabello added a way to filter posts by title only (and not body) when searching.

@Freakazoid182 added custom emoji and tagline views.

@nothing4u made our scheduled cleanup job delete denied users.

@sunaurus made a few image proxy fixes.

@sleepless has been working hard on lemmy-ui-leptos, which may eventually replace lemmy-ui. He made improvements to how posts are displayed; made SI formatting consistent with how the current UI handles it; added translations; added post content actions, creator, and community listings; and made some plugins for markdown-it.

@nutomic cleaned up the issue tracker by closing invalid issues and adding tags like good first issue. He also made some simple improvements, like adding a category to RSS feeds, fixing an issue with activitypub ids, and removing the enable_nsfw setting in favor of content_warning.

@dessalines integrated a new rust clearurls library into lemmy that will remove tracking params for any post or comment text (Much thanks to @jendrikw for creating this library), increased the bio max length from 300 to 1000, removes lemmy’s reliance on openssl, made the list logins response more uniform, added the ability to restore content on an unban, added a default comment sort type for both the local site, and your user.

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.

  • 1984English
    55·
    3 months ago

    I’m sorry but how is single sign on with some big tech player account like github or Microsoft considered a privacy feature? It sounds like anti privacy?

    • seang96@spgrn.comEnglish
      24·
      3 months ago

      Its using OpenID so yes it would support those. But it would support a lot of others as well. Authelia, keycloak, and authentik are a few examples that are open source and self hostable. Its nice to have SSO for all your services even in a homelab.

    • Tiff@reddthat.comEnglish
      16·
      3 months ago

      This is sso support as the client. So you could use any backend that supports the oauth backend (I assume, didn’t look at it yet).

      So you could use a forgejo instance, immediately making your git hosting instance a social platform, if you wanted.
      Or use something as self hostable like hydra.

      Or you can use the social platforms that already exist such as Google or Microsoft. Allowing faster onboarding to joining the fediverse. While allowing the issues that come with user creation to be passed onto a bigger player who already does verification. All of these features are up for your instance to decide on.
      The best part, if you don’t agree with what your instance decides on, you can migrate to one that has a policy that coincides with your values.

      Hope that gives you an idea behind why this feature is warranted.