showing posts tagged #lemmyworld — clear

0

Call for donations for Lemmy.World (Autumn 2026)

preview

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:

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

blog.mastodon.world/september-2025-updates-for-th…

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:

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

blog.mastodon.world/september-2025-updates-for-th…

0

lemmy.org has been defederated due to lack of moderation

preview

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.

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.

0

Update: anarchist.nexus has been refederated

preview

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.

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.

0

[Completed] Lemmy.World maintenance in 35 minutes, 13th 22:30-22:45 UTC

preview

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: 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.

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: 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.

0

Call for donations for Lemmy.World

preview

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: blog.mastodon.world

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: blog.mastodon.world

0

[Resolved] Outbound federation issues

preview

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,

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.

0

[Completed] Possible Lemmy.World maintenance and update to 0.19.15 on 26th between 09:00-13:30 UTC

preview

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: 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 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: 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

0

[Completed] Lemmy.World hardware maintenance today 13:45-14:45 UTC

preview

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: 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,

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: 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

0

Update on Jordan Lund | Update 2025-10-06 01:27 UTC

preview

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 legal.lemmy.world/tos/#1-attacks-on-people-or-gro…. 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,

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 legal.lemmy.world/tos/#1-attacks-on-people-or-gro…. 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.

0

Accidental removals by automod

preview

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,

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

0

[Completed] Lemmy.World maintenance and update to 0.19.12 today 20:00-20:15 UTC

preview

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: 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.

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: 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.

0

[Lifted] Privacy Guides link ban

preview

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.

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.

0

Ending the April Fools Lemmy Silver event!

preview

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:

