We’ll get some more control over images when 1.0 comes, I will take a look at it again then, but in general the new user cooldown for image uploads has really significantly reduced the amount of image related abuse we have seen.

@Character_Locked@lemm.ee please understand, nobody on our admin team is getting paid to moderate disgusting images, they are volunteering to do it, and it takes a mental toll. Also, image hosting itself is not free. Our donations right now are barely breaking even with server costs. So realistically, our options are not “current situation vs fully unrestricted image uploads”, they are “current situation vs completely burned out admin team and costs increasing beyond donations”.

What I mean is that some posters have a bunch of alts on different instances, and if they get awards split between their accounts, then they’ll be at a bit of a disadvantage 😄

This is cool!

Any rules for alts? Can people “claim” alt accounts to sum up their votes?

I’m afraid .world users will also miss out on your mod actions in all of your communities, which is a particularly unfortunate side-effect.

I don’t think it’s the end of the world (:P), though - .world is a big instance, but there are still tons of users on other instances. I mean, even in your communities, I don’t think .world is not making up the majority of activity.

I’m not sure why .world has the 18 age requirement - AFAIK GDPR only requires 16+ if you don’t specifically ask for parental consent. Of course, there is the matter of pornography etc, but for example Reddit allows 13+ users, and all they do for pornography is show an NSFW warning, which Lemmy also has (although this is a good point - maybe the NSFW toggle should be improved to explicitly ask users to confirm their age on Lemmy as well, similarly to how it works on Reddit).

But at the end of the day, each instance is free to create whatever rules and processes they want, and to ban people according to those rules. I would say that .world admins are probably just trying to do their best in enforcing their rules, and unfortunately that means that most likely you’ll be cut off from .world for the next 5 months 🫤

Hi, there is no free speech policy on lemm.ee, we have very strict moderation when it comes to our rules. We regularly permaban users for breaking our instance rules. We simply don’t use defederation as a moderation tool, preferring other tools like user bans, for reasons outlined here: https://lemm.ee/post/35472386

Interesting! We’ve had quite a noticeable spike of sign-ups on lemm.ee as well

I think it’s not really on your side, most likely either just something wrong on kbin.social itself, OR a side-effect of the measures lemmy.world implemented against kbin.social recently.

They are basically local-only communities on lemmy.world at this point, unfortunately. There is no federation to any other instance for any lemmy.world user posts on those communities.

It’s not really a bug, it’s just a case where app developers need to update their code to support a small change in the Lemmy API. More details here: https://lemm.ee/post/34259050/12479585

It’s a full new game that you need to purchase separately, but all the marketplace stuff you’ve bought for 2020 will also come with you to 2024

We finally have a release date for Microsoft Flight Simulator 2024!

Regarding your question:

Lemmy federation basically works by copying stuff from their source instance to all other federated instances. So if I write a comment on lemm.ee, other federated instances will get their own copy of my comment. They will also all know that the “authority” for this comment is lemm.ee.

If an admin on another instance decides to delete their local copy of my comment on lemm.ee, then they are always free to do so (for example, some instances might want to moderate more strictly), but any actions they take like this are limited to their own instance - for the rest of Lemmy, lemm.ee remains the authority for this comment, so individual remote instance admins taking actions won’t have any effect on any other instances.

As for the original topic of modlog federation, basically it just boils down to this: just like with the comment example above, Lemmy instances also save a local copy of incoming federated mod logs. The Lemmy software does not yet have 100% coverage in terms of federating mod logs (for example, there are no federated logs yet for instance admins banning remote users), but this coverage has been increasing, and I expect this will eventually get to 100% (just needs more dev time really).

Also, if some instance admins try to tamper with their mod logs, then other instances can still see the real history, because there is no way for an instance admin to delete copies of their mod log from other instances.

Banning a local user from a local community does actually federate already

Most actions federate, any exceptions which aren’t federated yet are generally just there because the federation logic has not been implemented (but improvements are constantly being worked on).

Generally federating the modlog is mostly just there for informative purposes. As in, we can check what mod actions were taken on instance A through the modlog on instance B (and there is no mechanism in Lemmy for other instances to retroactively remove or hide federated modlog items, btw).

It’s the first option in the dropdown:

Big thanks to all maintainers and contributors!

That’s true, it will only show content which has been federated to lemm.ee, so indeed if you want to search for more content than is available on your instance, you would need some additional tools for that.

I’m a simple man:

“What day is it?” asked Pooh.

“It’s today,” squeaked Piglet.

“My favorite day,” said Pooh.

incorporated into the UI, rather than a piece of text in the post.

How would other instances (or other ActivityPub software) know about it if it’s not a piece of text in the post?