If I go to ban a user, it shows successful in the app, but no mod logs will show the user banned, and they’re able to continue to post- after a ban via Voyager app

I have to go outside of voyager to do any ban moderation. Has this always been a thing?

EDIT: it seems it works fine for permanent bans. But not for temporary bans.

  • recursive_recursion they/them@lemmy.caEnglish
    1·
    1 month ago

    Before attempting the test I found:

    After doing a ban test on a new user account it succeeds (on Programming.dev anyways) although the ban function is currently only available for community-based bans as asked/detailed by SockPls on Github.

    I’m currently unsure about the unlisted modlogs error, unfortunately this might be an instance related issue that you might want to test by creating a test user account

    Hope this helps a bit though!🤗

    • WrenFeathers@lemmy.worldOPEnglish
      2·
      1 month ago

      That’s weird. Had a user last night to ban, and tried three times after not seeing it show in logs.

      . Went ahead and assumed they were banned as the app gave conformation- but they kept on posting.

      • recursive_recursion they/them@lemmy.caEnglish
        2·
        1 month ago

        huh that IS odd🤔

        Without knowing how the underlying app’s systems work:

        My guess is that the app might be acknowledging the ban request as a confirmation that the request was sent (button pressed? yes: Display “Ban Confirmed”) but wasn’t verified/validated that the request was indeed successfully accepted on the instance’s side

          • recursive_recursion they/them@lemmy.caEnglish
            1·
            1 month ago

            hmm another way of looking at this is that:

            You’ve inserted coins into the vending machine (entered ban descriptions and other inputs) but after pressing the juice button, the vending machine doesn’t dispense your drink but it displays “Drink dispensing in progress” (the drink buttons and display works but there’s a gap/shortcircuit between the display and the dispensing arm (the dispensing arm being the instance for this situation)

            So the problem might be on:

            • the app’s side
            • the instance

            or it could even be a mix of both (¿Por qué no los dos?), hard to know till someone tests all possibilities