-
-
Notifications
You must be signed in to change notification settings - Fork 387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Softer blocking for temporary, i.e. non-permanent block should left existing comments alone #377
Comments
@Reeywhaar - I think there is a bug on UI side rendering blocked users. I see the in order to reproduce it log in as admin (dev_user) block some other user temporary and refresh the page. |
not exactly. blocking someone (looks good) -> refresh (looks bad) -> refresh (looks bad) -> more refreshes (still bad).
.user.block === true only. The current master doesn't set |
this is a small video demoing what I've seen |
As you see on the video - refresh breaks blocking rendering but going back to settings restores it till the next refresh |
Found the problem, solution is on the way. But found another issue: last comments endpoint doesn't trim blocked users. I think it should? |
Do you mean temporary or permanent block? Temporary shouldn't trim anymore, only permanent should do it. |
Temporary, I think it's confusing that last comments have blocked user rendered fine. |
I see what you mean - we don't do faded thingy for last comment widget. Probably you right, I'll make the change to filter them out from the last comments widget. Regrading the picture - is it you or me doing "this user was blocked"? Somehow I have expected to see the original text here unless comment marked as deleted upd: and the original user name |
"This user was blocked" will be shown to non-admin users, as well as avatar will be ghost. Also I think to remove time on the right, and deny voting for comment |
just to clarify - the goal of this ticket is not to delete (and not to hide) comments for temporarily blocked user, but make blocking status visible (color and blocked badge) and not allow them to interact with the system till block expired |
Oh, ok, overdone it. |
This is the practical use case I have witnessed multiple times - a user acts like a normal human being until some "hot topic" mentioned. From this point, he started to post offensive, inappropriate, and silly comments. Before the proposed change, my actions were limited. I don't want to remove/hide his innocent comments, but want to stop the madness and (maybe) delete a few recent comments. However, the only action I was able to do was a block (hiding all comments) or manual removal (allowing him to continue). With this change, we will able to suspend such undesired activity without extream punishment. I hope it makes sense. |
Ok, understand, so I think there is no necessity to trim last comments too |
it works, thank you. One minor issue/inconsistency - blocking action refreshes whatever part of the screen it needs to update, and admin may see the effect immediately. Attempt to unblock right away refreshes appropriately as well, however, if between the block and unblock actions admin does any refresh, unblocking works "quietly", i.e. without updating/refreshing the screen. Pls, note - I meant unblock by clicking a link under the user name, not on settings view. Obviously, this is not a big deal, but it will be helpful to make it right. Let me know if you want a video demonstrating it. |
LGTM |
Currently, the temporary block doesn't remove user's comment but hides them for a given time and prevents the user from posting more. Practically, this logic seems to be too restrictive because the reason for such a temporary ban is usually a heated discussion or some other c concrete topic/conversation triggered the ban. However, it doesn't mean we have to hide/remove all previous comment from the user as they can be fine and legit.
The proposed change will not hide such comments, but won't allow the user to post more for the duration of the ban.
The text was updated successfully, but these errors were encountered: