Announcements

22775 readers
1 users here now

Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.

You can also find major news on join-lemmy.org

founded 5 years ago
MODERATORS
26
 
 

Its been a long time coming 🥳 .

Excerpt from the link:

Major Changes

Language Tags

Content can now be tagged to indicate the language it is written in. These tags can be used to filter content, so that you only see posts in languages which you actually understand. Instances and communities can also specify which languages are allowed, and prevent posting in other languages.

In the future this will also allow for integrated translation tools.

Comment trees

Lemmy has changed the way it stores comments, in order to be able to properly limit the comments shown to a maximum depth.

Included are proper comment links (/comment/id), where you can see its children, a count of its hidden children, and a context button to view its parents, or the post.

Featured posts

Admins and mods can now "feature" (this used to be called "sticky" ala reddit) posts to the top of either a community, or the top of the front page. This makes possible announcement and bulletin-type posts.

Special thanks to @makotech for adding this feature.

Federation

Lemmy users can now be followed. Just visit a user profile from another platform like Mastodon, and click the follow button, then you will receive new posts and comments in the timeline.

Votes are now federated as private. This prevents other platforms from showing who voted on a given post, and it also means that Lemmy now counts votes from Mastodon.

This release also improves compatibility with Pleroma. If you previously had trouble interacting between Pleroma and Lemmy, give it another try.

We've extracted the main federation logic into its own library, activitypub-federation-rust. It is open source and can be used by other projects to implement Activitypub federation, without having to reinvent the wheel. The library helps with handling HTTP signatures, sending and receiving activities, fetching remote objects and more.

Other changes

  • Admins can now purge content and pictures from the database.
  • Mods can distinguish a comment, "stickying" it to the top of a post. Useful for mod messages and announcements.
  • Number of new / unread comments are now shown for each post.
  • Lemmy now automatically embeds videos from Peertube, Youtube and other sites which provide an embed link via Opengraph attribute.
  • You can give your site "taglines", short markdown messages, which are shown at the top of your front page. Thanks to @makotech for adding this.
  • You can now report private messages.
  • Most settings have been moved from the config file into the database. This means they can be updated much easier, and apply immediately without a restart.
  • When setting up a new Lemmy instance, it doesn't create a default community anymore. Instead this needs to be done manually.
  • Admins can choose to receive emails for new registration applications.
  • An upgrade of diesel to v2.0, our rust -> postgres layer.
27
 
 

We're getting ready to release a new version of Lemmy, which will require a database upgrade, so we'll have a few hours of downtime.

28
 
 

All the old pictures are restored from a backup, and should be working now. We've bought more hard drive space too, so we should be okay for a while.

29
 
 

A few bug fixes:

  • Fix missing auth on new post refresh. (#764)
  • Change CSP rule for connect-src (websocket) to wildcard (fixes #730) (#737)
  • Increase default search rate limit. (#2424)
  • Rejected federated pm from blocked users (fixes #2398) (#2408)
  • Handle Like, Undo/Like activities from Mastodon, add tests (fixes #2378) (#2380)
  • Revert "Handle Like, Undo/Like activities from Mastodon, add tests (fixes #2378) (#2380)"
  • Handle Like, Undo/Like activities from Mastodon, add tests (fixes #2378) (#2380)
  • Dont allow login if account is banned or deleted (fixes #2372) (#2374)
  • Fix panics in search_by_apub_id() (fixes #2371) (#2373)
30
-1
submitted 4 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]
 
 

Recently there have been some discussions about the political stances of the Lemmy developers and site admins. To clear up some misconceptions: Lemmy is run by a team of people with different ideologies, including anti-capitalist, communist, anarchist, and others. While @dessalines and I are communists, we take decisions collectively, and don't demand that anyone adopt our views or convert to our ideologies. We wouldn't devote so much time to building a federated site otherwise.

What's important to us is that you follow the site rules and Code of Conduct. Meaning primarily, no-bigotry, and being respectful towards others. As long as that is the case, we can get along perfectly fine.

In general we are open for constructive feedback, so please contact any member of the admin team if you have an idea how to improve Lemmy.

Slur Filter

We also noticed a consistent criticism of the built-in slur filter in Lemmy. Not so much on lemmy.ml itself, but whenever Lemmy is recommended elsewhere, a few usual suspects keep bringing it up. To these people we say the following: we are using the slur filter as a tool to keep a friendly atmosphere, and prevent racists, sexists and other bigots from using Lemmy. Its existence alone has lead many of them to not make an account, or run an instance: a clear net positive.

You can see for yourself the words which are blocked (content warning, link here). Note that it doesn't include any simple swear words, but only slurs which are used to insult and attack other people. If you want to use any of these words, then please stay on one of the many platforms that permit them. Lemmy is not for you, and we don't want you here.

We are fully aware that the slur filter is not perfect. It is made for American English, and can give false positives in other languages or dialects. We are totally willing to fix such problems on a case by case basis, simply open an issue in our repo with a description of the problem.