I was reading an external thread only to waste time troubleshooting why I couldn't retrive the comment, when our modlog is missing the reason they are banned here.

If our instance will ban specific users from external instances, I would love to have a /c/ or /metalog where we can read the reasons specific users were banned from our instance. This is general request, and not a sole external user I used as an example. It just felt weird I couldn't even find out why that user was banned, and if it's a glitch in piefed or something. Going forward, I would love accountability for those instances, even whole /c/s we will ban and defed with.

I apologize in advance if my English is bad. I am still getting my ropes up regarding piefed.

all 4 comments

sorted by: hot top controversial new old
[–] 2 points 6 months ago* (3 children)

Do you mind sharing who the user was? (You can PM if you would like). I have noticed in the past users that I have not banned, have ended up banned and am wondering if this is the case again.

As far as I know, I have listed all ban reasons in the modlog.

  • source
  • hideshow 3 child comments
  • [–] [S] 2 points 6 months ago (2 children)

    In the e.g., it was cassandrafatigue@lemmy.dbzer0.com . I don't know them. I just found the source insightful . I would love to know if it is not a piefed glitch, then that going forward, we can have an accountability community or log, so we can read the reasonings.

    When I moderated issues instance wide, I made detailed reports on why I did things, and the reasonings behind them, so others can discuss it, and gauge their own decisions. This was on a network that properly implemented granular federatational moderation. That network no longer exists for multiple reasons. I can be DM’ed if you want more info on that network.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 6 months ago* (1 child)

    Ah I see. There was an issue with users being banned from their host instance not getting the unban federated out to PieFed, I think that's been fixed now but it looks like it's not applied retroactively. I've manually unbanned them from our end.

    I'm actually working with some others on a tool to help with instances tracking bans/users and moderation logging. That could be useful with working on my current project.

  • source
  • parent
  • hideshow 1 child comment