Calling for donations! We're running Lemmy.World for you to use for free, however the running costs aren't for free… If you appreciate our services and are willing and able to help out paying the bills, please consider a donation on one of these platforms:

• https://ko-fi.com/fhfworld - Preferred
• https://liberapay.com/fhf
• https://opencollective.com/mastodonworld - (Either recurring or one-time donations)
• https://patreon.com/mastodonworld - (Recurring donations only)
• https://bunq.me/fhf - This is a Dutch bank account for those looking for SEPA / IBAN bank transfers

The most recent blog post with financial information is from September as follows:

https://blog.mastodon.world/september-2025-updates-for-the-worlds-and-call-for-donations

Hello World,

we have just defederated from lemmy.org due to lack of moderation on their side.

This instance has open registrations, seemingly zero abuse prevention on signup, including not requiring emails. This leads to a small number of people constantly creating new disposable accounts for various types of abuse with zero consequences.

Their admin is the CEO of an ad company, which surely doesn't affect incentives. They do virtually zero moderation, allowing all these abusive accounts to rampantly harass other instances. The very rare cases when moderation actually happens is when it affects local communities on that instance, anything else seems to be getting ignored. The admin is also frequently posting to their local communities, but doesn't at all comment or interact with remote communities in any way.

We, as well as other people, including at least one admin of another instance, have attempted to reach out to them about their lack of moderation, but we haven't received any response at all.

At this point there isn't really anything left besides defederating them, which several other instances have already done as well.

Due to a (now former) admin of the instance anarchist.nexus calling for a member of our team, as well as anyone else they call a zionist, to be murdered, the instance has been defederated.

We're currently discussing how we will proceed with this situation and whether it will affect lemmy.dbzer0.com, which is mostly run by the same admin team, notably excluding the person who used to be on the anarchist.nexus admin team.

We will share further updates once we have them.

---

Update 2026-04-22 23:25 UTC: anarchist.nexus federation has been reactivated.

We are still discussing this matter, but there is currently no point in keeping anarchist.nexus defederated while lemmy.dbzer0.com is federated.

Hello World,

we will be performing an update to Lemmy in about 35 minutes.

We expect up to about 15 minutes of downtime for a DB migration to add a new DB index to optimize a query.

You can convert this to your local time here: https://inmytime.zone/?iso=2026-04-13T22%3A30%3A00.000Z

Along with this, we will also be deploying a change to test new DB timeouts proposed by Lemmy devs in #6441, which adjust functionality we've previously reverted from the most recent Lemmy version.

No user-facing changes are expected.

Calling for donations! We're running Lemmy.World for you to use for free, however the running costs aren't for free... If you appreciate our services and are willing and able to help out paying the bills, please consider a donation on one of these platforms:

• https://ko-fi.com/fhfworld - Preferred.
• https://liberapay.com/fhf
• https://opencollective.com/mastodonworld - (Either recurring or one-time donations).
• https://patreon.com/mastodonworld - (Recurring donations only)
• https://bunq.me/fhf - This is a Dutch bank account for those looking for SEPA / IBAN bank transfers

We have a blog with overview of the running costs, which is severely outdated... I will update this before the next call for donations: https://blog.mastodon.world/

Hello World,

after updating to 0.19.17 last night we've experienced federation issues over the last 24h, where in some cases federation to some other instances was stuck for up to a few hours at a time.

We believe to have identified the root cause for this issue and are currently rolling out a patch to revert the likely cause.

This issue has been reported on the Lemmy issue tracker here.

Due to the overall volume of federation data it'll take some time until other instances will be fully caught up again. We'll keep monitoring the situation.

---

edit: forgot to refresh the dashboard, should be caught up on most instances already

---

update 2026-03-31 8:27 UTC: we're not seeing the previously logged errors anymore since reverting the suspected patch.

Hello World,

we may be performing an update to Lemmy 0.19.15 on Friday.

