-
Notifications
You must be signed in to change notification settings - Fork 319
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
Rating Bar Near Invisible Negative Number #640
Comments
Duplicate of #499
Intended behavior at #288 |
You're right. A negative rating is barely noticeable. As for not showing
|
Depends on the severity... obfuscation is absolutely immediate. The TOS is what I try follow since it is a combination of stuff even before I came along. :) |
Maybe we should put some of those policies on our new script page
|
Terms of Service is linked on every page already and is necessary to find at any entry point on the site... so that would be extremely redundant and duplication is unnecessary for existing compliance with legal... speaking of I have a hearing to get to. bbl. |
Thank you for the moderation rights, but I doubt I fulfil the role well. I think it is best to remove the rank. ^_^ Just out of interest, by looking at the mod actions, a few questions have risen:
|
Done, at your request.
Currently the threshold is at one flag, but upvotes negate flags to protect popular scripts from haters.
This is why we have admin. It is the job of admin to catch things that may fall between the cracks. I still need to show absolute number of flags in the script listings for admins. #641
It doesn't matter who flagged it. There is "Mod tools" section that includes a remove button. We force you to actually go to the script page to remove it. That way maybe you won't blindly remove scripts.
We still don't have a solution for the case that something is improperly flagged. We might add a button that sets |
Currently I manually inspect the items that show up and either negate the flag or assume the role of the flagger(s). I know this isn't currently the best approach but until the listing of who did what is available in the UI. e.g. a master flag that should be available to at the very least admins and up to ensure that things are in order and override the user/author flags. Part of #262 to improve this procedure... and now in #642 and #643. There are also a few that are being "watched" from the admin side that I do on the user themselves in case they (are) doing an instance of spam or accidental stuff (a current example of a weird reply here... but I know Sebastian probably didn't mean to do this... so I haven't flagged that author.)... e.g. if they spam again and are flagged by me they are bye bye for violation of the TOS. In other words I usually give one chance depending on the severity. |
Thank you both for detailed the info.
This is a bit extreme for admin, isn't it? There are thousands of scripts and it is too much for mods. As the site gets more popular, the numbers will be too much.
Couldn't find that option when I had the privilege.
Accidental posting (something I am guilty of) occurs sometimes, and without edit makes it a bit of a nuisance. :) |
It's part of the job description. The filtering system and proposals from the new issues that @sizzlemctwizzle has created should be sufficient. This is all a team effort including users and author contributions. Eventually my proactive nature will be subdued by those issue completions and I won't need to be as persistent and be able to turn it over to the community for more evaluation. I will still look for obfuscated code though as that is considered severe in my book unless otherwise directed by the establishing owner, sizzle... in which case the TOS needs to be amended.
Patience please... until then use the preview before commenting. ;) |
We can have as many mods as we want. They are cheap. The moderation system Mods don't have to be completely trusted. We can scale the number of mods Admins on the other hand, have far greater privileges. They must be
|
For the first time I noticed a negative number beside the number of votes on the script's page progress bar (div.progress-bar-danger). A more visible colour would be preferable if it is not meant to be hidden.
Also, the negative number makes little sense to the end-user as it isn't infinitive how it is calculated using flags/down votes.
Unrelated suggestion: an easier way to tell if a script is flagged in authors page and even in listing. Maybe a little flag above the progress bar in the listing pages.
The text was updated successfully, but these errors were encountered: