Skip to content
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

Open
sizzlemctwizzle opened this issue Jul 2, 2015 · 5 comments
Labels
CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. DB Pertains inclusively to the Database operations. DOC Pertains inclusively to the Documentation operations. feature Something we don't already have implemented to the best of knowledge but would like to see.
Milestone

Comments

@sizzlemctwizzle
Copy link
Member

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).

@sizzlemctwizzle sizzlemctwizzle added DB Pertains inclusively to the Database operations. DOC Pertains inclusively to the Documentation operations. CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. feature Something we don't already have implemented to the best of knowledge but would like to see. labels Jul 2, 2015
@Martii Martii added this to the #485 milestone Jul 2, 2015
@Martii
Copy link
Member

Martii commented Oct 23, 2017

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. :)

@jscher2000
Copy link

I guess I never noticed the Github notifications icon before. Sorry about that!

I might not be active enough to be a useful moderator.

@Martii
Copy link
Member

Martii commented Feb 10, 2018

@jscher2000
Well give it a whirl at your leisure... you've been upmoted. :) Like I said there isn't much to do other than what you are doing at this time. You have been a great help over the years and that deserves some extra clout.

@jscher2000
Copy link

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.

@Martii
Copy link
Member

Martii commented Mar 9, 2018

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.

Martii added a commit to Martii/OpenUserJS.org that referenced this issue Nov 25, 2021
* 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
Martii added a commit that referenced this issue Nov 25, 2021
* 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 #1847 and applies to #657

Auto-merge
Martii added a commit to Martii/OpenUserJS.org that referenced this issue Dec 7, 2021
* `@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
Martii added a commit that referenced this issue Dec 7, 2021
* `@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
Martii referenced this issue in Martii/OpenUserJS.org Apr 12, 2022
* 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. DB Pertains inclusively to the Database operations. DOC Pertains inclusively to the Documentation operations. feature Something we don't already have implemented to the best of knowledge but would like to see.
Development

No branches or pull requests

3 participants