We don't know for sure yet if we will have time to prepare and then do the update, but we'll try to squeeze it in to have it deployed this year still, as we would otherwise have to postpone it to next year.

We are planning maintenance within the time frame from 09:00-13:30 UTC on 26th of December. Actual downtime within this window is expected to be significantly shorter, maybe 15-30 minutes due to a DB migration, but we don't know yet when it will be, or if we'll be able to fit it in here at all.

You can convert this to your local time here: https://inmytime.zone/?iso=2025-12-26T09%3A00%3A00.000Z

You can find an overview of the changes here:

• 0.19.13 release announcement
• 0.19.14 release announcement
• 0.19.15 release announcement

The most notable user-facing changes are the following:

• Comments are no longer shown as edited in the default web interface, provided the edit was within 5 minutes of the comment being posted
• Length of user profile bio has been increased to 10,000 characters
• Community sidebars now have a search field in the default web interface
• Search can be limited to post title only
• Moderation actions on deleted users federate properly
• Pagination limit using non-cursor pagination has been limited to 100 pages max.
  This should only be relevant for developers and users of clients using the legacy method for pagination, although it isn't common to scroll through 100 pages either way. Using cursor navigation is recommended and does not impose this limit.

---

Update 10:55 UTC: the update has been completed successfully

Hello World,

we will be replacing a faulty memory module on our server today. As this will require powering down the server, we will also combine this with a few other system maintenance tasks.

Our hosting provider has confirmed their work between 14:00-14:30 UTC, our full maintenance window is 13:45-14:45 UTC to have a little extra buffer and be able to deal with our additional maintenance work.

You can convert this to your local time here: https://inmytime.zone/?iso=2025-12-05T13%3A45%3A00.000Z

---

Update 12:25 UTC: Hosting provider confirmed the maintenance window

---

Update 14:20 UTC: Memory module has been replaced and all maintenance work has been completed

Hello World,

as some of you might be aware, there have been various accusations against one of our former community team members, Jordan Lund.

We have removed Jordan as a member of our community team a week ago, on 23rd of September, due to various behavior that we do not consider acceptable for a member of our team. We haven't posted about this earlier, as we're still in the progress of reviewing and making decisions, and we originally expected to be able to conclude this earlier, within a time frame where we could have presented the final outcome in the first post.

During his time with Lemmy.World, Jordan has been helping out our team with various admin-level tasks, as well as moderating a few large communities, including [email protected], [email protected] and [email protected]. As far as we can tell, most of his actions, including moderation actions, were in alignment with both our instance rules and also rules and spirit of the affected communities.

Unfortunately, this does not apply to all his actions. We have identified multiple cases of conduct that do not align with what we expect from members of our team. We currently do not have any explicit rules or code of conduct for our community team or other team members like instance admins on top of our ToS/bylaws, as we expected to have a common understanding of acceptable behavior. In the past we already had discussions with Jordan about some of this behavior and we believed that to be enough at that time. Going forward, we will be working on a code of conduct applicable to all members of our team, including community team and anyone above.

Being a member of our community team provides additional privileges for selected members, such as the ability to appoint community moderators, update our community spotlight or even banning users. In Jordan's case this included permissions to appoint community moderators and ban users from the instance.

As of today, we are not aware of misuse of these additional privileges. Once we have reviewed other actions taken by Jordan we will also review these types of actions taken by Jordan in the recent past. If you believe that you or someone else was incorrectly banned from Lemmy.World, you're welcome to appeal your ban by reaching out to our team. As we currently have some technical issues with our ticket system, I recommend sending an email to report at lemmy dot world for the time being, visting our Matrix room #general:lemmy.world or reaching out to @[email protected] directly, also possible via Matrix at @mrkaplan:lemmy.world.

Following our instance rules, we have a few cases in which we may remove community moderators from their communities:

1. Grossly committing a violation of the Terms of Service
2. Acting repeatedly against the local community rules
3. Extended periods of inactivity, as evident by lack of public interaction and/or failure to respond to reports