(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,

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:

(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 (:

0

Lemmy needs more donations

preview

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 @nutomic@lemmy.ml below:

cross-posted from: 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,

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 @nutomic@lemmy.ml below:

cross-posted from: 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.

0

[Completed] Lemmy.World maintenance and update to 0.19.11 today 21:30-21:45 UTC

preview

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: 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 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: 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.

0

Lemmy.World April update

preview

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 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 !privacyguides@lemmy.one, 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 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,

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 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 !privacyguides@lemmy.one, 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 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

0

Ban of "Nicole" images and potential doxing

preview

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,

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.

0

[NO LONGER ACTIVE] Announcing an April charity event!

preview

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: app.formbricks.com/s/cm8x96xjc022vvt01xr0z9tdp

Feel free to leave any feedback here in the comments, in !LemmySilver@lemmy.world 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 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: app.formbricks.com/s/cm8x96xjc022vvt01xr0z9tdp

Feel free to leave any feedback here in the comments, in !LemmySilver@lemmy.world 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.

0

[Completed] Lemmy.World pict-rs maintenance 2025-03-28 22:00-22:15 UTC

preview

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: inmytime.zone/?iso=2025-03-28T22%3A00%3A00.000Z


The update has been completed successfully.

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: inmytime.zone/?iso=2025-03-28T22%3A00%3A00.000Z


The update has been completed successfully.

0

Unplanned downtime and update to Lemmy 0.19.10

preview

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: join-lemmy.org/…/2025-03-19_-_Lemmy_Release_v0.19…

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.

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: join-lemmy.org/…/2025-03-19_-_Lemmy_Release_v0.19…

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.

0

[Completed] Lemmy.World update to Lemmy 0.19.9 on 16th of March, 16:00 UTC

preview

Hello,

we will be performing the long awaited update to Lemmy 0.19.9 tomorrow.

We are planning for around 1 hour of downtime between 16:00-17:00 UTC on 16th of March.

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

You can find an overview of the changes in our previous announcement here and in the Lemmy release notes:


Update 16:50 UTC:

The upgrade was successfully completed at around 16:27 UTC, but we’re still fighting with some performance issues after the upgrade. Our database and the outbound federation container are currently using significantly higher CPU than expected, which is still being investigated to identify the root cause.

Hello,

we will be performing the long awaited update to Lemmy 0.19.9 tomorrow.

We are planning for around 1 hour of downtime between 16:00-17:00 UTC on 16th of March.

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

You can find an overview of the changes in our previous announcement here and in the Lemmy release notes:


Update 16:50 UTC:

The upgrade was successfully completed at around 16:27 UTC, but we’re still fighting with some performance issues after the upgrade. Our database and the outbound federation container are currently using significantly higher CPU than expected, which is still being investigated to identify the root cause.

0

[Completed] Lemmy.World maintenance/downtime 2025-02-22 19:00-19:30 UTC

preview

Hello,

while preparation our upcoming Lemmy update we’re also be updating to a newer database version, which will provide additional performance benefits and functionality.

We are planning for around 10 minutes of downtime for the database update between 19:00-19:30 UTC on 22nd of February. This is not yet the planned Lemmy update, we will be announcing that separately when we are ready.

edit: You can convert this to your local time here: inmytime.zone/?iso=2025-02-22T19%3A00%3A00.000Z

edit 2: The database upgrade has been completed successfully.

Hello,

while preparation our upcoming Lemmy update we’re also be updating to a newer database version, which will provide additional performance benefits and functionality.

We are planning for around 10 minutes of downtime for the database update between 19:00-19:30 UTC on 22nd of February. This is not yet the planned Lemmy update, we will be announcing that separately when we are ready.

edit: You can convert this to your local time here: inmytime.zone/?iso=2025-02-22T19%3A00%3A00.000Z

edit 2: The database upgrade has been completed successfully.

0

Moderation Policy Change - Respectful Dissent

preview

There will be a new announcement soon to clarify.

Communities should not be overly moderated in order to enforce a specific narrative. Respectful disagreement should be allowed in a smaller proportion to the established narrative.

Humans are naturally inclined to believe a single narrative when they’re only presented with a single narrative. That’s the basis of how fiction works. You can’t tell someone a story if they’re questioning every paragraph. However, a well placed sentence questioning that narrative gives the reader the option to chose. They’re no longer in a story being told by one author, and they’re free to choose the narrative that makes sense to them, even if one narrative is being pushed much more heavily than the other.

Unfortunately, some malicious actors are hijacking this natural tendency to be invested in fiction, and they’re using it to create absurd, cult-like trends in non-fiction. They’re using this for various nefarious ends, to turn us against each other, to generate profit, and to affect politics both domestically and internationally.

In a fully anonymous social media platform, we can’t counter this fully. But we can prune some of the most egregious echo chambers.

We’re aware that this policy is going to be subjective. It won’t be popular in all instances. We’re going to allow some “flat earth” comments. We’re going to force some moderators to accept some “flat earth” comments. The point of this is that you should be able to counter those comments with words, and not need moderation/admin tools to do so. One sentence that doesn’t jive with the overall narrative should be easily countered or ignored.

It’s harder to just dismiss that comment if it’s interrupting your fictional story that’s pretending to be real. “The moon is upside down in Australia” does a whole lot more damage to the flat earth argument than “Nobody has crossed the ice wall” does to the truth. The purpose of allowing both of these is to help everyone get a little closer to reality and avoid incubating extreme cult-like behavior online.

A user should be able to (respectfully, infrequently) post/comment about a study showing marijuana is a gateway drug to !marijuana without moderation tools being used to censor that content.

Of course this isn’t about marijuana. There’s a small handful of self-selected moderators who are very transparently looking to push their particular narrative. And they don’t want to allow discussion. They want to function as propaganda and an incubator. Our goal is to allow a few pinholes of light into the Truman show they wish to create. When those users’ pinholes are systematically shut down, we as admins can directly fix the issue.

We don’t expect this policy to be perfect. Admins are not aware of everything that happens on our instances and don’t expect to be. This is a tool that allows us to trim the most extreme of our communities and guide them to something more reasonable. This policy is the board that we point to when we see something obscene on !yepowertrippinbastards@lemmy.dbzer0.com so that we can actually do something about it without being too authoritarian ourselves. We want to enable our users to counter the absolute BS, and be able to step in when self-selected moderators silence those reasonable people.

Some communities will receive an immediate notice with a link to this new policy. The most egregious communities will comply, or their moderators will be removed from those communities.

Moderators, if someone is responding to many root comments in every thread, that’s not “in a smaller proportion” and you’re free to do what you like about that. If their “counter” narrative posts are making up half of the posts to your community, you’re free to address that. If they’re belligerent or rude, of course you know what to do. If they’re just saying something you don’t like, respectfully, and they’re not spamming it, use your words instead of your moderation abilities.

There will be a new announcement soon to clarify.

Communities should not be overly moderated in order to enforce a specific narrative. Respectful disagreement should be allowed in a smaller proportion to the established narrative.

Humans are naturally inclined to believe a single narrative when they’re only presented with a single narrative. That’s the basis of how fiction works. You can’t tell someone a story if they’re questioning every paragraph. However, a well placed sentence questioning that narrative gives the reader the option to chose. They’re no longer in a story being told by one author, and they’re free to choose the narrative that makes sense to them, even if one narrative is being pushed much more heavily than the other.

Unfortunately, some malicious actors are hijacking this natural tendency to be invested in fiction, and they’re using it to create absurd, cult-like trends in non-fiction. They’re using this for various nefarious ends, to turn us against each other, to generate profit, and to affect politics both domestically and internationally.

In a fully anonymous social media platform, we can’t counter this fully. But we can prune some of the most egregious echo chambers.

We’re aware that this policy is going to be subjective. It won’t be popular in all instances. We’re going to allow some “flat earth” comments. We’re going to force some moderators to accept some “flat earth” comments. The point of this is that you should be able to counter those comments with words, and not need moderation/admin tools to do so. One sentence that doesn’t jive with the overall narrative should be easily countered or ignored.

It’s harder to just dismiss that comment if it’s interrupting your fictional story that’s pretending to be real. “The moon is upside down in Australia” does a whole lot more damage to the flat earth argument than “Nobody has crossed the ice wall” does to the truth. The purpose of allowing both of these is to help everyone get a little closer to reality and avoid incubating extreme cult-like behavior online.

A user should be able to (respectfully, infrequently) post/comment about a study showing marijuana is a gateway drug to !marijuana without moderation tools being used to censor that content.

Of course this isn’t about marijuana. There’s a small handful of self-selected moderators who are very transparently looking to push their particular narrative. And they don’t want to allow discussion. They want to function as propaganda and an incubator. Our goal is to allow a few pinholes of light into the Truman show they wish to create. When those users’ pinholes are systematically shut down, we as admins can directly fix the issue.

We don’t expect this policy to be perfect. Admins are not aware of everything that happens on our instances and don’t expect to be. This is a tool that allows us to trim the most extreme of our communities and guide them to something more reasonable. This policy is the board that we point to when we see something obscene on !yepowertrippinbastards@lemmy.dbzer0.com so that we can actually do something about it without being too authoritarian ourselves. We want to enable our users to counter the absolute BS, and be able to step in when self-selected moderators silence those reasonable people.

Some communities will receive an immediate notice with a link to this new policy. The most egregious communities will comply, or their moderators will be removed from those communities.

Moderators, if someone is responding to many root comments in every thread, that’s not “in a smaller proportion” and you’re free to do what you like about that. If their “counter” narrative posts are making up half of the posts to your community, you’re free to address that. If they’re belligerent or rude, of course you know what to do. If they’re just saying something you don’t like, respectfully, and they’re not spamming it, use your words instead of your moderation abilities.

0

About updating Lemmy & explanation of recent federation issues with lemmy.ml

preview

Hello World,

as many of you know, several newer Lemmy versions have been released since the once we are currently using.

As this is a rather long post, the TLDR is that we’re currently planning for late January/early February to update Lemmy.World to a newer Lemmy release.

We’re currently running Lemmy 0.19.3 with a couple patches on top to address some security or functionality issues.

As new Lemmy versions have been released, we’ve been keeping an eye on other instances’ experiences with the newer versions, as well as tracking certain issues on GitHub, which might impact stability or moderation experience.

We updated to Lemmy 0.19.3 back in March this year. At that point, 0.19.3 had been released for a little over a month already and at that point all the major issues that troubled the earlier 0.19 releases had been addressed.

Several months later, in June, Lemmy 0.19.4 was released with several new features. This was a rather big release, as a lot of changes had happened since the last release. Only 12 days later 0.19.5 was released, which fixed a few important issues with the 0.19.4 release. Unfortunately, Lemmy 0.19.5 also introduced some changes that were, and to some part are still not fully addressed.

Prior to Lemmy 0.19.4, regular users may see contents of removed or deleted comments in some situations, primarily when using third party apps. Ideally, this would have been fixed by restricting access to contents of removed comments to community moderators in the communities they moderate, as well as admins on each instance. Deleted comments will be overwritten in the database after some delay, but they might still be visible prior to that. This is especially a problem when moderators want to review previously removed comments to either potentially restore them or to understand context in a thread with multiple removed comments. Lemmy modlog does not always record individual modlog entries for bulk-removed items, such as banning a user while also removing their content would only log their ban but not the individual posts or comments that were removed.

We were considering writing a patch to restore this functionality for moderators in their communities, but this is unfortunately a rather complex task, which also explains why this isn’t a core Lemmy feature yet.

While admins can currently filter modlog for actions by a specific moderator, this functionality was lost somewhere in 0.19.4. While this isn’t something our admin team is using very frequently, it is still an important feature to have available for us for the times we need it.

This also included a few security changes for ActivityPub handling, which resulted in breaking the ability to find e.g. Mastodon posts in Lemmy communities by entering the post URL in the search. It also caused issues with changes to communities by remote moderators.

The 0.19.4 release also broke marking posts as read in Sync for Lemmy. Although this isn’t really something we consider a blocker, it’s still worth mentioning, as there are still a lot of Sync for Lemmy users out there that haven’t noticed this issue yet if they’re only active on Lemmy.World. Over the last 2 weeks we’ve had nearly 5k active Sync for Lemmy users . This is unfortunately something that will break during the upgrade, as the API has changed in upstream Lemmy.

There are also additional issues with viewing comments on posts in local communities that appear to be related to the 0.19.4/0.19.5 release, appear to be a lot more serious. There have been various reports of posts showing with zero comments in Sync, while viewing them in a browser or another client will show various comments. It’s not entirely clear to us right now what the full impact is and to what extent it can be mitigated by user actions, such as subscribing to communities. If anyone wants to research what is needed to restore compatibility and potentially even propose a patch for compatibility with both the updated and the previous API version we’ll consider applying it as a custom patch on top of the regular Lemmy release.

If there won’t be a Sync update in time for our update and we won’t have a viable workaround available, you may want to check out !lemmyapps@lemmy.world to find potential alternatives.

There were also several instances reporting performance issues after their upgrades, although they seemed to mostly have been only for a relatively short time after the upgrades and not persistent.

Lemmy 0.19.6 ended up getting released in November and introduced quite a few bug fixes and changes again, including filtering the modlog by moderator. Due to a bug breaking some DB queries, 0.19.7 was released just 7 days later to address that.

Among the issues fixed in this release were being able to resolve Mastodon URLs in the search again and remote moderators being able to update communities again.

0.19.6 also changed the way post thumbnails generated, which resulted thumbnails missing on various posts.

A month later, now we’re in December, 0.19.8 was released.

One of the issues addressed by 0.19.8 was Lemmy returning content of removed comments again for admins. For community moderators this functionality is not yet restored due to the complexity of having to check mod status in every community present in the comment listing.

At this point it seems that most of the issues have been addressed, although there seem to still be some remaining issues relating to thumbnails not reliably being created in some cases. We’ll keep an eye on any updates on that topic to see if it might be worth waiting a little longer for another fix or possibly deploying an additional patch even if it may not be part of an official Lemmy release yet at the time.

While we were backporting some security/stability related changes, including a fix for a bug that can break federation in some circumstances when a community is removed, we accidentally reverted this patch while applying another backport, which resulted in our federation with lemmy.ml breaking back in November. This issue was already addressed upstream a while back, so other instances running more recent Lemmy versions were not affected by this.

Among the new features released in the Lemmy versions we have missed out on so far, here are a couple highlights:

  • Users will be able to see and delete their uploads on their profile. This will include all uploads since we updated to 0.19.3, which is the Lemmy version that started tracking which user uploaded media.
  • Several improvements to federation code, which improve compatibility with wordpress, discourse, nodebb.
  • Fixing signed fetch for federation, enabling federation with instances that require linked instances to authenticate themselves when fetching remote resources. Not having this is something we’ve seen cause issues with a small number of mastodon instances that require this.
  • Site bans will automatically issue community bans, which means they’re more reliable to federate.
  • Deleted and removed posts and comments will no longer show up in search results.
  • Bot replies and mentions will no longer be included in notification counts when a user has blocked all bots.
  • Saved posts and comments will now be returned in the reverse order of saving them rather than the reverse order of them being created.
  • The image proxying feature has evolved to a more mature state. This feature intends to improve user privacy by reducing requests to third party websites when browsing Lemmy. We do not currently plan on enabling it with the update, but we will evaluate it later on.
  • Local only communities. We don’t currently see a good use for these, as they will prevent federation of such communities. This cuts off users on all other instances, so we don’t recommend using them unless you really want that.
  • Parallel sending of federated activities to other instances. This can be especially useful for instances on the other side of the world, where latency introduces serious bottlenecks when only sending one activity at a time. A few instances have already been using intermediate software to batch activities together, which is not standard ActivityPub behavior, but it allows them to eliminate most of the delays introduced by latency. This mostly affects instances in Australia and New Zealand, but we’ve also seen federation delays with instances in US from time to time. This will likely not be enabled immediately after the upgrade, but we’re planning to enable this shortly after.

edit: added information about sync not showing comments on posts in local communities

Hello World,

as many of you know, several newer Lemmy versions have been released since the once we are currently using.

As this is a rather long post, the TLDR is that we’re currently planning for late January/early February to update Lemmy.World to a newer Lemmy release.

We’re currently running Lemmy 0.19.3 with a couple patches on top to address some security or functionality issues.

As new Lemmy versions have been released, we’ve been keeping an eye on other instances’ experiences with the newer versions, as well as tracking certain issues on GitHub, which might impact stability or moderation experience.

We updated to Lemmy 0.19.3 back in March this year. At that point, 0.19.3 had been released for a little over a month already and at that point all the major issues that troubled the earlier 0.19 releases had been addressed.

Several months later, in June, Lemmy 0.19.4 was released with several new features. This was a rather big release, as a lot of changes had happened since the last release. Only 12 days later 0.19.5 was released, which fixed a few important issues with the 0.19.4 release. Unfortunately, Lemmy 0.19.5 also introduced some changes that were, and to some part are still not fully addressed.

Prior to Lemmy 0.19.4, regular users may see contents of removed or deleted comments in some situations, primarily when using third party apps. Ideally, this would have been fixed by restricting access to contents of removed comments to community moderators in the communities they moderate, as well as admins on each instance. Deleted comments will be overwritten in the database after some delay, but they might still be visible prior to that. This is especially a problem when moderators want to review previously removed comments to either potentially restore them or to understand context in a thread with multiple removed comments. Lemmy modlog does not always record individual modlog entries for bulk-removed items, such as banning a user while also removing their content would only log their ban but not the individual posts or comments that were removed.

We were considering writing a patch to restore this functionality for moderators in their communities, but this is unfortunately a rather complex task, which also explains why this isn’t a core Lemmy feature yet.

While admins can currently filter modlog for actions by a specific moderator, this functionality was lost somewhere in 0.19.4. While this isn’t something our admin team is using very frequently, it is still an important feature to have available for us for the times we need it.

This also included a few security changes for ActivityPub handling, which resulted in breaking the ability to find e.g. Mastodon posts in Lemmy communities by entering the post URL in the search. It also caused issues with changes to communities by remote moderators.

The 0.19.4 release also broke marking posts as read in Sync for Lemmy. Although this isn’t really something we consider a blocker, it’s still worth mentioning, as there are still a lot of Sync for Lemmy users out there that haven’t noticed this issue yet if they’re only active on Lemmy.World. Over the last 2 weeks we’ve had nearly 5k active Sync for Lemmy users . This is unfortunately something that will break during the upgrade, as the API has changed in upstream Lemmy.

There are also additional issues with viewing comments on posts in local communities that appear to be related to the 0.19.4/0.19.5 release, appear to be a lot more serious. There have been various reports of posts showing with zero comments in Sync, while viewing them in a browser or another client will show various comments. It’s not entirely clear to us right now what the full impact is and to what extent it can be mitigated by user actions, such as subscribing to communities. If anyone wants to research what is needed to restore compatibility and potentially even propose a patch for compatibility with both the updated and the previous API version we’ll consider applying it as a custom patch on top of the regular Lemmy release.

If there won’t be a Sync update in time for our update and we won’t have a viable workaround available, you may want to check out !lemmyapps@lemmy.world to find potential alternatives.

There were also several instances reporting performance issues after their upgrades, although they seemed to mostly have been only for a relatively short time after the upgrades and not persistent.

Lemmy 0.19.6 ended up getting released in November and introduced quite a few bug fixes and changes again, including filtering the modlog by moderator. Due to a bug breaking some DB queries, 0.19.7 was released just 7 days later to address that.

Among the issues fixed in this release were being able to resolve Mastodon URLs in the search again and remote moderators being able to update communities again.

0.19.6 also changed the way post thumbnails generated, which resulted thumbnails missing on various posts.

A month later, now we’re in December, 0.19.8 was released.

One of the issues addressed by 0.19.8 was Lemmy returning content of removed comments again for admins. For community moderators this functionality is not yet restored due to the complexity of having to check mod status in every community present in the comment listing.

At this point it seems that most of the issues have been addressed, although there seem to still be some remaining issues relating to thumbnails not reliably being created in some cases. We’ll keep an eye on any updates on that topic to see if it might be worth waiting a little longer for another fix or possibly deploying an additional patch even if it may not be part of an official Lemmy release yet at the time.

While we were backporting some security/stability related changes, including a fix for a bug that can break federation in some circumstances when a community is removed, we accidentally reverted this patch while applying another backport, which resulted in our federation with lemmy.ml breaking back in November. This issue was already addressed upstream a while back, so other instances running more recent Lemmy versions were not affected by this.

Among the new features released in the Lemmy versions we have missed out on so far, here are a couple highlights:

  • Users will be able to see and delete their uploads on their profile. This will include all uploads since we updated to 0.19.3, which is the Lemmy version that started tracking which user uploaded media.
  • Several improvements to federation code, which improve compatibility with wordpress, discourse, nodebb.
  • Fixing signed fetch for federation, enabling federation with instances that require linked instances to authenticate themselves when fetching remote resources. Not having this is something we’ve seen cause issues with a small number of mastodon instances that require this.
  • Site bans will automatically issue community bans, which means they’re more reliable to federate.
  • Deleted and removed posts and comments will no longer show up in search results.
  • Bot replies and mentions will no longer be included in notification counts when a user has blocked all bots.
  • Saved posts and comments will now be returned in the reverse order of saving them rather than the reverse order of them being created.
  • The image proxying feature has evolved to a more mature state. This feature intends to improve user privacy by reducing requests to third party websites when browsing Lemmy. We do not currently plan on enabling it with the update, but we will evaluate it later on.
  • Local only communities. We don’t currently see a good use for these, as they will prevent federation of such communities. This cuts off users on all other instances, so we don’t recommend using them unless you really want that.
  • Parallel sending of federated activities to other instances. This can be especially useful for instances on the other side of the world, where latency introduces serious bottlenecks when only sending one activity at a time. A few instances have already been using intermediate software to batch activities together, which is not standard ActivityPub behavior, but it allows them to eliminate most of the delays introduced by latency. This mostly affects instances in Australia and New Zealand, but we’ve also seen federation delays with instances in US from time to time. This will likely not be enabled immediately after the upgrade, but we’re planning to enable this shortly after.

edit: added information about sync not showing comments on posts in local communities

0

Media upload filter updates again

preview

Hello World,

today, @db0@lemmy.dbzer0.com has provided an update to the media upload scanner we’re using. This should reduce the amount of false positives blocked from being uploaded. We have deployed the updated version now.

While we do not have stats about false positives from before we implemented the scan when uploading, those changes did not change the overall data availability for us. Flagged images were still deleted, they were just still served by our cache in many cases. By moving this to the upload process, it has become much more effective, as previously images could persist in Cloudflare’s cache for extended periods of time, while now they won’t get cached in the first place.

Over the last week, we’ve seen a rate of roughly 6.7% uploads rejected out of around 3,000 total uploads. We’ll be able to compare numbers in a week to confirm that this has indeed improved the false positive rate.

Hello World,

today, @db0@lemmy.dbzer0.com has provided an update to the media upload scanner we’re using. This should reduce the amount of false positives blocked from being uploaded. We have deployed the updated version now.

While we do not have stats about false positives from before we implemented the scan when uploading, those changes did not change the overall data availability for us. Flagged images were still deleted, they were just still served by our cache in many cases. By moving this to the upload process, it has become much more effective, as previously images could persist in Cloudflare’s cache for extended periods of time, while now they won’t get cached in the first place.

Over the last week, we’ve seen a rate of roughly 6.7% uploads rejected out of around 3,000 total uploads. We’ll be able to compare numbers in a week to confirm that this has indeed improved the false positive rate.

0

Lemmy.World ToS and the murder of the UHC CEO

preview

Hello World,

following feedback we have received in the last few days, both from users and moderators, we are making some changes to clarify our ToS.

Before we get to the changes, we want to remind everyone that we are not a (US) free speech instance. We are not located in US, which means different laws apply. As written in our ToS, we’re primarily subject to Dutch, Finnish and German laws. Additionally, it is our discretion to further limit discussion that we don’t consider tolerable. There are plenty other websites out there hosted in US and promoting free speech on their platform. You should be aware that even free speech in US does not cover true threats of violence.

Having said that, we have seen a lot of comments removed referring to our ToS, which were not explicitly intended to be covered by our ToS. After discussion with some of our moderators we have determined there to be both an issue with the ambiguity of our ToS to some extent, but also lack of clarity on what we expect from our moderators.

We want to clarify that, when moderators believe certain parts of our ToS do not appropriately cover a specific situation, they are welcome to bring these issues up with our admin team for review, escalating the issue without taking action themselves when in doubt. We also allow for moderator discretion in a lot of cases, as we generally don’t review each individual report or moderator action unless they’re specifically brought to admin attention. This also means that content that may be permitted by ToS can at the same time be violating community rules and therefore result in moderator action. We have added a new section to our ToS to clarify what we expect from moderators.

We are generally aiming to avoid content organizing, glorifying or suggesting to harm people or animals, but we are limiting the scope of our ToS to build the minimum framework inside which we all can have discussions, leaving a broader area for moderators to decide what is and isn’t allowed in the communities they oversee. We trust the moderators judgement and in cases where we see a gross disagreement between moderatos and admins’ criteria we can have a conversation and reach an agreement, as in many cases the decision is case-specific and context matters.

We have previously asked moderators to remove content relating to jury nullification when this was suggested in context of murder or other violent crimes. Following a discussion in our team we want to clarify that we are no longer requesting moderators to remove content relating to jury nullification in the context of violent crimes when the crime in question already happened. We will still consider suggestions of jury nullification for crimes that have not (yet) happened as advocation for violence, which is violating our terms of service.

As always, if you stumble across content that appears to be violating our site or community rules, please use Lemmys report functionality. Especially when threads are very active, moderators will not be able to go through every single comment for review. Reporting content and providing accurate reasons for reports will help moderators deal with problematic content in a reasonable amount of time.

Hello World,

following feedback we have received in the last few days, both from users and moderators, we are making some changes to clarify our ToS.

Before we get to the changes, we want to remind everyone that we are not a (US) free speech instance. We are not located in US, which means different laws apply. As written in our ToS, we’re primarily subject to Dutch, Finnish and German laws. Additionally, it is our discretion to further limit discussion that we don’t consider tolerable. There are plenty other websites out there hosted in US and promoting free speech on their platform. You should be aware that even free speech in US does not cover true threats of violence.

Having said that, we have seen a lot of comments removed referring to our ToS, which were not explicitly intended to be covered by our ToS. After discussion with some of our moderators we have determined there to be both an issue with the ambiguity of our ToS to some extent, but also lack of clarity on what we expect from our moderators.

We want to clarify that, when moderators believe certain parts of our ToS do not appropriately cover a specific situation, they are welcome to bring these issues up with our admin team for review, escalating the issue without taking action themselves when in doubt. We also allow for moderator discretion in a lot of cases, as we generally don’t review each individual report or moderator action unless they’re specifically brought to admin attention. This also means that content that may be permitted by ToS can at the same time be violating community rules and therefore result in moderator action. We have added a new section to our ToS to clarify what we expect from moderators.

We are generally aiming to avoid content organizing, glorifying or suggesting to harm people or animals, but we are limiting the scope of our ToS to build the minimum framework inside which we all can have discussions, leaving a broader area for moderators to decide what is and isn’t allowed in the communities they oversee. We trust the moderators judgement and in cases where we see a gross disagreement between moderatos and admins’ criteria we can have a conversation and reach an agreement, as in many cases the decision is case-specific and context matters.

We have previously asked moderators to remove content relating to jury nullification when this was suggested in context of murder or other violent crimes. Following a discussion in our team we want to clarify that we are no longer requesting moderators to remove content relating to jury nullification in the context of violent crimes when the crime in question already happened. We will still consider suggestions of jury nullification for crimes that have not (yet) happened as advocation for violence, which is violating our terms of service.

As always, if you stumble across content that appears to be violating our site or community rules, please use Lemmys report functionality. Especially when threads are very active, moderators will not be able to go through every single comment for review. Reporting content and providing accurate reasons for reports will help moderators deal with problematic content in a reasonable amount of time.

0

Media upload filter updates

preview

Hello World,

we’ve just updated our tooling that scans uploaded images for illegal content.

We don’t expect this to cause any issues. If you do experience any issues with uploads or media in general please let us know.

This will hopefully improve the current situation where sometimes previews, thumbnails or entire images have gone missing after they were posted.

Uploads will now be scanned at the time they are created, which should result in immediate feedback when uploads are rejected.

Hello World,

we’ve just updated our tooling that scans uploaded images for illegal content.

We don’t expect this to cause any issues. If you do experience any issues with uploads or media in general please let us know.

This will hopefully improve the current situation where sometimes previews, thumbnails or entire images have gone missing after they were posted.

Uploads will now be scanned at the time they are created, which should result in immediate feedback when uploads are rejected.

0

Lemmy.World: Possible downtime Nov 25th 03:30 - 04:30 UTC

preview

Due to maintenance at our hosting provider Hetzner, there might be an outage of lemmy.world between 03:30 and 04:30 UTC on November 25th. (What’s that in my timezone?)

Status can be found at status.lemmy.world

Due to maintenance at our hosting provider Hetzner, there might be an outage of lemmy.world between 03:30 and 04:30 UTC on November 25th. (What’s that in my timezone?)

Status can be found at status.lemmy.world

0

[Resolved] Federation issues with lemmy.ml

preview

We’re aware of ongoing federation issues for activities being sent to us by lemmy.ml.

We’re currently working on the issue, but we don’t have an ETA right now.

Cloudflare is reporting 520 - Origin Error when lemmy.ml is trying to send us activities, but the requests don’t seem to properly arrive on our proxy server. This is working fine for federation with all other instances so far, but we have seen a few more requests not related to activity sending that seem to occasionally report the same error.

Right now we’re about 1.25 days behind lemmy.ml.

You can still manually resolve posts in lemmy.ml communities or comments by lemmy.ml users in our communities to make them show up here without waiting for federation, but this obviously is not something that will replace regular federation.

We’ll update this post when there is any new information available.


Update 2024-11-19 17:19 UTC:

Federation is resumed and we’re down to less than 5 hours lag, the remainder should be caught up soon.

The root cause is still not identified unfortunately.


Update 2024-11-23 00:24 UTC:

We’ve explored several different approaches to identify and/or mitigate the issue, which included replacing our primary load balancer with a new VM, updating HAproxy from the latest version packaged in Ubuntu 24.04 LTS to the latest upstream version, finding and removing a configuration option that may have prevented logging of certain errors, but we still haven’t really made any progress other than ruling out various potential issues.

We’re currently waiting for lemmy.ml admins to be available to reset federation failures at a time when we can start capturing some traffic to get more insights on the traffic that is hitting our load balancer, as the problem seems to be either between Cloudflare and our load balancer, or within the load balancer itself. Due to real life time constraints, we weren’t able to find a suitable time this evening, we expect to be able to continue with this tomorrow during the day.

As of this update we’re about 2.37 days behind lemmy.ml.

We are still not aware of similar issues on other instances.


Update 2024-11-25 12:29 UTC:

We have identified the underlying issue, where a backport for a bugfix resulting in crashes in certain circumstances was accidentally reverted when another backport was applied. We have applied this patch again and we’re receiving activities from lemmy.ml again. It may take an hour or so to catch up, but this time we should reliably be getting there again. We’re currently 4.77 days behind.

We still don’t have an explanation why the logs were missing in HAproxy after going through Cloudflare, but this shouldn’t cause any further federation issues.


Update 2024-11-25 14:31 UTC:

Federation has fully caught up again.

We’re aware of ongoing federation issues for activities being sent to us by lemmy.ml.

We’re currently working on the issue, but we don’t have an ETA right now.

Cloudflare is reporting 520 - Origin Error when lemmy.ml is trying to send us activities, but the requests don’t seem to properly arrive on our proxy server. This is working fine for federation with all other instances so far, but we have seen a few more requests not related to activity sending that seem to occasionally report the same error.

Right now we’re about 1.25 days behind lemmy.ml.

You can still manually resolve posts in lemmy.ml communities or comments by lemmy.ml users in our communities to make them show up here without waiting for federation, but this obviously is not something that will replace regular federation.

We’ll update this post when there is any new information available.


Update 2024-11-19 17:19 UTC:

Federation is resumed and we’re down to less than 5 hours lag, the remainder should be caught up soon.

The root cause is still not identified unfortunately.


Update 2024-11-23 00:24 UTC:

We’ve explored several different approaches to identify and/or mitigate the issue, which included replacing our primary load balancer with a new VM, updating HAproxy from the latest version packaged in Ubuntu 24.04 LTS to the latest upstream version, finding and removing a configuration option that may have prevented logging of certain errors, but we still haven’t really made any progress other than ruling out various potential issues.

We’re currently waiting for lemmy.ml admins to be available to reset federation failures at a time when we can start capturing some traffic to get more insights on the traffic that is hitting our load balancer, as the problem seems to be either between Cloudflare and our load balancer, or within the load balancer itself. Due to real life time constraints, we weren’t able to find a suitable time this evening, we expect to be able to continue with this tomorrow during the day.

As of this update we’re about 2.37 days behind lemmy.ml.

We are still not aware of similar issues on other instances.


Update 2024-11-25 12:29 UTC:

We have identified the underlying issue, where a backport for a bugfix resulting in crashes in certain circumstances was accidentally reverted when another backport was applied. We have applied this patch again and we’re receiving activities from lemmy.ml again. It may take an hour or so to catch up, but this time we should reliably be getting there again. We’re currently 4.77 days behind.

We still don’t have an explanation why the logs were missing in HAproxy after going through Cloudflare, but this shouldn’t cause any further federation issues.


Update 2024-11-25 14:31 UTC:

Federation has fully caught up again.

0

Open Reports & Notifying Moderators

preview

Hello World,

we know one of the most important indicators of comment and post community interest is votes. Beyond that, reports help to regulate comments and posts that go beyond down-votes and into the rule-breaking territory.

Unfortunately, Lemmy’s current reporting system has some shortcomings. Here are a few key technical points that everyone should be aware of:

  • Reports are NOT always visible to remote moderators. (See Full reports federation · Issue #4744 · LemmyNet/lemmy · GitHub)
  • Resolving reports on a remote instance does not federate if the content isn’t removed.
  • Removal only resolves reports in some cases, e.g. individual content removal. Some people remove individual content before banning the user, especially when the ban is with content removal, as individual content removals resolve reports on all instances. Bans with the remove content checkbox selected will not currently resolve reports automatically.

Our moderators are also volunteers with other demands on their time: work gets busy, people take vacations, and life outside of Lemmy goes on. But that doesn’t mean content that causes distress to users should stick around any longer than reasonable. Harmful content impacts both Lemmy.world users AND users of all other instances as well. We always strive to be good neighbors.

While the devs work on the technical issues, we can work to improve the human side of things. To help keep the reports queue manageable and help reports be resolved in a REASONABLE amount of time we will be enabling global notifications for all stale reports. Open reports older than 1 day will trigger a notification for 1 week every 2 days so as not to overwhelm community moderators endlessly. If a community moderator does not wish to receive these reports, they may simply block the bot, but we still expect them to address unresolved reports.

We expect that this feature will eventually be removed once Lemmy has a better reporting system in place.

As an aside, we recommend that all LW communities have at least two moderators so there is some redundancy in resolving reports themselves, and to reduce the workload on individual moderators. We know this can be harder for smaller communities, but this is just a recommendation.

We recommend that moderators have alt accounts on Lemmy.world to resolve reports that are from federated instances.

As always feedback is welcome. This is an active project which we really hope will benefit the community. Please feel free to reply to this thread with comments, improvements, and concerns.

Thanks!

FHF / LemmyWorld Admin team 💖

Additional mods

We recommend using the Photon front-end for adding mods to your community.

With the standard lemmy-ui, additional mods can only be appointed if the account has made a post or comment in the community.

Photon (p.lemmy.world) does not have this limitation. You can use the community sidebar, click Gear (settings) icon, then click the Team tab, and add any user as a mod.

Hello World,

we know one of the most important indicators of comment and post community interest is votes. Beyond that, reports help to regulate comments and posts that go beyond down-votes and into the rule-breaking territory.

Unfortunately, Lemmy’s current reporting system has some shortcomings. Here are a few key technical points that everyone should be aware of:

  • Reports are NOT always visible to remote moderators. (See Full reports federation · Issue #4744 · LemmyNet/lemmy · GitHub)
  • Resolving reports on a remote instance does not federate if the content isn’t removed.
  • Removal only resolves reports in some cases, e.g. individual content removal. Some people remove individual content before banning the user, especially when the ban is with content removal, as individual content removals resolve reports on all instances. Bans with the remove content checkbox selected will not currently resolve reports automatically.

Our moderators are also volunteers with other demands on their time: work gets busy, people take vacations, and life outside of Lemmy goes on. But that doesn’t mean content that causes distress to users should stick around any longer than reasonable. Harmful content impacts both Lemmy.world users AND users of all other instances as well. We always strive to be good neighbors.

While the devs work on the technical issues, we can work to improve the human side of things. To help keep the reports queue manageable and help reports be resolved in a REASONABLE amount of time we will be enabling global notifications for all stale reports. Open reports older than 1 day will trigger a notification for 1 week every 2 days so as not to overwhelm community moderators endlessly. If a community moderator does not wish to receive these reports, they may simply block the bot, but we still expect them to address unresolved reports.

We expect that this feature will eventually be removed once Lemmy has a better reporting system in place.

As an aside, we recommend that all LW communities have at least two moderators so there is some redundancy in resolving reports themselves, and to reduce the workload on individual moderators. We know this can be harder for smaller communities, but this is just a recommendation.

We recommend that moderators have alt accounts on Lemmy.world to resolve reports that are from federated instances.

As always feedback is welcome. This is an active project which we really hope will benefit the community. Please feel free to reply to this thread with comments, improvements, and concerns.

Thanks!

FHF / LemmyWorld Admin team 💖

Additional mods

We recommend using the Photon front-end for adding mods to your community.

With the standard lemmy-ui, additional mods can only be appointed if the account has made a post or comment in the community.

Photon (p.lemmy.world) does not have this limitation. You can use the community sidebar, click Gear (settings) icon, then click the Team tab, and add any user as a mod.

0

Moderation conflict involving c/vegan

preview

Intro

We would like to address some of the points that have been raised by some of our users (and by one of our communities here on Lemmy.World) on /c/vegan regarding a recent post concerning vegan diets for cats. We understand that the vegan community here on Lemmy.World is rightfully upset with what has happened. In the following paragraphs we will do our best to respond to the major points that we’ve gleaned from the threads linked here.

Links


Actions in question

Admin removing comments discussing vegan cat food in a community they did not moderate.

The comments have been restored.

The comments were removed for violating our instance rule against animal abuse (legal.lemmy.world/tos/#11-attacks-on-users). Rooki is a cat owner himself and he was convinced that it was scientific consensus that cats cannot survive on a vegan diet. This originally justified the removal.

Even if one of our admins does not agree with what is posted, unless the content violates instance rules it should not be removed. This was the original justification for action.

Removing some moderators of the vegan community

Removed moderators have been reinstated.

This was in the first place a failure of communication. It should have been clearly communicated towards the moderators why a certain action was taken (instance rules) and that the reversal of that action would not be considered (during the original incident).

The correct way forward in this case would have been an appeal to the admin team, which would have been handled by someone other than the admin initially acting on this.

We generally discuss high impact actions among team before acting on them. This should especially be the case when there is no strong urgency on the act performed. Since this was only a moderator removal and not a ban, this should have been discussed among the team prior to action.

Going forward we have agreed, as a team, to discuss such actions first, to help prevent future conflict

Posting their own opposing comment and elevating its visibility

Moderators’ and admins’ comments are flagged with flare, which is okay and by design on Lemmy. But their comments are not forced above the comments of other users for the purpose of arguing a point.

These comments were not elevated to appear before any other users comments.

In addition, Rooki has since revised his comments to be more subjective and less reactive.


Community Responses

The removed comments presented balanced views on vegan cat food, citing scientific research supporting its feasibility if done properly.

Presenting scientifically backed peer reviewed studies is 100% allowed, and encouraged. While we understand anyone can cherry pick studies, if a individual can find a large amount of evidence for their case, then by all accounts they are (in theory) technically correct.

That being said, using facts to bully others is not in good faith either. For example flooding threads with JSTOR links.

The topic is controversial but not clearly prohibited by site rules.

That is correct, at the time there was no violation of site wide rules.

Rooki’s actions appear to prioritize his personal disagreement over following established moderation guidelines.

Please see the above regarding addressing moderator policy.


Conclusions

Regarding moderator actions

We will not be removing Rooki from his position as moderator, as we believe that this is a disproportionate response for a heat-of-the-moment response.

Everybody makes mistakes, and while we do try and hold the site admin staff to a higher standard, calling for folks resignation from volunteer positions over it would not fair to them. Rooki has given up 100’s of hours of his free time to help both Lemmy.World, FHF and the Fediverse as a whole grown in far reaching ways. You don’t immediately fire your staff when they make a bad judgment call.

While we understand that this may not be good enough for some users, we hope that they can be understanding that everyone, no matter the position, can make mistakes.

We’ve also added a new by-laws section detailing the course of action users should ideally take, when conflict arises. In the event that a user needs to go above the admin team, we’ve provided a secure link to the operations team (who the admin’s report to, ultimately). See legal.lemmy.world/bylaws/#12-site-admin-issues-fo… for details.

TL;DR In the event of an admin action that is deemed unfair or overstepping, moderators can raise this with our operations team for an appeal/review.

Regarding censorship claims

Regarding the alleged censorship, comments were removed without a proper reason. This was out of line, and we will do our best to make sure that this does not happen again. We have updated our legal policy to reflect the new rules in place that bind both our user AND our moderation staff regarding removing comments and content. We WANT users to hold us accountable to the rules we’ve ALL agreed to follow, going forward. If members of the community find any of the rules we’ve set forth unreasonable, we promise to listen and adjust these rules where we can. Our terms of service is very much a living document, as any proper binding governing document should be.

Controversial topics can and should be discussed, as long as they are not causing risk of imminent physical harm. We are firm believers in the hippocratic oath of “do no harm”.

We encourage users to also list pros and cons regarding controversial viewpoints to foster better discussion. Listing the cons of your viewpoint does not mean you are wrong or at fault, just that you are able to look at the issue from another perspective and aware of potential points of criticism.

While we want to allow our users to express themselves on our platform, we also do not want users to spread mis-information that risks causing direct physical harm to another individual, origination or property owned by the before mentioned. To echo the previous statement “do no harm”.

To this end, we have updated our legal page to make this more clear. We already have provisions for attacking groups, threatening individuals and animal harm, this is a logical extension of this to both protect our users and to protect our staff from legal recourse and make it more clear to everyone. We feel this is a very reasonable compromise, and take these additional very seriously.

See Section 8 Misinformation

Sincerely,
FHF / LemmyWorld Operations Team


EDIT: Added org operations contact info

Intro

We would like to address some of the points that have been raised by some of our users (and by one of our communities here on Lemmy.World) on /c/vegan regarding a recent post concerning vegan diets for cats. We understand that the vegan community here on Lemmy.World is rightfully upset with what has happened. In the following paragraphs we will do our best to respond to the major points that we’ve gleaned from the threads linked here.

Links


Actions in question

Admin removing comments discussing vegan cat food in a community they did not moderate.

The comments have been restored.

The comments were removed for violating our instance rule against animal abuse (legal.lemmy.world/tos/#11-attacks-on-users). Rooki is a cat owner himself and he was convinced that it was scientific consensus that cats cannot survive on a vegan diet. This originally justified the removal.

Even if one of our admins does not agree with what is posted, unless the content violates instance rules it should not be removed. This was the original justification for action.

Removing some moderators of the vegan community

Removed moderators have been reinstated.

This was in the first place a failure of communication. It should have been clearly communicated towards the moderators why a certain action was taken (instance rules) and that the reversal of that action would not be considered (during the original incident).

The correct way forward in this case would have been an appeal to the admin team, which would have been handled by someone other than the admin initially acting on this.

We generally discuss high impact actions among team before acting on them. This should especially be the case when there is no strong urgency on the act performed. Since this was only a moderator removal and not a ban, this should have been discussed among the team prior to action.

Going forward we have agreed, as a team, to discuss such actions first, to help prevent future conflict

Posting their own opposing comment and elevating its visibility

Moderators’ and admins’ comments are flagged with flare, which is okay and by design on Lemmy. But their comments are not forced above the comments of other users for the purpose of arguing a point.

These comments were not elevated to appear before any other users comments.

In addition, Rooki has since revised his comments to be more subjective and less reactive.


Community Responses

The removed comments presented balanced views on vegan cat food, citing scientific research supporting its feasibility if done properly.

Presenting scientifically backed peer reviewed studies is 100% allowed, and encouraged. While we understand anyone can cherry pick studies, if a individual can find a large amount of evidence for their case, then by all accounts they are (in theory) technically correct.

That being said, using facts to bully others is not in good faith either. For example flooding threads with JSTOR links.

The topic is controversial but not clearly prohibited by site rules.

That is correct, at the time there was no violation of site wide rules.

Rooki’s actions appear to prioritize his personal disagreement over following established moderation guidelines.

Please see the above regarding addressing moderator policy.


Conclusions

Regarding moderator actions

We will not be removing Rooki from his position as moderator, as we believe that this is a disproportionate response for a heat-of-the-moment response.

Everybody makes mistakes, and while we do try and hold the site admin staff to a higher standard, calling for folks resignation from volunteer positions over it would not fair to them. Rooki has given up 100’s of hours of his free time to help both Lemmy.World, FHF and the Fediverse as a whole grown in far reaching ways. You don’t immediately fire your staff when they make a bad judgment call.

While we understand that this may not be good enough for some users, we hope that they can be understanding that everyone, no matter the position, can make mistakes.

We’ve also added a new by-laws section detailing the course of action users should ideally take, when conflict arises. In the event that a user needs to go above the admin team, we’ve provided a secure link to the operations team (who the admin’s report to, ultimately). See legal.lemmy.world/bylaws/#12-site-admin-issues-fo… for details.

TL;DR In the event of an admin action that is deemed unfair or overstepping, moderators can raise this with our operations team for an appeal/review.

Regarding censorship claims

Regarding the alleged censorship, comments were removed without a proper reason. This was out of line, and we will do our best to make sure that this does not happen again. We have updated our legal policy to reflect the new rules in place that bind both our user AND our moderation staff regarding removing comments and content. We WANT users to hold us accountable to the rules we’ve ALL agreed to follow, going forward. If members of the community find any of the rules we’ve set forth unreasonable, we promise to listen and adjust these rules where we can. Our terms of service is very much a living document, as any proper binding governing document should be.

Controversial topics can and should be discussed, as long as they are not causing risk of imminent physical harm. We are firm believers in the hippocratic oath of “do no harm”.

We encourage users to also list pros and cons regarding controversial viewpoints to foster better discussion. Listing the cons of your viewpoint does not mean you are wrong or at fault, just that you are able to look at the issue from another perspective and aware of potential points of criticism.

While we want to allow our users to express themselves on our platform, we also do not want users to spread mis-information that risks causing direct physical harm to another individual, origination or property owned by the before mentioned. To echo the previous statement “do no harm”.

To this end, we have updated our legal page to make this more clear. We already have provisions for attacking groups, threatening individuals and animal harm, this is a logical extension of this to both protect our users and to protect our staff from legal recourse and make it more clear to everyone. We feel this is a very reasonable compromise, and take these additional very seriously.

See Section 8 Misinformation

Sincerely,
FHF / LemmyWorld Operations Team


EDIT: Added org operations contact info

0

Update to Terms of Service + New Bylaws (Protections for users)

preview

Hey all,

In light of recent events concerning one of our communities (/c/vegan), we (as a team) have spent the last week working on how to address better some concerns that had arisen between the moderators of that community and the site admin team. We always strive to find a balance between the free expression of communities hosted here and protecting users from potentially harmful content.

We as a team try to stick to a general rule of respect and consideration for the physical and mental well-being of our users when drafting new rules and revising existing ones. Furthermore, we’ve done our best to try to codify these core beliefs into the additions to the ToS and a new by-laws section.

ToS Additions

That being said, we will be adding a new section to our “terms of service” concerning misinformation. While we do try to be as exact as reasonably able, we also understand that rules can be up to interpretation as well. This is a living document, and users are free to respectfully disagree. We as site admins will do our best to consider the recommendations of all users regarding potentially revising any rules.

Regarding misinformation, we’ve tried our best to capture these main ideas, which we believe are very reasonable:

  • Users are encouraged to post information they believe is true and helpful.
  • We recommend users conduct thorough research using reputable scientific sources.
  • When in doubt, a policy of “Do No Harm”, based on the Hippocratic Oath, is a good compass on what is okay to post.
  • Health-related information should ideally be from peer-reviewed, reproducible scientific studies.
    • Single studies may be valid, but often provide inadequate sample sizes for health-related advice.
    • Non-peer-reviewed studies by individuals are not considered safe for health matters.

We reserve the right to remove information that could cause imminent physical harm to any living being. This includes topics like conversion therapy, unhealthy diets, and dangerous medical procedures. Information that could result in imminent physical harm to property or other living beings may also be removed.

We know some folks who are free speech absolutists may disagree with this stance, but we need to look out for both the individuals who use this site and for the site itself.

By-laws Addition

We’ve also added a new by-laws section as well as a result of this incident. This new section is to better codify the course of action that should be taken by site and community moderators when resolving conflict on the site, and also how to deal with dormant communities.

This new section provides also provides a course of action for resolving conflict with site admin staff, should it arise. We want both the users and moderators here to feel like they have a voice that is heard, and essentially a contact point that they can feel safe going to, to “talk to the manager” type situation, more or less a new Lemmy.World HR department that we’ve created as a result of what has happened over the last week.

Please feel free to raise any questions in this thread. We encourage everyone to please take the time to read over these new additions detailing YOUR rights and how we hope to better protect everyone here.

legal.lemmy.world/tos/#80-misinformation

legal.lemmy.world/bylaws/

Sincerely,

FHF / LemmyWorld Operations Team


EDIT:

We will be releasing a separate post regarding the moderation incident in the next 24-48 hours, just getting final approval from the team.

EDIT 2 (2024-08-31):

We’ve posted a response, sorry for the delay.

👉 lemmy.world/post/19264848 👈

Hey all,

In light of recent events concerning one of our communities (/c/vegan), we (as a team) have spent the last week working on how to address better some concerns that had arisen between the moderators of that community and the site admin team. We always strive to find a balance between the free expression of communities hosted here and protecting users from potentially harmful content.

We as a team try to stick to a general rule of respect and consideration for the physical and mental well-being of our users when drafting new rules and revising existing ones. Furthermore, we’ve done our best to try to codify these core beliefs into the additions to the ToS and a new by-laws section.

ToS Additions

That being said, we will be adding a new section to our “terms of service” concerning misinformation. While we do try to be as exact as reasonably able, we also understand that rules can be up to interpretation as well. This is a living document, and users are free to respectfully disagree. We as site admins will do our best to consider the recommendations of all users regarding potentially revising any rules.

Regarding misinformation, we’ve tried our best to capture these main ideas, which we believe are very reasonable:

  • Users are encouraged to post information they believe is true and helpful.
  • We recommend users conduct thorough research using reputable scientific sources.
  • When in doubt, a policy of “Do No Harm”, based on the Hippocratic Oath, is a good compass on what is okay to post.
  • Health-related information should ideally be from peer-reviewed, reproducible scientific studies.
    • Single studies may be valid, but often provide inadequate sample sizes for health-related advice.
    • Non-peer-reviewed studies by individuals are not considered safe for health matters.

We reserve the right to remove information that could cause imminent physical harm to any living being. This includes topics like conversion therapy, unhealthy diets, and dangerous medical procedures. Information that could result in imminent physical harm to property or other living beings may also be removed.

We know some folks who are free speech absolutists may disagree with this stance, but we need to look out for both the individuals who use this site and for the site itself.

By-laws Addition

We’ve also added a new by-laws section as well as a result of this incident. This new section is to better codify the course of action that should be taken by site and community moderators when resolving conflict on the site, and also how to deal with dormant communities.

This new section provides also provides a course of action for resolving conflict with site admin staff, should it arise. We want both the users and moderators here to feel like they have a voice that is heard, and essentially a contact point that they can feel safe going to, to “talk to the manager” type situation, more or less a new Lemmy.World HR department that we’ve created as a result of what has happened over the last week.

Please feel free to raise any questions in this thread. We encourage everyone to please take the time to read over these new additions detailing YOUR rights and how we hope to better protect everyone here.

legal.lemmy.world/tos/#80-misinformation

legal.lemmy.world/bylaws/

Sincerely,

FHF / LemmyWorld Operations Team


EDIT:

We will be releasing a separate post regarding the moderation incident in the next 24-48 hours, just getting final approval from the team.

EDIT 2 (2024-08-31):

We’ve posted a response, sorry for the delay.

👉 lemmy.world/post/19264848 👈

0

[Restored] Accidental 2FA removal for LW users

preview

Hello Lemmy.World users,

yesterday we had an incident where human error lead to accidental removal of 2FA for all Lemmy.World users.
Until the mistake had been corrected and the original state had been restored where possible, 2FA was not enforced for any logins, even if the user enabled 2FA prior to this.

Timeline (all times in UTC):

Approximately at 2024-08-09 09:30 MFA had been removed for all users due to a mistake when MFA was intended to be reset for an individual user.
Around 2024-08-09 22:10 we became aware of the issue due to a user reporting that they were no longer prompted for 2FA on login. We immediately started an investigation to determine the root cause for this and discovered the mistake that was done earlier. Once the root cause was identified we started working on restoring the original state.
At 2024-08-10 01:10:00 2FA had been reactivated for all users that previously had 2FA enabled and hadn’t reactivated it on their own since. After additional investigation to identify affected users with 2FA that had logged in during this period, we have sent out individual messages with information about logins to their accounts during this period.

Although less than 2% of our active users have 2FA enabled, we are committed to keep our user accounts as secure as reasonably possible, and we will review our processes for resetting 2FA for individual users going forward to reduce the risk of this happening again in the future.
Fortunately our robust backup database backups allowed us to revert the exact state we had just before this change happened, allowing us to restore the original 2FA secrets for all affected users.
During this period, we have observed a total of 824 logins. 18 of these logins were done by 14 users who had 2FA disabled. Notifications to all affected users who we observed logins for during this period have been sent shortly after publishing this post.
2 users had reactivated their 2FA already on their own, so we have not reverted their 2FA to the previous state.

If you have any concerns that your account may have been compromised during this period due to the lack of 2FA enforcement feel free to reach out to us via email to info@lemmy.world or via PM to @lwadmin@lemmy.world.

Hello Lemmy.World users,

yesterday we had an incident where human error lead to accidental removal of 2FA for all Lemmy.World users.
Until the mistake had been corrected and the original state had been restored where possible, 2FA was not enforced for any logins, even if the user enabled 2FA prior to this.

Timeline (all times in UTC):

Approximately at 2024-08-09 09:30 MFA had been removed for all users due to a mistake when MFA was intended to be reset for an individual user.
Around 2024-08-09 22:10 we became aware of the issue due to a user reporting that they were no longer prompted for 2FA on login. We immediately started an investigation to determine the root cause for this and discovered the mistake that was done earlier. Once the root cause was identified we started working on restoring the original state.
At 2024-08-10 01:10:00 2FA had been reactivated for all users that previously had 2FA enabled and hadn’t reactivated it on their own since. After additional investigation to identify affected users with 2FA that had logged in during this period, we have sent out individual messages with information about logins to their accounts during this period.

Although less than 2% of our active users have 2FA enabled, we are committed to keep our user accounts as secure as reasonably possible, and we will review our processes for resetting 2FA for individual users going forward to reduce the risk of this happening again in the future.
Fortunately our robust backup database backups allowed us to revert the exact state we had just before this change happened, allowing us to restore the original 2FA secrets for all affected users.
During this period, we have observed a total of 824 logins. 18 of these logins were done by 14 users who had 2FA disabled. Notifications to all affected users who we observed logins for during this period have been sent shortly after publishing this post.
2 users had reactivated their 2FA already on their own, so we have not reverted their 2FA to the previous state.

If you have any concerns that your account may have been compromised during this period due to the lack of 2FA enforcement feel free to reach out to us via email to info@lemmy.world or via PM to @lwadmin@lemmy.world.

0

Messaging Site-Admins

preview

Hey everyone,

We wanted to address a common situation we’ve seen over the years with some large online forums, reaching out to moderators for questions and concerns.

Typically a good first line of contact is to use the Report button for any posts that need moderator attention. This will open a report for both the community moderators and the site admins. This is normally enough for most larger communities with active mod staff. You may also reach out to your community mods, they’re here to help. 💖

We do encourage our communities to take care of their own and want them to always feel empowered to run themselves as they see fit (provided they are following the global site rules). Issues can arise for some smaller communities with only one moderator or situations where the local mod staff is inactive for one reason or another for an extended time.

In these situations, we’ve seen folks email our ticket system, and while we will try and get back to them, this ticket system tends to get end-user support cases mixed in (as well as a low stream of spammers trying to buy ads 🙄).

What we do want, is to provide a more direct line of contact to the site-admin team, so when ANYONE needs to reach out to us when something is amiss, they can get a timely response. While the team all are on a few different platforms, this tends to create a fragmented approach of not just the WHO, but the HOW to contact us.

While we as a team use our internal chat platform, we want to find a happy middle ground between @'ing us each directly in random chats, and issues sitting for too long in our ticket system.

This new system would be for PRIVATE Messages as a supplement to our Lemmy.world Support community, which we do monitor very closely, and our ticket email info@lemmy.world, both for more technical issues. Think of it like the bat signal 🦇🎆!

To this end, we’ve created two methods for reaching the site-mod team directly.

We hope that between both an anonymous platform approach AND a secure email-based approach, we can keep everyone happy 💝

In closing, please, always try and reach out to your community mods FIRST, they usually will know best how to handle a difficult or tricky situation, and use this only when you feel you need to reach out now.


  • The FHF/Lemmy.World Admin team 💓

Hey everyone,

We wanted to address a common situation we’ve seen over the years with some large online forums, reaching out to moderators for questions and concerns.

Typically a good first line of contact is to use the Report button for any posts that need moderator attention. This will open a report for both the community moderators and the site admins. This is normally enough for most larger communities with active mod staff. You may also reach out to your community mods, they’re here to help. 💖

We do encourage our communities to take care of their own and want them to always feel empowered to run themselves as they see fit (provided they are following the global site rules). Issues can arise for some smaller communities with only one moderator or situations where the local mod staff is inactive for one reason or another for an extended time.

In these situations, we’ve seen folks email our ticket system, and while we will try and get back to them, this ticket system tends to get end-user support cases mixed in (as well as a low stream of spammers trying to buy ads 🙄).

What we do want, is to provide a more direct line of contact to the site-admin team, so when ANYONE needs to reach out to us when something is amiss, they can get a timely response. While the team all are on a few different platforms, this tends to create a fragmented approach of not just the WHO, but the HOW to contact us.

While we as a team use our internal chat platform, we want to find a happy middle ground between @'ing us each directly in random chats, and issues sitting for too long in our ticket system.

This new system would be for PRIVATE Messages as a supplement to our Lemmy.world Support community, which we do monitor very closely, and our ticket email info@lemmy.world, both for more technical issues. Think of it like the bat signal 🦇🎆!

To this end, we’ve created two methods for reaching the site-mod team directly.

We hope that between both an anonymous platform approach AND a secure email-based approach, we can keep everyone happy 💝

In closing, please, always try and reach out to your community mods FIRST, they usually will know best how to handle a difficult or tricky situation, and use this only when you feel you need to reach out now.


  • The FHF/Lemmy.World Admin team 💓
0

Planned Server Maintenance 6/30 Sunday 1700 UTC

preview

Hey all, We are planning to do a Docker upgrade tomorrow 6/30 Sunday, around 1800 UTC. The whole site will be down during the upgrade, but should only be down for a short while. Just wanted to give everyone a heads up. Thanks!

Hey all, We are planning to do a Docker upgrade tomorrow 6/30 Sunday, around 1800 UTC. The whole site will be down during the upgrade, but should only be down for a short while. Just wanted to give everyone a heads up. Thanks!

0

Looking for new Site Admins

preview

Hey everyone,

The Fedihosting Foundation is looking for a new site-admin for Lemmy.World, to help our busy team. This moderator will help with reviewing and acting on reports, weighing in on user content, and helping foster our local communities while acting as a friendly neighbor to other fediverse instances.

You also DO NOT need to have an account on one of our FHF services but WILL have to create an account after joining. Users from other sites WELCOME!

Benefits:

  • You’ll get to work with a great team of passionate kind, goofy individuals from all over the (lemmy) world!
  • We have weekly virtual hangouts where we brainstorm new ideas and catch up with each other. Community for us is not just a buzzword.
  • We can also provide work and personal references, as we are a registered legal non-profit.
  • While not a technical role, you will also gain exposure to best-in-class industry tooling and processes for large-scale hosted applications (aka modern DevOps).
  • We also run a small blog, that we’d love to have folks contribute to.
  • Join in on the editorial voice for our featured communities.
  • We also understand this is a hobby and that family and work come first
    • If you’re having a hard time finding time or are busy, we will always do our best to help and support you.

Applicants should have the following qualities:

  • Experience moderating a diverse group of individuals from many geographic, religious, and LGBTQ+ backgrounds.
  • Able to commit to at least 5-10 hours a week.
  • Excellent interpersonal skills and communication.
  • Solid background in conflict resolution.
  • Must be able to speak English.
  • Works well asynchronously with remote teams.
  • Grammar skills optional 😛

Bonus skills (which you will learn if you don’t already)

  • SQL / Business Intelligence software skills.
  • N8N workflow automation
  • Web Design (Hugo + GitHub Pages).
  • Python scripting

Application process:

  • It goes without saying that we will only be considering applicants with a significant positive history of online posts and/or comments, no trolls, please.
  • Applicants must be okay with sitting for a video interview and must pass a basic background check.
  • While not strictly required, a CV with relevant work and volunteer history will help during the application process.
  • We are an international team that works from both North America EST time (-4) and Europe CEST (+2), so we would ask that candidates be flexible with their availability.

Please apply HERE forms.gle/epTdTy9Xh9kNFKsQA

(Edit: Updated post, thanks Donuts!)

(Edit2: Thanks for all the feed back on this post, it’s much appreciated 💗💗💗)

(Edit3: If you feel like you’d fit in, apply, the req’s that we posted are more of a suggestion, then a hard yes or no)

Hey everyone,

The Fedihosting Foundation is looking for a new site-admin for Lemmy.World, to help our busy team. This moderator will help with reviewing and acting on reports, weighing in on user content, and helping foster our local communities while acting as a friendly neighbor to other fediverse instances.

You also DO NOT need to have an account on one of our FHF services but WILL have to create an account after joining. Users from other sites WELCOME!

Benefits:

  • You’ll get to work with a great team of passionate kind, goofy individuals from all over the (lemmy) world!
  • We have weekly virtual hangouts where we brainstorm new ideas and catch up with each other. Community for us is not just a buzzword.
  • We can also provide work and personal references, as we are a registered legal non-profit.
  • While not a technical role, you will also gain exposure to best-in-class industry tooling and processes for large-scale hosted applications (aka modern DevOps).
  • We also run a small blog, that we’d love to have folks contribute to.
  • Join in on the editorial voice for our featured communities.
  • We also understand this is a hobby and that family and work come first
    • If you’re having a hard time finding time or are busy, we will always do our best to help and support you.

Applicants should have the following qualities:

  • Experience moderating a diverse group of individuals from many geographic, religious, and LGBTQ+ backgrounds.
  • Able to commit to at least 5-10 hours a week.
  • Excellent interpersonal skills and communication.
  • Solid background in conflict resolution.
  • Must be able to speak English.
  • Works well asynchronously with remote teams.
  • Grammar skills optional 😛

Bonus skills (which you will learn if you don’t already)

  • SQL / Business Intelligence software skills.
  • N8N workflow automation
  • Web Design (Hugo + GitHub Pages).
  • Python scripting

Application process:

  • It goes without saying that we will only be considering applicants with a significant positive history of online posts and/or comments, no trolls, please.
  • Applicants must be okay with sitting for a video interview and must pass a basic background check.
  • While not strictly required, a CV with relevant work and volunteer history will help during the application process.
  • We are an international team that works from both North America EST time (-4) and Europe CEST (+2), so we would ask that candidates be flexible with their availability.

Please apply HERE forms.gle/epTdTy9Xh9kNFKsQA

(Edit: Updated post, thanks Donuts!)

(Edit2: Thanks for all the feed back on this post, it’s much appreciated 💗💗💗)

(Edit3: If you feel like you’d fit in, apply, the req’s that we posted are more of a suggestion, then a hard yes or no)

0

Canvas in 30 days 👀

preview

cross-posted from: toast.ooo/post/3740832

turns out I did my math wrong, so it’s a little less than 30 days

July 12th, 2024 @ midnight EDT

canvas.fediverse.events

✨ this year’s event also supports the entire fediverse not just Lemmy!

(you have to be able to make/receive text posts, like mastodon, lemmy, pixelfed, etc) (peertube accounts will not work)

you can get update announcements on other fedi platforms with @canvas@fediverse.events link

chat about Canvas on Matrix or Discord (they’re bridged)

cross-posted from: toast.ooo/post/3740832

turns out I did my math wrong, so it’s a little less than 30 days

July 12th, 2024 @ midnight EDT

canvas.fediverse.events

✨ this year’s event also supports the entire fediverse not just Lemmy!

(you have to be able to make/receive text posts, like mastodon, lemmy, pixelfed, etc) (peertube accounts will not work)

you can get update announcements on other fedi platforms with @canvas@fediverse.events link

chat about Canvas on Matrix or Discord (they’re bridged)

0

Temporarily blocking activities from kbin.social

preview

What’s the Problem?

Over the past few weeks we have been receiving large amounts of activity requests from kbin instances, primarily kbin.social. The issue is intermittent and the root cause is unknown. It appears as though some process occasionally gets stuck in a loop on the kbin side. For example, a legitimate user may upvote a post in one of our communities, causing kbin to send an upvote action, then an undo action, then an upvote action again, an undo action again, and on and on.

This is not straining lemmy.world’s infrastructure at the moment. However, it does create enough network traffic to be problematic for the Lemmy network in general because these activity requests get passed on to other instances. Some instances have already struggled to keep up with normal traffic from lemmy.world due to how Lemmy processes activity requests (see reddthat.com/post/15383278, for more info). When this kbin issue occurs it multiples our outbound traffic and makes the problem worse. The additional activity requests can easily triple the number of outgoing activities from lemmy.world to other instances.

Short-Term Fixes

As a temporary fix we are currently blocking all incoming activity requests from kbin.social.
Users on that site are effectively “read-only” in lemmy.world communities at the moment.

We are hoping to replace the current block with a rate limit on incoming kbin activities. Unfortunately, it may take a few days before the lemmy.world infrastructure team has time to implement that.

We were initially banning the individual users whose actions were being repeated, with the intention of unbanning them when the repeated requests stopped. However, the problem has persisted, and that game of whack-a-mole is manual and too time-consuming. It also gives the impression that those users had done something wrong, which is not the case.

Long-Term Solution

We have reached out to Ernest, who is the kbin dev and kbin.social admin. So far we have not received a response. Ultimately, this appears to be a bug on the kbin side. Hopefully he will be able to dig into this issue soon and resolve it. Until then, we will try to mitigate it on our end as best we can.

We apologize for the inconvenience. Thank you for bearing with us.

For some recent history regarding this issue please see these comments:
lemmy.world/comment/9081380
lemmy.world/comment/8961882
lemmy.world/comment/9330566

What’s the Problem?

Over the past few weeks we have been receiving large amounts of activity requests from kbin instances, primarily kbin.social. The issue is intermittent and the root cause is unknown. It appears as though some process occasionally gets stuck in a loop on the kbin side. For example, a legitimate user may upvote a post in one of our communities, causing kbin to send an upvote action, then an undo action, then an upvote action again, an undo action again, and on and on.

This is not straining lemmy.world’s infrastructure at the moment. However, it does create enough network traffic to be problematic for the Lemmy network in general because these activity requests get passed on to other instances. Some instances have already struggled to keep up with normal traffic from lemmy.world due to how Lemmy processes activity requests (see reddthat.com/post/15383278, for more info). When this kbin issue occurs it multiples our outbound traffic and makes the problem worse. The additional activity requests can easily triple the number of outgoing activities from lemmy.world to other instances.

Short-Term Fixes

As a temporary fix we are currently blocking all incoming activity requests from kbin.social.
Users on that site are effectively “read-only” in lemmy.world communities at the moment.

We are hoping to replace the current block with a rate limit on incoming kbin activities. Unfortunately, it may take a few days before the lemmy.world infrastructure team has time to implement that.

We were initially banning the individual users whose actions were being repeated, with the intention of unbanning them when the repeated requests stopped. However, the problem has persisted, and that game of whack-a-mole is manual and too time-consuming. It also gives the impression that those users had done something wrong, which is not the case.

Long-Term Solution

We have reached out to Ernest, who is the kbin dev and kbin.social admin. So far we have not received a response. Ultimately, this appears to be a bug on the kbin side. Hopefully he will be able to dig into this issue soon and resolve it. Until then, we will try to mitigate it on our end as best we can.

We apologize for the inconvenience. Thank you for bearing with us.

For some recent history regarding this issue please see these comments:
lemmy.world/comment/9081380
lemmy.world/comment/8961882
lemmy.world/comment/9330566

0

Feedback from all moderators

preview

Hello world!

We would like to start by saying thank you ❤, no really 🙏 THANK YOU to ALL the moderators out there!

Without you folks, we would have no one to help keep our community safe and help build the communities both here on Lemmy.World and on other fine instances. To this end, we want to make sure your voices are heard 📣 loud and clear📣.

So, in the spirit of transparency, we would like everyone to know that we are looking to help out the folks working on Sublinks. Over the last several months we have grown to be more than just Lemmy.World. We’ve added platforms such as Pixelfed and Sharkey to help offer our users more diverse options for expressing themselves online. We still are very committed to Mastodon as well.

We DO NOT plan on moving away from Lemmy as a software platform at this time. Any changes in our core services would need to be discussed extensively internally AND externally with our community members. We firmly believe in the growth of the Fediverse and without the users, there would only be software, and that’s no fun!

Sooo…

The Sublinks team has written up a little survey, which we feel is both thorough and inclusive. It covers a wide range of topics, such as user privacy, and community engagement, along with trying to gauge things that are difficult when moderating.

Also please be aware the information collected by this survey is completely anonymous. As many of us in the social sciences background know, if you want the REAL feelings of individuals, they need to feel safe to express themselves.

👉Moderation Survey HERE👈

Please feel free to comment in this thread, we will do our best to respond to any genuine questions.

We look forward to hearing from each and every one of you!

=Sincerely,
Fedihosting Foundation

PS … also if this sounds like a corporate press release to you folks, we still punk 🤘😜🤘

Hello world!

We would like to start by saying thank you ❤, no really 🙏 THANK YOU to ALL the moderators out there!

Without you folks, we would have no one to help keep our community safe and help build the communities both here on Lemmy.World and on other fine instances. To this end, we want to make sure your voices are heard 📣 loud and clear📣.

So, in the spirit of transparency, we would like everyone to know that we are looking to help out the folks working on Sublinks. Over the last several months we have grown to be more than just Lemmy.World. We’ve added platforms such as Pixelfed and Sharkey to help offer our users more diverse options for expressing themselves online. We still are very committed to Mastodon as well.

We DO NOT plan on moving away from Lemmy as a software platform at this time. Any changes in our core services would need to be discussed extensively internally AND externally with our community members. We firmly believe in the growth of the Fediverse and without the users, there would only be software, and that’s no fun!

Sooo…

The Sublinks team has written up a little survey, which we feel is both thorough and inclusive. It covers a wide range of topics, such as user privacy, and community engagement, along with trying to gauge things that are difficult when moderating.

Also please be aware the information collected by this survey is completely anonymous. As many of us in the social sciences background know, if you want the REAL feelings of individuals, they need to feel safe to express themselves.

👉Moderation Survey HERE👈

Please feel free to comment in this thread, we will do our best to respond to any genuine questions.

We look forward to hearing from each and every one of you!

=Sincerely,
Fedihosting Foundation

PS … also if this sounds like a corporate press release to you folks, we still punk 🤘😜🤘

0

Removal of piracy communities

preview

Removal of piracy communities

Hello world!

Some of you will already have noticed that we have removed some piracy related communities from Lemmy.World during the last day.

Lack of communication

First off, we want to address the lack of communication.

Not everyone in our current admin team has been with us long enough to be aware of the previous issues and discussions related to these communities and the impact this has on our community.

We should absolutely have published this announcement when or before we removed the communities, not hours later. After realizing this mistake, we would have liked to write this a lot earlier already, but we were all busy with irl things, that we just didn’t have time for it.

Lemmy.World is run by volunteers on their personal time, nobody here gets paid for what we do.

Removed communities

Next, we want to explain how we got to the decision to remove these communities.

!crackwatch@lemmy.dbzer0.com

A lot of the recent content posted to this community included images instructing users to visit a specific website to obtain a copy of the release that the post is about. These instructions were in the form of Type in Google: visit-this.domain. The domain referenced in these posts is entirely focused on video game piracy and providing people with access to copyright infringing material.

While there may be legal differences between whether one is linking to specific content on a domain or just linking to the domain itself, such as linking to en.wikipedia.org/wiki/Online_piracy compared to linking to en.wikipedia.org, we do not consider this to be clear enough in laws and previous lawsuits that linking to just the domain is acceptable, if that domain is primarily about distributing copyright infringing material. We therefore do not allow linking to such domains. Additionally, we do not see a significant difference between posting a link directly to a website and embedding said link in an image, so we treat them equally.

!piracy@lemmy.dbzer0.com

This community is, for the most part, just about discussing various topics related to piracy. We do not at all mind discussion about this topic, and if it had been limited to that, this community would be fine.

This community, however, contains a pinned Megathread post by a community moderator, which, through a few levels of a pastebin-like site, provides an aggregated overview of various sources of content. Some of these sources are entirely legal content, but it intentionally includes various other references, such as the website referred to from the CrackWatch community, which are primarily intended for copyright infringement.

lemmy.dbzer0.com is willing to accept this content on their instance, as well as the potential legal risk coming from this, which they’re free to do.

We do not plan to defederate from lemmy.dbzer0.com, but we will continue to remove communities that are directly facilitating copyright infringement. @db0@lemmy.dbzer0.com, the admin of lemmy.dbzer0.com, is a great person, and we have no problems with him as a person. This is just a matter of different risk tolerance.

!piracy@lemmy.ml

Same as !piracy@lemmy.dbzer0.com.

Why have the piracy communities been restored previously? What changed?

Currently, based on the memories of team members involved in the decision back then, it appears that there was a misunderstanding between the community moderators and Lemmy.World admins in how the community will be moderated going forward, as well as which types of content are allowed.

Lemmy.World expected/assumed that links to websites primarily focused on facilitating distribution of pirated content would be disallowed in these communities.

The community moderators however do tolerate references to such websites, as long as people are not linking to individual content directly.

We suspect that this may have been missed during our original review when restoring the communities, which lead us to previously restoring these communities.

Why now?

We have recently received a takedown request for content not directly related to these communities, but it prompted us to review other piracy related content and communities.

Terms of Service clarification

Last, as we’ve reviewed our Terms of Service, we have updated our wording here to make it more clear what is and what isn’t allowed when it comes to piracy. This was already covered by “Do not post illegal content of any type. Do not engage in any activity that may […] facilitate or provide access to illegal transactions” in section 4, but we have now added section 4.1 to better explain this.

We apologize for the delays in communication.

Removal of piracy communities

Hello world!

Some of you will already have noticed that we have removed some piracy related communities from Lemmy.World during the last day.

Lack of communication

First off, we want to address the lack of communication.

Not everyone in our current admin team has been with us long enough to be aware of the previous issues and discussions related to these communities and the impact this has on our community.

We should absolutely have published this announcement when or before we removed the communities, not hours later. After realizing this mistake, we would have liked to write this a lot earlier already, but we were all busy with irl things, that we just didn’t have time for it.

Lemmy.World is run by volunteers on their personal time, nobody here gets paid for what we do.

Removed communities

Next, we want to explain how we got to the decision to remove these communities.

!crackwatch@lemmy.dbzer0.com

A lot of the recent content posted to this community included images instructing users to visit a specific website to obtain a copy of the release that the post is about. These instructions were in the form of Type in Google: visit-this.domain. The domain referenced in these posts is entirely focused on video game piracy and providing people with access to copyright infringing material.

While there may be legal differences between whether one is linking to specific content on a domain or just linking to the domain itself, such as linking to en.wikipedia.org/wiki/Online_piracy compared to linking to en.wikipedia.org, we do not consider this to be clear enough in laws and previous lawsuits that linking to just the domain is acceptable, if that domain is primarily about distributing copyright infringing material. We therefore do not allow linking to such domains. Additionally, we do not see a significant difference between posting a link directly to a website and embedding said link in an image, so we treat them equally.

!piracy@lemmy.dbzer0.com

This community is, for the most part, just about discussing various topics related to piracy. We do not at all mind discussion about this topic, and if it had been limited to that, this community would be fine.

This community, however, contains a pinned Megathread post by a community moderator, which, through a few levels of a pastebin-like site, provides an aggregated overview of various sources of content. Some of these sources are entirely legal content, but it intentionally includes various other references, such as the website referred to from the CrackWatch community, which are primarily intended for copyright infringement.

lemmy.dbzer0.com is willing to accept this content on their instance, as well as the potential legal risk coming from this, which they’re free to do.

We do not plan to defederate from lemmy.dbzer0.com, but we will continue to remove communities that are directly facilitating copyright infringement. @db0@lemmy.dbzer0.com, the admin of lemmy.dbzer0.com, is a great person, and we have no problems with him as a person. This is just a matter of different risk tolerance.

!piracy@lemmy.ml

Same as !piracy@lemmy.dbzer0.com.

Why have the piracy communities been restored previously? What changed?

Currently, based on the memories of team members involved in the decision back then, it appears that there was a misunderstanding between the community moderators and Lemmy.World admins in how the community will be moderated going forward, as well as which types of content are allowed.

Lemmy.World expected/assumed that links to websites primarily focused on facilitating distribution of pirated content would be disallowed in these communities.

The community moderators however do tolerate references to such websites, as long as people are not linking to individual content directly.

We suspect that this may have been missed during our original review when restoring the communities, which lead us to previously restoring these communities.

Why now?

We have recently received a takedown request for content not directly related to these communities, but it prompted us to review other piracy related content and communities.

Terms of Service clarification

Last, as we’ve reviewed our Terms of Service, we have updated our wording here to make it more clear what is and what isn’t allowed when it comes to piracy. This was already covered by “Do not post illegal content of any type. Do not engage in any activity that may […] facilitate or provide access to illegal transactions” in section 4, but we have now added section 4.1 to better explain this.

We apologize for the delays in communication.

0

[Fixed] Issue with image upload/display

preview

Currently we have an images issue. Our Wasabi (S3) account was disabled because of some illegal content that was found, we’re working with them to get the account re-enabled and the content removed.

[Update 20240308 14:47 UTC] The issue has been fixed.

Currently we have an images issue. Our Wasabi (S3) account was disabled because of some illegal content that was found, we’re working with them to get the account re-enabled and the content removed.

[Update 20240308 14:47 UTC] The issue has been fixed.

0

[Fixed] Donation platforms for Lemmy.World

Mastodon Ruud (@ruud@mastodon.world) mastodon.world
preview

There’s some unrest because the Open Collective Foundation is stopping.

Don’t worry, we use Open Collective Europe as a donations platform, they’re going nowhere.

We’ve added some donation platforms, so if you would like to support us running our .world servers, you can do so here:

And for those wanting to donate crypto:

  • Monero address: 83tnuFN4f28jRxTBW9qGDad2U23qNE5nfeW4Pfyd85oWMW7J9gqpXi3S8FDbX5uEeCAKcGnSpS2XT5dGwYiELthg8XuDrxH
  • Cardano address: addr1v9qv6xvfwcx9ny56uag4umu6238sw2e7ff2kcxl3qe7p9esayjxgu

Thank you!

[Edit] Some of the links were broken, they should now all work! [Edit 20240314: Added Liberapay]

There’s some unrest because the Open Collective Foundation is stopping.

Don’t worry, we use Open Collective Europe as a donations platform, they’re going nowhere.

We’ve added some donation platforms, so if you would like to support us running our .world servers, you can do so here:

And for those wanting to donate crypto:

  • Monero address: 83tnuFN4f28jRxTBW9qGDad2U23qNE5nfeW4Pfyd85oWMW7J9gqpXi3S8FDbX5uEeCAKcGnSpS2XT5dGwYiELthg8XuDrxH
  • Cardano address: addr1v9qv6xvfwcx9ny56uag4umu6238sw2e7ff2kcxl3qe7p9esayjxgu

Thank you!

[Edit] Some of the links were broken, they should now all work! [Edit 20240314: Added Liberapay]

0

[Update] Version 0.19 Upgrade - Done!

preview

[Update - March 3rd 2024 , 21:14 CET]

The update seems to have worked well. The database migration took some time, but after that it looks everything works as far as we tested. Let us know what you think! And if you like our work, check the donations links in the sidebar ;-)

(As you might notice, the new comments are shown YELLOW, that’s not a bug, it’s apparently a new feature in Lemmy…)


Hey everyone,

We wanted to announce that we will be attempting to upgrade Lemmy.World to version 0.19.3 on Sunday. The update will start at 2024-03-03 1900 UTC and should hopefully take no more than 2 hours. In the event there are issues, we will roll back to 0.18.5. In the event of a roll back, any data created by users will be lost, so we’ll try our best to avoid this!

Hopefully downtime should be minimal <3

During the upgrade, please feel free to make yourself at home on our Matrix and Discord chat rooms.

Lemmy.World Pub

Matrix

Please follow Lemmy.World (@LemmyWorld@mastodon.world) - Mastodon for updates.

As usual, status can be tracked by visiting dash.lemmy.world and status.lemmy.world

Thanks for your patience in waiting for us. Stability is king for us!

-LW Tech Group

[Update - March 3rd 2024 , 21:14 CET]

The update seems to have worked well. The database migration took some time, but after that it looks everything works as far as we tested. Let us know what you think! And if you like our work, check the donations links in the sidebar ;-)

(As you might notice, the new comments are shown YELLOW, that’s not a bug, it’s apparently a new feature in Lemmy…)


Hey everyone,

We wanted to announce that we will be attempting to upgrade Lemmy.World to version 0.19.3 on Sunday. The update will start at 2024-03-03 1900 UTC and should hopefully take no more than 2 hours. In the event there are issues, we will roll back to 0.18.5. In the event of a roll back, any data created by users will be lost, so we’ll try our best to avoid this!

Hopefully downtime should be minimal <3

During the upgrade, please feel free to make yourself at home on our Matrix and Discord chat rooms.

Lemmy.World Pub

Matrix

Please follow Lemmy.World (@LemmyWorld@mastodon.world) - Mastodon for updates.

As usual, status can be tracked by visiting dash.lemmy.world and status.lemmy.world

Thanks for your patience in waiting for us. Stability is king for us!

-LW Tech Group

0

Content / Image posting restrictions (based on network)

preview

Just wanted to keep everyone in the loop. If you encounter an issue where you cannot post or comment, but voting is functioning correctly, it is most likely because we have implemented a block for VPN & Tor users. If you are using these services, you can still take part in activities such as voting, reporting posts, and performing other passive actions on the site. We implemented this restriction because of users posting illegal content.

See lemmy.world/post/11571711

While we value our users’ right to privacy, we also prioritize the protection of both ourselves and our users. We want to emphasize that we weigh the pros and cons of restrictions like these with the entire team. We do not take these actions lightly, and we hope everyone understands the reasoning behind it.

Just wanted to keep everyone in the loop. If you encounter an issue where you cannot post or comment, but voting is functioning correctly, it is most likely because we have implemented a block for VPN & Tor users. If you are using these services, you can still take part in activities such as voting, reporting posts, and performing other passive actions on the site. We implemented this restriction because of users posting illegal content.

See lemmy.world/post/11571711

While we value our users’ right to privacy, we also prioritize the protection of both ourselves and our users. We want to emphasize that we weigh the pros and cons of restrictions like these with the entire team. We do not take these actions lightly, and we hope everyone understands the reasoning behind it.

0

Recently posts that go against our ToS policies and ethics

preview

Dear Lemmy.world Community,

Recently posts were made to the AskLemmy community that go against not just our own policies but the basic ethics and morals of humanity as a whole. We acknowledge the gravity of the situation and the impact it may have had on our users. We want to assure you that we take this matter seriously and are committed to making significant improvements to prevent such incidents in the future. Considering I’m reluctant to say exactly what these horrific and repugnant images were, I’m sure you can probably guess what we’ve had to deal with and what some of our users unfortunately had to see. I’ll add the thing we’re talking about in spoilers to the end of the post to spare the hearts and minds of those who don’t know.

Our foremost priority is the safety and well-being of our community members. We understand the need for a swift and effective response to inappropriate content, and we recognize that our current systems, protocols and policies were not adequate. We are immediately taking immediate steps to strengthen our moderation and administrative teams, implementing additional tools, and building enhanced pathways to ensure a more robust and proactive approach to content moderation. Not to mention ensuring ways that these reports are seen more quickly and succinctly by mod and admin teams.

The first step will be limiting the image hosting sites that Lemmy.world will allow. We understand that this can cause frustration for some of our users but we also hope that you can understand the gravity of the situation and why we find it necessary. Not just to protect all of our users from seeing this but also to protect ourselves as a site. That being said we would like input in what image sites we will be whitelisting. While we run a filter over all images uploaded to Lemmy.world itself, this same filter doesn’t apply to other sites which leads to the necessity of us having to whitelist sites.

This is a community made by all of us, not just by the admins. Which leads to the second step. We will be looking for more moderators and community members that live in more diverse time zones. We recognize that at the moment it’s relatively heavily based between Europe and North America and want to strengthen other time zones to limit any delays as much as humanly possible in the future.

We understand that trust is essential, especially when dealing with something as awful as this, and we appreciate your patience as we work diligently to rectify this situation. Our goal is to create an environment where all users feel secure and respected and more importantly safe. Your feedback is crucial to us, and we encourage you to continue sharing your thoughts and concerns.

Every moment is an opportunity to learn and build, even the darkest ones.

Thank you for your understanding.


Sincerely,

The Lemmy.world Administration

Legal / ToS

spoiler

CSAM ___

Dear Lemmy.world Community,

Recently posts were made to the AskLemmy community that go against not just our own policies but the basic ethics and morals of humanity as a whole. We acknowledge the gravity of the situation and the impact it may have had on our users. We want to assure you that we take this matter seriously and are committed to making significant improvements to prevent such incidents in the future. Considering I’m reluctant to say exactly what these horrific and repugnant images were, I’m sure you can probably guess what we’ve had to deal with and what some of our users unfortunately had to see. I’ll add the thing we’re talking about in spoilers to the end of the post to spare the hearts and minds of those who don’t know.

Our foremost priority is the safety and well-being of our community members. We understand the need for a swift and effective response to inappropriate content, and we recognize that our current systems, protocols and policies were not adequate. We are immediately taking immediate steps to strengthen our moderation and administrative teams, implementing additional tools, and building enhanced pathways to ensure a more robust and proactive approach to content moderation. Not to mention ensuring ways that these reports are seen more quickly and succinctly by mod and admin teams.

The first step will be limiting the image hosting sites that Lemmy.world will allow. We understand that this can cause frustration for some of our users but we also hope that you can understand the gravity of the situation and why we find it necessary. Not just to protect all of our users from seeing this but also to protect ourselves as a site. That being said we would like input in what image sites we will be whitelisting. While we run a filter over all images uploaded to Lemmy.world itself, this same filter doesn’t apply to other sites which leads to the necessity of us having to whitelist sites.

This is a community made by all of us, not just by the admins. Which leads to the second step. We will be looking for more moderators and community members that live in more diverse time zones. We recognize that at the moment it’s relatively heavily based between Europe and North America and want to strengthen other time zones to limit any delays as much as humanly possible in the future.

We understand that trust is essential, especially when dealing with something as awful as this, and we appreciate your patience as we work diligently to rectify this situation. Our goal is to create an environment where all users feel secure and respected and more importantly safe. Your feedback is crucial to us, and we encourage you to continue sharing your thoughts and concerns.

Every moment is an opportunity to learn and build, even the darkest ones.

Thank you for your understanding.


Sincerely,

The Lemmy.world Administration

Legal / ToS

spoiler

CSAM ___

0

Version 0.19.X Deployment

preview

Version 0.19.X Deployment

Hello world!

I’m sure many of you fine folks have been wondering why we have not upgraded to version 0.19.X yet.

The whole team here has been getting asked this question quite a bit, from both members of the community and other instance admins. We want everyone to know, YES, we will upgrade to version 0.19.

We do not have a hard date set for when we will be upgrading as of yet, as we have about 7 associated task items that go along with this upgrade for things we need to double-check and confirm there will be no breakage.

Another big reason why we have not upgraded is due to reports from other instance admins that the front-end GUI can have performance issues. While a large portion of folks access our site using apps on their phones, we would rather not degrade the user experience for the rest of everyone else.

Worst case in terms of UI slowness, we would ask everyone to use either Alexandrite () or Photon () to mitigate the potential performance issues.

One final point to mention to address the delay is that we usually wait 1-2 weeks after a new release before applying it to production. This was complicated by the fact that there were multiple releases right after each other, with each new release having issues we hoped would be patched in the NEXT version. A new version would come up, and we would have to evaluate the stability and performance of it, which would take about 2 weeks, and then ANOTHER version would come out, which we would need to test. This was further complicated by the fact this was during the holiday season.

Version Release Date
0.19.0 2023-12-15
0.19.1 2023-12-20
0.19.2 2024-01-10
0.19.3 2024-01-24

For us, stability is paramount, as we care very much about keeping everyone happy here.

While we can appreciate the rapid release of patches on 0.19, I hope everyone can now understand the delay. If all goes well, we will set a release day in the next week or two, most likely on a Saturday around 1800 UTC.

-jelloeater85

Version 0.19.X Deployment

Hello world!

I’m sure many of you fine folks have been wondering why we have not upgraded to version 0.19.X yet.

The whole team here has been getting asked this question quite a bit, from both members of the community and other instance admins. We want everyone to know, YES, we will upgrade to version 0.19.

We do not have a hard date set for when we will be upgrading as of yet, as we have about 7 associated task items that go along with this upgrade for things we need to double-check and confirm there will be no breakage.

Another big reason why we have not upgraded is due to reports from other instance admins that the front-end GUI can have performance issues. While a large portion of folks access our site using apps on their phones, we would rather not degrade the user experience for the rest of everyone else.

Worst case in terms of UI slowness, we would ask everyone to use either Alexandrite () or Photon () to mitigate the potential performance issues.

One final point to mention to address the delay is that we usually wait 1-2 weeks after a new release before applying it to production. This was complicated by the fact that there were multiple releases right after each other, with each new release having issues we hoped would be patched in the NEXT version. A new version would come up, and we would have to evaluate the stability and performance of it, which would take about 2 weeks, and then ANOTHER version would come out, which we would need to test. This was further complicated by the fact this was during the holiday season.

Version Release Date
0.19.0 2023-12-15
0.19.1 2023-12-20
0.19.2 2024-01-10
0.19.3 2024-01-24

For us, stability is paramount, as we care very much about keeping everyone happy here.

While we can appreciate the rapid release of patches on 0.19, I hope everyone can now understand the delay. If all goes well, we will set a release day in the next week or two, most likely on a Saturday around 1800 UTC.

-jelloeater85

0

Happy 2024!

preview

Hello World!

We want to wish you all a great new year! We also want to look back on 2023 and the amazing things that have happened here on Lemmy.World and the rest of the Lemmyverse.

We couldn’t have begun to dream of the amazing community we have built here. The self-destruction that has been happening on Reddit has been the opportunity of a lifetime to create an amazing community here. We hope everyone who migrated over has found a great place to share, scroll and upvote here on Lemmy.

The numbers have been amazing:

  • Almost 150k accounts here on Lemmy.World
  • 212k posts and 1.66 million comments
  • Almost 10k communities

We think next year will be even better! You can help us achieve that by simply being yourself and posting as much as you want. A special thanks to all the moderators that have kept the communities rolling. Don’t hesitate to thank them for their contributions.

Our donors allow Lemmy.World to stay truly free and accessible for everyone! Thank you to every single one of them. Also thank you to everyone who donated to the team that created Lemmy itself, funding the development of this platform with huge potential.

We hope 2024 will be great for everyone! Thank you for being such an amazing community.

~ The admin and community teams

Hello World!

We want to wish you all a great new year! We also want to look back on 2023 and the amazing things that have happened here on Lemmy.World and the rest of the Lemmyverse.

We couldn’t have begun to dream of the amazing community we have built here. The self-destruction that has been happening on Reddit has been the opportunity of a lifetime to create an amazing community here. We hope everyone who migrated over has found a great place to share, scroll and upvote here on Lemmy.

The numbers have been amazing:

  • Almost 150k accounts here on Lemmy.World
  • 212k posts and 1.66 million comments
  • Almost 10k communities

We think next year will be even better! You can help us achieve that by simply being yourself and posting as much as you want. A special thanks to all the moderators that have kept the communities rolling. Don’t hesitate to thank them for their contributions.

Our donors allow Lemmy.World to stay truly free and accessible for everyone! Thank you to every single one of them. Also thank you to everyone who donated to the team that created Lemmy itself, funding the development of this platform with huge potential.

We hope 2024 will be great for everyone! Thank you for being such an amazing community.

~ The admin and community teams

0

[Done] Pictrs Migration- Between NOW and 1700 UTC Image Upload Disabled

preview

Hi all, We will be attempting to migrate Pict-rs tomorrow starting at 1700 UTC. Between now and 1700, image uploads will be disabled to try and avoid any data loss. You will still be able to like, comment and post until then. During the upgrade window, Pict-rs will be offline, so viewing images might not work. In theory CloudFlares CDN cache should cover us during the window, but YMMV. Hopefully everything should go smooth, but we do our best to make sure we have backups!

You can monitor our site health at dash.lemmy.world and status.lemmy.world

We will post updates to mastodon.world/@LemmyWorld as well.

Cheers, LW Infra Team 💗

Update This change is done. Images are now hosted on S3 storage and uploads are re-enabled.

Hi all, We will be attempting to migrate Pict-rs tomorrow starting at 1700 UTC. Between now and 1700, image uploads will be disabled to try and avoid any data loss. You will still be able to like, comment and post until then. During the upgrade window, Pict-rs will be offline, so viewing images might not work. In theory CloudFlares CDN cache should cover us during the window, but YMMV. Hopefully everything should go smooth, but we do our best to make sure we have backups!

You can monitor our site health at dash.lemmy.world and status.lemmy.world

We will post updates to mastodon.world/@LemmyWorld as well.

Cheers, LW Infra Team 💗

Update This change is done. Images are now hosted on S3 storage and uploads are re-enabled.