-
Notifications
You must be signed in to change notification settings - Fork 309
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
"You are now a Moderator" notification with a guide on our moderation policies #657
Comments
I'd like to sponsor @jscher2000 if he'll have it? Current responsibilities are just what he's doing. Current perks are double the flagging count value and access to what has been flagged/removed. Eventually there may be more activities. Thanks for the consideration. :) |
I guess I never noticed the Github notifications icon before. Sorry about that! I might not be active enough to be a useful moderator. |
@jscher2000 |
A new user posted four spam discussions. I don't see a way to flag/hide discussions and the Remove User link is disabled. So I'm not clear on what to do. Is there any documentation? Meanwhile I flagged the user. |
Perfect... we don't rate individual posts just yet that's part of #601 buried in there after that I think. One of the Admin+ (that's me, Founder, or sizzle) will remove currently and check at least once a day or so. The actual code to allow Moderators to remove is set to never enable the feature... it's a little buggy imho last time I tested it so I haven't corrected it yet. So in short... just report with a flag for now. Flags exist on users and scripts. More will come at a later date. Until the pardoning feature that sizzle wants comes in... if I see something different I usually clear the flag... although not always. Thanks. |
* Moderators and above may still flag if further abused and of course optionally, unannounced, removal by Admin+. These are covered in the TOS already. Try a preemptive strategy instead. Post OpenUserJS#1847 and applies to OpenUserJS#657
* `@connect` and `@antifeature` tracking/handling. Full language support (like TM)... the same as `@name`. It is highly recommended to have an unlocalized *(like `@name`)* which is what we will currently/soon be nabbing until the time for i18n comes along. NOTE(s): * User+ can utilize this to determine if flagging is needed and of course removal from Admin+. Some of these might be up for debate but it is a good start. Post OpenUserJS#944 OpenUserJS#657
* `@connect` and `@antifeature` tracking/handling. Full language support (like TM)... the same as `@name`. It is highly recommended to have an unlocalized *(like `@name`)* which is what we will currently/soon be nabbing until the time for i18n comes along. NOTE(s): * User+ can utilize this to determine if flagging is needed and of course removal from Admin+. Some of these might be up for debate but it is a good start. Post #944 #657 Auto-merge
* v2.x wasn't on npmjs for a while and it seems to be 1:1 compared to v1.x usage... minimal retesting... will test in the wild. Auto-merge
People have complained about the flag system not being effective. We can't expect one user: @Martii, who is an admin and shouldn't even be responsible for removing flagged scripts, to do everything. We should be able to make anyone a moderator (that's how the system was designed) and have a one-time notification (like the one we used for Google OAuth migration, except this one should be gone once you close it) that informs them that they are a moderator, and links to a guide on how to use the tools plus our policies for removal (which are already in the TOS).
Anyway, the goal is that I can just make users into moderators and have them know it, and what to do. If they don't want to be a moderator, fine then they can just don't ignore the dashboard (it's a tiny icon in the nav bar).
The text was updated successfully, but these errors were encountered: