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

unverified user status #12

Closed
btbonval opened this issue Nov 13, 2013 · 3 comments
Closed

unverified user status #12

btbonval opened this issue Nov 13, 2013 · 3 comments
Labels
bug the issue is regarding one of our programs which faces problems when a certain task is executed

Comments

@btbonval
Copy link
Member

To curb spam, moderation is being proposed in issues like #11 .

Moderation should only be applied to users who aren't otherwise verified. Moderators and admin are implicitly verified.

Basic users are both verified and unverified. If basic were broken up into basic (unverified) and verified, the permission priority schedule might look more like: basic, verified, moderator, admin. Thus verified user is classified as such under DrupalUser.role or User.role.

Features which verified users have over basic users:

  • preventative spam measures are not applied
  • may vote to promote basic users to verified (this might enact the promotion or it might suggest it to mods/admin for review)
  • may vote wiki and notes as spam (this might not unpublish/delete the wiki or note, but might suggest it to mods/admin for review)

It might be awhile until jywarren#160 (proper RBAC) is completed, since there weren't any obvious or highly recommended RBAC implementations in Ruby.

@btbonval
Copy link
Member Author

Oh, based on jywarren#177 it might be wise to add another feature for verified users over basic users:

  • can add/remove tags OR can mark tags as spam for review

It might be too much of a hindrance to new users if basic/unverified users may not use tags, then again, it might be very worthwhile in the overall.

@btbonval
Copy link
Member Author

Incremental insertion plan:

  1. Keep basic and verified roles functionally the same. (find all places that say "basic" and add "verified")
  2. Create verify button: put on user profiles ("I verify user is legitimate") and research notes ("I verify the author is legitimate") where user/author is "basic". The button is shown to verified role and higher. Clicking it promotes the user from basic.
  3. (optional) Create a logging scheme of who verified a user. If a spam user is ever verified by accident or on purpose, and begins verifying other spam users, it would be fairly simple to create a cascade ban and/or cascade demotion.
  4. After 1-2 months of users verifying users, begin differentiating "verified" from "basic" in the code.

@jywarren jywarren added the bug the issue is regarding one of our programs which faces problems when a certain task is executed label Apr 1, 2015
@jywarren
Copy link
Member

I think we're all good on this for now, unless we expand the moderation system to cover more types of content. Let's close for now and re-open if it becomes an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug the issue is regarding one of our programs which faces problems when a certain task is executed
Projects
None yet
Development

No branches or pull requests

2 participants