We are still discussing whether we consider his behavior a "gross violation of our ToS", as there are definitely some arguments to be made in favor of that. This includes for example using incorrect gendered pronouns, which we will update in our ToS in the coming days to make it more clear to everyone that this will not be tolerated. Due to his previous and current position we are still discussing what our final resolution to this issue will be as far as instance rules are concerned. Whether or not a person is trolling does not justify using incorrect pronouns for them. We have also informed Jordan that we expect his behavior in this regard to change immediately.

We're currently also in conversations with other moderators of communities moderated by Jordan to review their position on his behavior within their communities and whether they believe that his actions in those communities were appropriate and in line with the community rules. As a reminder, the order of community moderators in the sidebar has direct impact on the moderator hierarchy, where a moderator listed earlier is able to remove any moderators later in the list. This means even if an action might not (yet) be taken by instance admins, other community moderators may be able to remove moderators if they're no longer desired to be part of the team. Especially community rules about civility and respectful conduct do not appear to have been followed in a number of cases, and we are reviewing with the community moderators whether this is in line with other content they would usually moderate/not moderate.

It should also be noted that not all things reported to us are actually or clearly violating our rules, even if we may not agree with them. For example, we currently do not have rules about moderators removing other people's arguments, especially as "misinformation", to strengthen their own misguided arguments, and then continue to accuse the other side of misinformation later on. We do expect our team members to not use positions of power to "win arguments" or falsely accuse others of misinformation, when this isn't actually the case. Therefore, while this example is not something we tolerate for members of our team, having this happen on community level (by a person who isn't also holding a role above community mod at that time) is currently not something we are enforcing.

Once we have worked out a CoC for members of our team, we will post about this separately and also gather community feedback on whether you believe that enforcement of that (or parts of it, or more things) should also include moderators of Lemmy.World communities.

Additionally, we will also be looking at expanding our community team a bit in the near future, as we have both lost some people over time and recently also Jordan. We will also be posting about this separately, currently expected to be in a few weeks, with a description of expectations and responsibilities.

We will also be updating this post over the coming days until we have finished our review and actions.

---

Update 2025-10-06 01:27 UTC:

After reviewing various comments and actions by Jordan, he has received a warning, especially relating to following our rules at https://legal.lemmy.world/tos/#1-attacks-on-people-or-groups. Going forward, if we see additional violations of our rules, especially when it comes to attacking others, we will consider additional consequences in the form of a temporary or permanent ban. If you still see Jordan's behaving in ways violating our ToS, please report this directly to us, e.g. through a pm to @[email protected]. We always review messages received by this account in our team.

In line with our current rules about potentially removing community moderators, we have reviewed the communities Jordan is currently a moderator in:

1. [email protected]: This community has active moderators above Jordan Lund, such as @[email protected].
2. [email protected] This community has active moderators above Jordan Lund, such as @[email protected].
3. [email protected]: We have moved Jordan from being top moderator to being bottom moderator. New top moderator is @[email protected].
4. [email protected]: No other active mods
5. [email protected]: No other active mods
6. [email protected]: No other active mods
7. [email protected]: We have moved Jordan from being top moderator to being bottom moderator. New (active) top moderator is @[email protected].
8. [email protected]: No other active mods
9. [email protected]: No other active mods

Any community moderator above Jordan will be able to remove him from his moderator position, should they decide that he is not a good fit for the community. It is up to those community moderators whether they want to keep him on the team.

We generally intend to limit our involvement in community moderation to enforcement of instance rules. Without disallowing other community mods to add Jordan back as a moderator, there would also not be much impact of removing him entirely, as they could just add him back right away. If you do not agree with the rules in a community or the way it is moderated, it's always possible to look for alternative communities with different rules, different mods, or creating your own community.

Having said this, we're still working on our team CoC, and will be gathering community feedback in a standalone post to determine whether we should enforce additional standards for community moderators.

Our review of Jordan's delegated admin actions (instance bans) are still pending. Unless we find evidence of this having been abused, we we do not currently expect additional consequences to arise from this.

Hello world,

Due to an error in a spam filter, Automod accidentally deleted all comments for a period of about 15 minutes. We are working hard to restore them. You might get a notification that your post was removed with the reason: "automod: suspicious activity", please ignore that notification.

Sorry for the inconvenience, and thank you for being on the Fediverse.

With regards, The LW admin team

Hello World,

we will be performing an update to Lemmy 0.19.12 in just over an hour.

We are planning for around 15 minutes of downtime today at 20:00-20:15 UTC.

You can convert this to your local time here: https://inmytime.zone/?iso=2025-06-17T20%3A00%3A00.000Z

Most of the changes for 0.19.12 were already backported by us when we deployed 0.19.11.

This update will bring us the remaining changes listed in the release notes.

We were mostly just missing some technical changes:

• building with Rust 1.81 instead of 1.80
• updating various dependencies
• a small logic change to count local users more accurately for statistics
• database index additions, which should improve performance of some less frequently used queries

There is one more notable change: Lemmy now ships with the RBlind theme

---

Update 20:35 UTC: The update has been completed successfully and services were back up at 20:20 UTC, 5 minutes later than planned due to a stuck DB query blocking migrations.

Update: we've finally been in contact with Jonah and the material we originally flagged has been taken down. The link ban has been lifted.

We will be posting another announcement soon to provide more information and our future plans relating to federation.

---

Hello world,

following our previous decision to defederate lemmy.one due to their lack of responsiveness to abuse reports about CSAM hosted on their instance we have decided to also defederate from all other platforms operated by the same entity.

Lemmy.one is operated by Fediverse Communications LLC, which is ran by Jonah Aragon. Fediverse Communications LLC operates various Fediverse instances listed here:

• mstdn.party
• mstdn.plus
• lemmy.one
• mastodon.neat.computer
• pxlfd.plus

Jonah is also the project director of privacyguides.org and discuss.privacyguides.net is the community platform belonging to privacyguides.org.

Additionally, Jonah is also the director of Triplebit, the ISP used to host Fediverse Communications LLC infrastructure and also Privacy Guides infrastructure.

Our abuse reports to both Fediverse Communications LLC and Triplebit about CSAM hosted on lemmy.one have gone nowhere and this material is still up, almost 3 months since the original report. This has since also been reported to NCMEC (via Cloudflare) and other US law enforcement directly by us, but so far this hasn't resulted in anything being taken down.

Although we do not believe that it is likely to find CSAM on privacyguides.org or privacyguides.net, going forward we will remove all posts and comments referencing privacyguides.org, privacyguides.net, or any of the domains of services operated by Fediverse Communications LLC. We will not ban any user for mentioning or linking them, only remove these posts and comments.

Privacy Guides has come to our attention as they are just now testing federation of their discourse forum, which is also coincidentally posted by Jonah.

We will be lifting this link ban once the offending material has been taken down, but we will not consider refederation with any instance that is operated by Fediverse Communications LLC until they can somehow convince us that they'll be taking responsibility for their infrastructure in the future.

If the Privacy Guides team is willing and able to cut ties with Jonah we will also be more than happy to remove the ban of their domains and also refederate with their discourse forum even without the original issue with lemmy.one being addressed. Federation between discourse and Lemmy appears to currently still be quite limited or not be working at all, so for the time being the federation aspect may not have much relevance here.

It's unfortunate that things had to this far; we generally try addressing issues like this in a friendly manner and reporting it privately to affected instances, as most people are more than willing to take down CSAM hosted on their infrastructure. In this case however, Jonah appears to be operating way beyond what he is able to manage. Being not only an instance operator but also an ISP puts a lot of responsibility in your hands, and at the very least you should respond to abuse reports. We have exhausted non-law-enforcement escalation steps a while back already; we went to their ISP, which they are conveniently themselves. We don't know the actual server IP hosting this content, as it's behind Cloudflare, so only law enforcement would be able to obtain this information.

Hello world,

The Lemmy silver event is all wrapped up. In the image you can see the winners of the event. All donations have been send.

Thank you everyone for participating! We hope you all enjoyed the event. If you have any feedback, questions or anything else feel free to leave them here in the comments.

Here are the links for the various charities / fundraisers if you want to donate yourself:

• https://www.aark.org/supportus
• https://www.rainbowrailroad.org/
• https://ij.org/issues/private-property/civil-forfeiture/
• https://awionline.org/
• https://www.givesendgo.com/legalfund-ceo-shooting-suspect

(We are not affiliated with these charities)

Thank you to all admins and mods who pledged money!

I hope to get to create another event next year (:

Hello world,

as many of you probably already know, Lemmy is an open source project and its development is funded by donations.

Unfortunately, as is often the case, donations amounts are often going down over time if people are not aware of their necessity. When older users leave the platform they may stop donating, while new users joining will typically not be aware of this and won't start donating to even things out or even go towards an overall increase in donations.

All of the services provided by our non-profit Fedihosting Foundation are dependent on the development of FOSS platforms, which we can host without paying any licensing or other fees, instead only being required to pay for the infrastructure cost. We are currently investing a small part (€50 each) of the donations we receive in development of Lemmy and Mastodon, but the majority of the donations we receive are used for covering infrastructure costs. We're currently just about breaking even with the donations we receive, but it's certainly not enough to cover a large part of Lemmy or other software development costs.

We're looking to support sustainable software development for all the services we provide and will post similar announcements on our other platforms to promote donations towards the respective development teams in the coming days.

You can find the original announcement by @[email protected] below:

cross-posted from: https://lemmy.ml/post/29579005

An open source project the size of Lemmy needs constant work to manage the project, implement new features and fix bugs. Dessalines and I work full-time on these tasks and more. As there is no advertising or tracking, all of our work is funded through donations. Unfortunately the amount of donations has decreased to only 2000€ per month. This leaves only 1000€ per developer, which is not enough to pay my bills. With the current level of donations I will be forced to find another job, and drastically reduce my contributions to Lemmy. To avoid this outcome and keep Lemmy growing, I ask you to please make a recurring donation:

Liberapay | Ko-fi | Patreon | OpenCollective | Crypto

If you want more information before donating, consider the comparison with Reddit. It began as startup funded by rich investors. The site is managed by corporate executives who over time have become more and more disconnected from normal users. Their main goal is to make investors happy and to make a profit. This leads to user-hostile decisions like firing the employee responsible for AMAs, blocking third-party apps and more. As Reddit is a single website under a single authority, it means all users need to follow the same rules, including ridiculous ones like censoring the name "Luigi".

Lemmy represents a new type of social media which is the complete opposite of Reddit. It is split across many different websites, each with its own rules, and managed by normal people who actually care about the users. There is no company and no profit motive. Much of the work is carried out by volunteer admins, mods and posters, who contribute out of enthusiasm and not for money. For users this is great as there is no advertising nor tracking, and no chance of takeover by a billionaire. Additionally there are no builtin political or ideological restrictions. You can use the software for any purpose you like, add your own restrictions or scrutinize its inner workings. Lemmy truly belongs to everyone.

Dessalines and I work fulltime on Lemmy to keep up with all the feature requests, bug reports and development work. Even so there is barely enough time in the day, and no time for a second job. Previously I sometimes had to rely on my personal savings to keep developing Lemmy for you, but that can't go on forever. We partly rely on NLnet for funding, but they only pay for development of new features, and not for mandatory maintenance work. The only available option are user donations. To keep it viable donations need to reach a minimum of 5000€ per month, resulting in a modest salary of 2500€ per developer. If that goal is reached Dessalines and I can stop worrying about money, and fully focus on improving the software for the benefit of all users and instances. Please use the link below to see current donation stats and make your contribution! We especially rely on recurring donations to secure the long-term development and make Lemmy the best it can be.

Donate

---

edit, as this was frequently brought up:

Will donations to Lemmy development go towards the operation of lemmy.ml?

It depends on the donation method used and is limited to around 2% of the minimum overall donation goal. The vast majority of donations is exclusively used for developer salaries.

lemmy.ml hosting is only financed by donations via Opencollective. All other donations go exclusively to developer salaries.

[source]

For donations via Open Collective, yes, a tiny fraction of donations towards Lemmy development will go towards the operation of lemmy.ml. The reasons for this include that lemmy.ml is used for testing new releases and also that it's not worth maintaining a separate donation account for the instance. Additionally, it should be noted that the money going towards lemmy.ml hosting is just a tiny fraction of the funds that are being asked for. Hosting lemmy.ml costs around €100/month, which is only 2% of the stated minimum donation goal.

Hello world,

we will be performing an update to Lemmy 0.19.11 in an hour.

We are planning for around 15 minutes of downtime today at 21:30-21:45 UTC.

You can convert this to your local time here: https://inmytime.zone/?iso=2025-05-03T21%3A30%3A00.000Z

As mentioned in our April update, we had already backported most of the Lemmy-UI changes for 0.19.11, but we were still missing most of the backend changes.

This update will bring us the remaining changes listed in the release notes, as well as some additional changes not yet released:

• user registrations are now processed in a DB transaction, which prevents some errors we've occasionally seen in the past where registrations rarely resulted in an inconsistent user creation state (#5480)
• new posts in NSFW communities are now always marked NSFW (#5310)
• another round of peertube federation fixes (#5652)
• fixed email notifications for denied applications (#5641)
  this was already supposed to be part of 0.19.11 but it did not work there. we are migrating our previous external email notification implementation to let Lemmy handle sending emails now.
• various fixes for opentelemetry that are not present in upstream Lemmy
  As Lemmy opentelemetry has been removed from Lemmy 1.0 this is not code that we are currently planning to upstream to the 0.19 branch, but we intend to keep using this going forward.

If you are an instance admin considering enabling opentelemetry in Lemmy 0.19, don't do that unless you also apply a similar set of patches to bring the related libraries to newer versions, as your instance will otherwise lock up after some requests.

---

Update 21:50 UTC: The update has been completed successfully and within the planned amount of time.

Hello world,

we've had various smaller updates lately that didn't all warrant their own update posts and we don't want to post too many announcements around the same time, so we collected them for a single larger post.

New alternative Lemmy frontend: Tesseract

We have recently added a new alternative Lemmy frontend to our collection: Tesseract.

Tesseract was forked from Photon a while back and includes a variety of additional customization options and moderation utilities.

It is available at https://t.lemmy.world/.

Lemmy-UI update to 0.19.11-ish

We have deployed a custom build of Lemmy-UI, the default Lemmy web interface, which includes most of the features included in the official 0.19.11 release.

While we haven't updated our backend to a newer version yet, as we still have to find a solution for dealing with the newly integrated functionality to send emails on rejected registration applications, all the frontend features that don't require a backend update have been included. The only part that is currently missing is Lemmy's new donation dialog, as this requires a backend upgrade as well.

You can find the list of changes in the frontend section in the announcement for the 0.19.11 release.

Defederation from lemmy.one and r.nf

A Lemmy.World user informed us about an instance we are federated with that was hosting very illegal content a while back. This was a result of an attack more than a year ago, and said content federated to many other instances, which made local copies of the material. Unfortunately, when this material was taken down at the source, that action did not federate to all linked instances, meaning that there are still some instances showing this material.

Once we were made aware of this, we realized that this was likely not the only occurrence, so we started looking for other instances where this content may also still exist. We have identified more than 50 affected instances and already reached out to many of them to inform them about this content to have it taken down.

Among these instances, r.nf and lemmy.one were some of the first instances that were informed, but even after 2 months since the initial report there has been zero reaction from either instance. Both of these instances don't appear to be moderated, as evident also by posts asking whether the instance is still maintaned on lemmy.one and 2 month old spam in r.nf's main community.

The community that gets hit the hardest by this is [email protected], which is the only larger community across these instances. We recommend looking for alternative communities on other instances.

Due to the lack of action and response we have since also reported this directly to their hosting providers through Cloudflare, which includes an automatic report to NCMEC.

Even when this material will get taken down now, we don't currently believe that the instance operators are willing or able to moderate these instances properly, so we will keep them defederated unless they can convince us that they are going to moderate their instances more actively and ensure that they provide usable abuse contacts that don't require going through their hosting provider.

We also defederate from other instances from time to time due to lack of moderation and unreachable admins among other reasons. If you're interested in the reasons for our defederations, we aim to always document them on Fediseer. Be warned though, as this list contains a mentions or references to various disturbing or illegal material.

Most of those instances are either very small, don't interact with Lemmy much anyway, or are explicitly stating support of content that is incompatible with our policies.

We also usually try to reach out to affected instances prior to defederation if we believe that they may not intentionally be supporting the problematic content.

We have temporarily re-federated to lemmy.one to allow this post and https://lemmy.world/post/28173100 to federate to them. We're waiting for federation to catch up with the activities since we defederated a day ago originally before we defederate again.

Reliability of media uploads

We have recently been receiving some reports of media uploads not working from time to time. We have already addressed one of the underlying issues and are working on addressing another one currently. Please continue to let us know about issues like that to ensure that they're on our radar.

We're currently also working on improving our overall application monitoring to collect more useful information that helps us track down specific issues, improve visibility for errors, as well as hopefully allowing us to identify potential performance issues.

Parallel federation

Back in Lemmy 0.19.6, Lemmy introduced the option to send federated activities in parallel. Without this, Lemmy would only ever have one activity in the process of being transmitted to another instance. While most instances don't have a large number of activities going out, we're at the point where instances far away from us are not able to keep up with our traffic anymore due to physics limitations when waiting for data from the other side of the world.

Some instances mitigated this by setting up an external federation queue near our instance that would batch activities together to work around these limitations while this was not implemented in Lemmy and deployed on our end. Unfortunately this also meant having to maintain an additional server, which means time investment, a few bucks every month to pay, as well as another potential component that could break.

We have enabled 2 parallel sends around a week ago and aussie.zone, who were pretty much constantly lagging behind multiple days have finally caught up with us again. We will continue to monitor this and if needed increase the number of parallel sends further in the future, but so far it looks like we should be fine with 2 for a good while.

---

edit: added section about parallel federation

Hello world,

as many of you may already be aware, there is an ongoing spam attack by a person claiming to be Nicole.

It is very likely that these images are part of a larger scale harassment campaign against the person depicted in the images shared as part of this spam.

Although the spammer claims to be the person in the picture, we strongly believe that this is not the case and that they're only trying to frame them.

Starting immediately, we will remove any images depicting "Nicole" and information that may lead to identifying the real person depicted in those images to prevent any possible harassment.
This includes older posts and comments once identified.

We also expect moderators to take action if such content is reported.

While we do not intend to punish people posting this once, not being aware of the context, we may take additional actions if they continue to post this content, as we consider this to be supporting the harassment campaign.

Discussion that does not include the images themselves or references that may lead to identifying the real person behind the image will continue to be allowed.

If you receive spam PMs please continue reporting them and we'll continue working on our spam detections to attempt to identify them early before they reach many users.

Hello world,

Today we are starting an April Fools charity event called: Lemmy Silver! accessible to all users of Lemmy with an account made before today (also non-world users!).

From now on, every 24 hours, you can comment !lemmysilver under any post in participating communities (see: this post for more information), or send a PM to this bot account with (!lemmysilver [username]) to award the poster points. We will keep a score depending on the amount of votes you send and receive. More details can be found in this post.

In this post we will keep a live leaderboard. At the end of April the users with the highest score will get these prizes:

1. €150 to a charity of choice
2. €100 to a charity of choice
3. €75 to a charity of choice
4. €50 to a charity of choice
5. €25 to a charity of choice

If you are a moderator and want to add your community to the whitelist, type !whitelistsilver in the comments or in a PM to the bot account to whitelist all the communities you moderate, or send a PM to me (Thekingoflorda).

The prize fund is made up by personal donations from members of the admin team and the moderation team, no money from the Fedihosting Foundation is used for this event. If you want to contribute to the prize fund, please send me a PM.

We also made a little survey for this event, so if you have 2 minutes, please fill it out: https://app.formbricks.com/s/cm8x96xjc022vvt01xr0z9tdp

Feel free to leave any feedback here in the comments, in [email protected] or by sending them to my PMs. The bot's PM will probably not be read. Please be honest, but respectful and keep the TOS in mind.

Thank you everyone! Hope you have fun.

PS. The bot might be a bit unstable in the beginning, so please send all your complaints my way so I can fix the inevitable bugs.

Hello,

we will be updating pict-rs to the latest version in about 2 hours.

We expect a short downtime of 1-2 minutes during the planned migration window, as there are no major database changes involved.

Most users won't be affected by this, as the majority of our media is cached and served by Cloudflare. This should primarily only affect thumbnail generation and uploads of new media while the service is down.

You can convert this to your local time here: https://inmytime.zone/?iso=2025-03-28T22%3A00%3A00.000Z

---

The update has been completed successfully.

Hello,

as some of you may have noticed we just had about 25 minutes of downtime due to the update to Lemmy 0.19.10.

Lemmy release notes: https://join-lemmy.org/news/2025-03-19_-_Lemmy_Release_v0.19.10_and_Developer_AMA

This won't fix YouTube thumbnails for us, as YouTube banned all IPs belonging to our hosting provider.

We were intending to apply this update without downtime, as we're looking to apply the database migration that allows marking PMs as removed due to the recent spam waves.

Although this update contains database migrations, we expected to still be able to apply the migration in the background before updating the running software, as the database schema between the versions was backwards compatible. Unfortunately, once we started the migrations, we started seeing the site go down.

In the first minutes we assumed that the migrations contained in this upgrade were somehow unexpectedly blocking more than intended but still processing, but it turned out that nothing was actually happening on the database side. Our database deadlocked due to what appears to be an orphaned transaction, which didn't die even after we killed all Lemmy containers other than the one running the migrations.

While the orphaned transaction was pending, a pending schema migration was waiting for the previous transaction to complete or be rolled back, so nothing was moving anymore. As the previous transaction also didn't move anymore everything started to die. We're not entirely sure why the original transaction broke down, as it was started about 30 seconds before the schema migration query, which seems like that shouldn't have been broken by that happening at the same time.

Lemmy has a "replaceable" schema, which is applied separately from the regular database schema migrations, which runs every time a DB migration occurs. We unfortunately did not consider this replaceable schema migration in our planning, as we would otherwise have realized that this would likely have larger impact on the overall migration.

After we identified that the database had deadlocked, we resorted to restarting our postgres container, then run the migration again. Once we restarted the database, everything was back online in less than 30 seconds, which includes first running the remaining migrations and then starting up all containers again.

When we tested this process on our test instance prior to deploying this to the Lemmy.World production environment we did not run into this issue. Everything was working fine with the backend services running on Lemmy 0.19.9 and the database being upgraded to Lemmy 0.19.10 schema already, but the major difference here is the lack of user activity during the time of the migration.

Our learning from this is to always plan for downtime for Lemmy updates if any database migrations are included, as it does not appear to be possible to "safely" apply them even if they seem small enough to be theoretically doable without downtime.