Voyager

5724 readers

1 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

[email protected]

Is anyone else having trouble with the ban feature in the Mod Zone? (lemmy.world)

submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

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.

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

[–] [email protected] 2 points 2 months ago (1 children)

I suppose that is possible. Though I’ll admit I’m not techy enough to fully understand that.

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

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

[–] [email protected] 2 points 2 months ago

See… now you’re speaking my lingo. I get it.

[–] [email protected] 2 points 2 months ago (1 children)

Seems to work fine for permanent bans. But not temporary ones.

[–] [email protected] 2 points 2 months ago* (last edited 2 months ago)

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👍