PieFed Meta

4668 readers

47 users here now

Discuss PieFed project direction, provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics.

Wiki

founded 2 years ago

MODERATORS

rimu@piefed.social

Receiving moderator reports for users and communities outside of expected scope (lazysoci.al)

submitted 2 weeks ago* (last edited 2 weeks ago) by lazyadmin@lazysoci.al to c/piefed_meta@piefed.social

2 comments fedilink hide all child comments

Hoping someone can help here.

WomensStuff was migrated from my instance using piefed migration tools some months ago, however I still get all the reports for their community even though I am not the instance admin, the post/commenter is not from my instance, and the reporter is not on my instance.

Example:

I have reached out to @LadyButterfly@piefed.blahaj.zone and then @ada@piefed.blahaj.zone but got no response.

Whilst WomensStuff has a logical reason, they were migrated from lazysoci.al, I am also receiving the odd report for other communities not associated with us, but every time the reporter is a piefed user. Coincidence maybe?

Another example:

I'm thinking this is a piefed issue, has anyone else had the same problem?

top 2 comments

sorted by: hot top controversial new old

[–] wjs018@piefed.wjs018.xyz 7 points 2 weeks ago (1 children)

This is happening because at least one user from your instance is a moderator for the community. This issue has been reported previously to us in matrix. Here is the relevant issue on codeberg. I have previously tried to figure out what is causing this to happen to no avail. It seems like whenever PieFed tries to send a report to a moderator, lemmy will also send it to the admins on that instance.

Maybe if @rimu@piefed.social gets a chance to dig into this some more, he can figure out how to prevent the reports from escalating to admins when they should stay at the mod level.

[–] lazyadmin@lazysoci.al 5 points 2 weeks ago

Thanks @wjs018@piefed.wjs018.xyz for the explanation. At least its a known issue, I'll put up with it for now.