Lemmy v0.19.9 Release
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.
Changes
This version fixes a potential security problem, by preventing Lemmy from accessing localhost URLs. There is also a fix for a crash during markdown parsing. Lemmy now uses mimalloc instead of the system allocator (usually glibc), which should improve performance and prevent unlimited memory growth over time.
Lemmy
- Error handling for thumbnail generation
- Use mimalloc as memory allocator
- Additional security checks for URLs (details) . Security Advisory
- Fix crash while rewriting markdown
- Fix peertube federation
- Append attachments to comments (@flamingo-cant-draw)
- Enable site languages for new user
Lemmy-UI
- Enforce required validation on signup answers (@anhcuky)
- copy thumbnail URL during crossposting (@anhcuky)
- Adding a bottom-margin to spoiler details tag.
- Fixing login password limits.
- Adding zh-CN as default for zh lang.
- Updated translations
Upgrade instructions
There are no breaking changes with this release.
Follow the upgrade instructions for ansible or docker.
If you need help with the upgrade, you can ask in our support forum or on the Matrix Chat.
Thanks to everyone
We’d like to thank our many contributors and users of Lemmy for coding, translating, testing, and helping find and fix bugs. We’re glad many people find it useful and enjoyable enough to contribute.
Support development
We (@dessalines and @nutomic) have been working full-time on Lemmy for over five years. This is largely thanks to support from NLnet foundation, as well as donations from individual users.
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. A recurring donation is the best way to ensure that open-source software like Lemmy can stay independent and alive, and helps us grow our little developer co-op to support more full-time developers.
- Liberapay (preferred option)
- Open Collective
- Patreon
- Cryptocurrency
Amazing that we are already up to 0.19.9 and on the verge of version 1.0.
The project has come a long way since 0.17.4, when I first joined. Sometimes it felt like it was taking a long time but looking back it seems like it went so fast. Thank you so much to all contributors, especially Dessalines and Nutomic.
There is still much more to be done, but I also think it’s good to reflect on how far we have come.
Very nice to see the fix for the spoiler bottom margin, I have been inserting line breaks after spoilers to alleviate that issue for quite some time.
Very nice to see the fix for the spoiler bottom margin, I have been inserting line breaks after spoilers to alleviate that issue for quite some time.
I’ve used
(it’s just a bunch of hyphens) and that works well
Yes that’s what I meant by inserting a line break. Btw you only need three hyphens.
I’ve become pretty adept with lemmy markdown, it’s extremely useful for formatting
Lol nice, thanks for the link.
I’ve started dreaming in markdown 😅
Enable site languages for new user
Good news!
Also, funny to see Lemmy and Mbin having releases on the same day
Very nice. Thank you for the continued work.
Is this update going to fix the report federation issues many mods have been having?
I implemented reports federation recently, in current versions it is not available at all. So you may have to wait until version 1.0, though @MrKaplan mentioned that he plans to backport it to 0.19.xEdit: Nevermind I was talking nonsense. Reports do federate, but only in a limited way. Particularly if you moderate a remote community you wont see the reports. Also the action of resolving a report is currently not federated at all. Both of these are fixed with the PR above.
Thanks for confirming
not available at all
I may be confused lol. For as long as I’ve been modding for !196@lemmy.blahaj.zone, I’ve been able to see reports from all instances, but it’s an incomplete list. My lemm.ee account and .world account both have reports that the other can’t see, but the lists are mostly the same.
I assumed that meant we did have reports federating, just not reliably.
Sorry I said it wrong, reports do federate but only in a limited way. Particularly if you moderate a remote community you wont see the reports. Also the action of resolving a report is currently not federated at all. Both of these are fixed with the PR above.
I thought so too. But I think moderation actionsaren’t federating. So if I understand correctly a removed post for example will only be removed from view form users of your instance?
AFAIK:
- Dismissing reports never federates
- Post removals almost always federate
- Bans almost always federate
- Reports usually federate
A post on 196@bhz removed from .world will be federated properly in my experience, but post removals from something like Kbin seem to be less likely to federate.
Dismissing reports never federates
Thanks!
Oh, nice to see you here ha ha
Good job, though for me on a raspbian Debian bookworm with
%raver@viruspi ~ uname -a Linux viruspi 6.6.74+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.74-1+rpt1 (2025-01-27) aarch64 GNU/LinuxRunning on raspberry pi 5 the lemmy 0.19.9 container fails with exit code 139 and won’t start
root@viruspi /etc/lemmy docker compose up [+] Running 6/6 ✔ Container lemmy-postfix-1 Running 0.0s ✔ Container lemmy-pictrs-1 Running 0.0s ✔ Container lemmy-postgres-1 Running 0.0s ✔ Container lemmy-lemmy-1 Created 0.0s ✔ Container lemmy-lemmy-ui-1 Running 0.0s ✔ Container lemmy-proxy-1 Running 0.0s Attaching to lemmy-1, lemmy-ui-1, pictrs-1, postfix-1, postgres-1, proxy-1 lemmy-1 exited with code 0 lemmy-1 exited with code 139 lemmy-1 exited with code 139 lemmy-1 exited with code 139 lemmy-1 exited with code 139 lemmy-1 exited with code 139 lemmy-1 exited with code 139 Gracefully stopping... (press Ctrl+C again to force) [+] Stopping 6/6 ✔ Container lemmy-postfix-1 Stopped 0.4s ✔ Container lemmy-proxy-1 Stopped 0.4s ✔ Container lemmy-lemmy-ui-1 Stopped 0.2s ✔ Container lemmy-lemmy-1 Stopped 0.0s ✔ Container lemmy-postgres-1 Stopped 0.3s ✔ Container lemmy-pictrs-1 Stopped 0.5s ⚡ root@viruspi /etc/lemmy This sounds like the same problem you reported before. Only thing I can think of is to get in contact with the maintainer of lemmy-cross-toolchains
Has there been any benchmarking of Lemmy using mimalloc vs default (or jemalloc)?
No we dont have any benchmarking infrastructure. Maybe one of the instance admins will report some results later.
