What is Lemmy?

Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top.

Major Changes

Theming

Customizing Lemmy is now much easier than before. Instance admins can select a default instance theme under /admin which applies to all users who are not logged in, and those who haven’t explicitly picked a theme.

It is also possible now to add custom themes to an instance, without having to recompile lemmy-ui. When running with Docker, make sure that these lines are present in docker-compose.yml (Ansible will add them automatically if you updated the repo). Then put your .css file into ./volumes/lemmy-ui/extra_themes. The new theme can then be selected by users, or set as instance default.

For native installation (without Docker), themes are loaded by lemmy-ui from ./extra_themes folder. A different path can be specified with LEMMY_UI_EXTRA_THEMES_FOLDER environment variable.

For instructions how to create a new theme, have a look at the documentation.

Federation

@nutomic made many changes to federation to increase compatibility with other software. Lemmy can now receive deletions from [Pleroma], comments from [Friendica] and communities from lotide. Other actions were already compatible before. Mastodon can now display communities even when a user with identical name exists (but the user can’t be viewed in that case). There were no breaking changes necessary, so federation is fully compatible with 0.15. If you notice something in another project that doesn’t federate but should, please open an issue.

Multiple users have pointed out that posts, comments and votes don’t federate reliably. We first attempted to fix this in Lemmy 0.15.4 a few days ago, but that didn’t help much. Later @nutomic noticed that Lemmy was only sending out activities with 4 worker threads, which is not enough for a big instance like lemmy.ml. At the same time, many of those workers were taken up by sending to broken instances, trying to connect for a minute or more. This version adds a timeout and increases the number of workers.

Federated bans

Until now, only community bans were federated, and the “Remove content” option didn’t work over federation. The new version fixes this behaviour, so that both site bans and community bans federate, including “Remove content” option and expiry. Note that this change only affects new bans, those which were issued before upgrading to 0.16 will not be federated.

Hide communities

@dayinjing implemented a funcionality for instance admins to hide controversial communities. A hidden community is only visible to those users who subscribe to it. This represents a milder alternative to removing a community. This functionality is not implemented in lemmy-ui yet, but admins can hide a community like this via command line:

curl -X PUT https://example.com/api/v3/community/hide \   
    -H "Content-Type: application/json" \
    -d \
    '{"community_id":3,"hidden":true,"reason":"*reason for mod log*","auth":"*admin jwt token*"}'

Jerboa: a new android app

To help adoption, and since most people use social media through their smartphones nowadays, @dessalines has been working on a native android app for Lemmy called Jerboa, which is now on F-Droid and Google Play.

It is still at an alpha level, but is very usable. We’d love to have experienced android developers contribute to it.

This now makes three smartphone apps for Lemmy: Lemmur and Jerboa for Android, and Remmel for iOS.

Upgrade notes

Follow the Docker or Ansible upgrade instructions here.

There are three lemmy.hjson config changes. See defaults.hjson for comments and default values.

• changed boolean email.use_tls to email.tls_type
• added setup.default_theme
• added federation.worker_count

Support development

We (@dessalines and @nutomic) have been working full-time on Lemmy for almost two years. This is largely thanks to support from NLnet foundation. If you would like to support our efforts, please consider donating.

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

• A full list of the API changes can be seen on this diff of lemmy-js-client: 0.15.0 -> 0.16.0 .

Config

• The config changes are here.