Lemmy.world Support

3227 readers

12 users here now

Lemmy.world Support

Welcome to the official Lemmy.world Support community! Post your issues or questions about Lemmy.world here.

This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.

This community is subject to the rules defined here for lemmy.world.

To open a support ticket

You can also DM https://lemmy.world/u/lwreport or email [email protected] (PGP Supported) if you need to reach our directly to the admin team.

Follow us for server news 🐘

Outages 🔥

https://status.lemmy.world

founded 1 year ago

MODERATORS

[email protected]

community linuxmemes seems to be unmoderated (unilem.org)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

Hi there. ~~The community [email protected] seems to be unmoderated. The only registered moderator @[email protected] has been inactive since ~2 months. I'd like to be added as a mod to weed out blatantly racist and other unacceptable content like this: Lol! So true..~~ I've been a regular in r/linuxmemes, have switched to lemmy, and would like [email protected] not to become a shithole.

Edit/correction: Looking at the mod log, @[email protected] is still moderating (even if not commenting/posting). Their last mod action was 4 days ago. I've written to them with a link to this post.

Edit2: the mod is still active. Due to some bugs it looked otherwise to me.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)

Weird. I looked into lemmy.world mod log and filtered for them: the latest action shown to me was 4 days ago ... maybe a bug in the filter mechanism? Also, the post from yesterday is still visible to me on unilem.org. That seems to be a federation issue though, with posts not reliably getting removed on federated instances. If I look at linuxmemes via lemmy.world, the post is indeed gone. I saw in the mod's profile, that they posted something concerning moderation, but trying to view that only threw an error for me. The overall lemmy experience seems to be still quite buggy.

TL;DR: You are right and the mod is still active. For a slew of reasons/bugs it looked otherwise to me. But I should have looked more closely.

Anyways, I've written to them and linked to this post.

Edit:

I just checked again, to see if I made some stupid mistake. This is the filtered mod log:

And I still see the new post (and the old) which you said was removed:

If I didn't know better by now, I'd still say that linuxmemes looks unmoderated (at least on my end).

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

Good, I'm glad you wrote them and I hope you help them out with moderating the community. I might be able to see a more updated version of the modlog because I'm a moderator? Also, when I use Firefox to navigate to lemmy world on my phone I often have to reload the page because the browser loads what I had previously viewed. So, I think there could be something weird going on with web browser caches. Anyway, federation sometimes creates hiccups, also. What you can see from one instance might not be visible from another. *edit, just an afterthought. If you start helping out with moderating the linuxmemes community, my advice would be to remove any and all blocks from your settings. If you don't, you might not be able to see (and remove) rule-breaking content if someone on your block list posts something to the community.

[–] [email protected] 2 points 1 year ago

So, I think there could be something weird going on with web browser caches.

I'm quite confident, that that is not the problem.

As you can see, there's quite the gap where several entries should be.

I might be able to see a more updated version of the modlog because I'm a moderator?

Yah, maybe. I thought the mod log was completely public. But, I might be mistaken. I'll have a look at the github issues to see if this is a known problem.