Outages 🔥

https://status.lemmy.world/


💓 https://fedihosting.foundation/

aspe:keyoxide.org:EFWMPEN4N66VBK5WGFM5FOZXXQ

  • 9 posts
  • 0 comments
Joined 3 years ago
Cake day: June 14th, 2023

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:

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:

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 !news@lemmy.world, !world@lemmy.world and !politics@lemmy.world. 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 @MrKaplan@lemmy.world 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 @lwreport@lemmy.world. 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. !politics@lemmy.world: This community has active moderators above Jordan Lund, such as @aidan@lemmy.world.
  2. !news@lemmy.world This community has active moderators above Jordan Lund, such as @JonsJava@lemmy.world.
  3. !world@lemmy.world: We have moved Jordan from being top moderator to being bottom moderator. New top moderator is @Tenthrow@lemmy.world.
  4. !business@lemmy.world: No other active mods
  5. !comicbooks@lemmy.world: No other active mods
  6. !portland_oregon@lemmy.world: No other active mods
  7. !thepoliceproblem@lemmy.world: We have moved Jordan from being top moderator to being bottom moderator. New (active) top moderator is @JonsJava@lemmy.world.
  8. !hottubs@lemmy.world: No other active mods
  9. !keeptrack@lemmy.world: 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,

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.