Release v0.15.1 Release · LemmyNet/lemmy
github.com
Releases.md

Lemmy now has private instances, optional registration applications, optional email verification, and temporary bans! These are described in detail below.

Special thanks to @asonix for adding tokio-console and Jaeger + opentelemetry to our dev setups, so we can better identify performance bottlenecks.

What is Lemmy?

Lemmy is similar to sites like Reddit, Lobste.rs, or Hacker News: you subscribe to communities you’re interested in, post links and discussions, then vote and comment on them. Lemmy isn’t just a reddit alternative; its a network of interconnected communities ran by different people and organizations, all combining to create a single, personalized front page of your favorite news, articles, and memes.

Major Changes

Required email verification

Admins can turn this on, and new users will need to verify their emails. Current users will not have to do this.

Registration applications

Admins can now optionally make new users fill out an application to join your server. There is a new panel in their top bar where they can approve or deny pending applications.

This works in conjunction with the require_email field. If that is also turned on, the application will only be shown after their email has been verified. The user will receive an email when they have been accepted.

Closed / Private instances

The instance settings now includes a private instance option, which if turned on, will only let logged in users view your site. Private instances was one of our first issues, and it was a large effort, so its great to finally have this completed.

Temporary Bans

When banning users from your site or community, moderators can now optionally give a number of days for the ban to last.

Allow comment replies from blocked users

It used to be that if a user blocked you, you couldn’t respond to their public posts and comments. This is now fixed. They won’t see your content, but others can.

Upgrade notes

Follow the Docker or Ansible upgrade instructions here.

Support development

If you’d like to support development, and make sure that we will always be available to work full time on Lemmy, consider donating to support its development. We’ve spent hundreds of hours on Lemmy, and would like to be able to add more developers to our little open-source co-op as time goes on.

Changes

API

We’ve removed a list of banned users from GetSite, added a few endpoints related to registration applications, made a few changes allowing temporary bans, site settings, made a few changes to the login response. These are non-destructive and current clients should work with this release.

Config

There is a new rate limit for creating new comments in the config.hjson.

Lemmy Server

  • Adding temporary bans. Fixes #1423 (#1999)
  • Add console-subscriber (#2003)
  • Opentelemetry (#1992)
  • Use correct encoding when fetching non-UTF-8 site metadata (#2015)
  • Adding a banned endpoint for admins. Removing it from GetSite. Fixes #1806
  • Prevent panic on InboxRequestGuard
  • Case-insensitive webfinger response. Fixes #1955 & #1986 (#2005)
  • First pass at invite-only migration. (#1949)
  • Upgrading pictrs. (#1996)
  • Trying out an upgraded version of html5ever. #1964 (#1991)
  • Adding min setup password length to the docs. Fixes #1989 (#1990)
  • Test pleroma follow (#1988)
  • Remove awc (#1979)
  • Consolidate reqwest clients, use reqwest-middleware for tracing
  • Don’t drop error context when adding a message to errors (#1958)
  • Change lemmur repo links (#1977)
  • added deps - git and ca-certificates (for federation to work) and changed adduser to useradd so that user can be added non-interactively (#1976)
  • Allow comment replies from blocked users. Fixes #1793 (#1969)
  • Fix retry infinite loops. Fixes #1964 (#1967)
  • Add lotide activities to tests
  • Allow single item for to, cc, and @context
  • Adding a captcha rate limit. Fixes #1755 (#1941)
  • Dont send email notifications for edited comments (fixes #1925)
  • Fix API dupes query. #1878
  • Fixing duped report view for admins. Fixes #1933 (#1945)
  • Adding a GetComment endpoint. Fixes #1919 (#1944)
  • Fix min title char count for post titles. Fixes #1854 (#1940)
  • Adding MarkPostAsRead to API. Fixes #1784 (#1946)
  • background-jobs 0.11 (#1943)
  • Add tracing (#1942)
  • Remove pointless community follower sort. (#1939)
  • Use once_cell instead of lazy_static
  • Adding unique constraint for activity ap_id. Fixes #1878 (#1935)
  • Making public key required. Fixes #1934
  • Change NodeInfo links to an array
  • Fixing fuzzy_search to escape like chars.
  • Fix build error in #1914
  • Fix login ilike bug. Fixes #1920
  • Fix Smithereen webfinger, remove duplicate webfinger impl (fixes #1916)
  • Dont announce comments, edited posts to Pleroma/Mastodon followers
  • Community outbox should only contain activities sent by community (fixes #1916)
  • Remove HTTP signature compatibility mode (its not necessary)
  • Implement rate limits on comments

Lemmy UI

  • Fixed an issue with post embeds not being pushed to a new line #544
  • Adding as and lt languages, Updating translations.
  • Temp bans (#524)
  • Fix banner. Fixes #466 (#534)
  • Making the modlog badge stand out more. Fixes #531 (#539)
  • Add some fallback properties for display in older browsers (#535)
  • Private instances (#523)
  • Add nord theme. Fixes #520 (#527)
  • Dont receive post room comments from blocked users. (#516)
  • Using console.error for error logs. (#517)
  • Fix issue with websocket buffer.
  • Switching to websocket-ts. #247 (#515)
  • Fix native language issue. (zh_Hant) (#513)
  • Fix tippy on component mount. Fixes #509 (#511)
  • Fix docker latest (#510)
  • Enabling html tags in markdown. Fixes #498
  • Fix comment scroll bug. Fixes #492
  • Fixing error for null person_block. Fixes #491
  • Trying to catch promise and json parse errors. #489 (#490)
  • edward@lemmy.ml
    1·
    3 years ago

    Hi, I’m a dev from hexbear and it looks like my first UI changes (relating to post listings) were included in this release.

    Here are the changes I made:

    • Expanded image and body now show below the rest of the listing.
      • And also offset to not be under the votes and thumbnail.
    • Post title doesn’t jump to a new line when you expand the image.
    • Thumbnail doesn’t disappear when you expand the image.
      • Does not apply on mobile since things don’t jump around as much.
    • Clicking expanded image opens the original in a new tab.
      • Does not apply on mobile since you can just long press.
      • Instead tapping the image closes it.
    • pictrs images now prefer the original format over jpg.
    • Rendering split into many functions to improve readability.
    • Post actions are now on the same line as the comments button.
    • Post actions now show on mobile.
    • Comments button made larger.
    • Expanding or contracting an image now expands or contracts the body.

    I’d love to hear any feedback or ideas anyone here may have.

  • Thann@lemmy.ml
    0·
    3 years ago

    It used to be that if a user blocked you, you couldn’t respond to their public posts and comments. This is now fixed. They won’t see your content, but others can.

    If a user personally-blocks you, but they moderate a subreddit, and you make a comment on their post in their sub, will they be able to moderate it?

      • Arthur Besse@lemmy.ml
        0·
        3 years ago

        I noticed an unexpected side effect of blocking: I am apparently blocked by a user I’ve never interacted with, which I discovered because I cannot upvote their posts or comments. Is this intentional? I wish I could ask them why they blocked me, but I of course cannot message them to ask. It makes sense that blocking prevents messaging, but, why can’t I upvote their posts?!