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
Lemmy-UI
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.
I may be confused lol. For as long as I've been modding for [email protected], 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:
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.
Thanks!