kersploosh

You are correct that my first point was incorrect. I just learned that the level of detail in the modlog is configurable and varies by instance. For example, if I look at literature.cafe all modlog actions are performed by "mod." On lemmy.world, though, some of those same actions are performed by "admin."

From Lemmy you can see the accounts, but usually not their content (see note below). @[email protected]
@[email protected]

Interaction between Lemmy and Mastodon doesn't work well because the two services structure their content differently. Lemmy is community based and Mastodon is user based. Lemmy doesn't have a mechanism to follow an individual user, and Mastodon doesn't have an analog to communities (afaik).

(Note: In the case of these two accounts, some of their toots are visible because they have been pulled into the [email protected] community as part of an experiment to bridge Lemmy and Mastodon.)

What you see in the modlog depends on your role.

• If you are a regular user, or are not logged in, the modlog shows all actions as performed by "mod" regardless of who did it.
• If you are a community moderator, you see who performed each action within your community. But you don't get that level of visibility in other communities or at the instance level (I think).
• If you are an admin, you see everything: which user performed each removal or ban, in any community, on any federated instance.

The effect of bans and content removals depends on the actor's role.

• As @[email protected] mentioned, community mods can only perform community bans.
• Actions performed by an admin from a remote instance are local to that remote instance. A site ban means you can no longer interact with communities on that instance. If your posts/comments are "removed" they will be hidden from users on that instance but still be visible to users on other instances.
• Actions performed by an admin on you home instance are global. If you are site banned, or your content is removed, those actions federate to other instances. You are effectively banned everywhere and your removed content is hidden from everyone. (Of course this assumes everything federates properly.)

At this point I think I'll leave those posts deleted. OP changed the post titles before deleting, then subsequently deleted their account and all comments, so the discussions in those posts are full of holes.

I only see Blaze in the modlog, and that user has been unbanned. If you are aware of other users that are somehow not in the modlog then let me know.

Yes, Blaze has been unbanned from the community.

Done.

It's in the "Blocked Instances" section, where it should be.

It seems to be working for me. Can you confirm that it's still broken on your end? I know there was a server hiccup on your home instance yesterday causing some odd behavior; maybe that was the culprit?

sh.itjust.works explicitly blocks Threads. They held a vote among the local users: https://sh.itjust.works/post/11308397

It is odd that threads.net appears on our instances page, while the same is not true for other Lemmy instances which have not blocked Threads. Lemmy.world is federated with Threads by default simply because it is not on our instance block list. I do not believe our instance has done anything special to force a link with Threads. I mentioned it in our admin chat and will update this post if I learn anything.

However, even with threads.net listed on our instances page, Threads does not seem to work with Lemmy. I am able to search and view Mastodon user profiles from lemmy.world, but it does not work for any of the Threads test profiles.

Edit: The lemmy.world database has no records for a person on threads.net. Our best guess is that a Threads user tried to interact with lemmy.world. Perhaps the process got far enough for our instance to recognize threads.net and add it to our instances list, but not far enough to create a record of the user in our DB.

Done. You are now the new mod of [email protected].

On a related note, I recommend using to a lemmy.world account to moderate a lemmy.world community. Reports do not federate across instances Lemmy bug #3781, so you will not see reports that may be created in your community. If you decide to create a lemmy.world account you should now be able to give it mod rights by yourself. If it doesn't work then let me know and I can help. Sometimes adding/removing mod rights is buggy across instances, too.