I ususally use the web interface to manage moderation but I'll give this a go and make a new comment on this post with my findings🤗
this post was submitted on 15 Oct 2024
12 points (87.5% liked)
Voyager
5604 readers
10 users here now
The official lemmy community for Voyager, an open source, mobile-first client for lemmy.
Rules
- Be nice.
- lemmy.world instance policy
Sponsor development! 👇
💙
founded 1 year ago
MODERATORS
Before attempting the test I found:
- Voyager [Issues]: Ban user from instance #1491 and
- Voyager [Issues]: Mod tools temporary ban with remove content doesn't work #1494
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!🤗
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.
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
I suppose that is possible. Though I’ll admit I’m not techy enough to fully understand that.
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
See… now you’re speaking my lingo. I get it.
Seems to work fine for permanent bans. But not temporary ones.
ah in that case I'd recommend linking to this post as a comment onto the second Github Issue link I shared above as it seems to be a replication of sallyFoster's reported bug👍