-
Notifications
You must be signed in to change notification settings - Fork 7
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
Rules about user isolation decisions #15
Comments
I'm going to start working on it. First, I think that when we hide a user, it needs to be public. Not the user name of course, but the reason that we have forced the fact that it is invisible. Like this "The moderators have made invisible a profile due to spam". After discussion on IRC, it's appear that we actually can hide user for 3 reasons:
If you see other, please say it :) So :
I think that we should be more clear on the fact that the users of our service agree to:
This is all I see for the moment. |
Accounts created in large numbers are deleted, not hidden. The accounts we hide as spam are the ones that seem to be created only for self-advertisement with no intention of actually using Liberapay (i.e. to give or receive money).
Yes, any account that looks suspicious.
"controversial" mostly means that showing the account is likely to result in all kinds of unpleasantness because who or what it funds is widely disliked if not hated. Usually we also don't like them so it's not just about external pressure. |
One rule could be that a user should at least received one moderator vote to retrieve its donation. |
At Gratipay there was an admin dashboard for screening suspicious accounts that was run before payday. I assume Changaco is using a similar tool that may or may not be accessible to other admins. Might be something to clarify on the website (who has the power). |
This issue isn't about blocking payments, it's about the "visibility" of user profiles. Liberapay has 3 profile visibility knobs:
The user can modify these settings in the Privacy page, and I can override them through the admin pages. |
About electing the moderator team, I propose the following:
Involving these projects in Liberapay user moderation is important if we want to:
Then the blocking should happen if 50% of the moderators decide to do so. |
In Lille @whit537 asked me who decides to prevent a user from using the social features of Liberapay (per article 1 paragraph 2 of the terms of service), and I was like "uh, me?" because we don't have a process in place for that. I think we should modify the rules of procedure to delegate this task to a group of "moderators" selected by the codirectors, make it mandatory to notify the affected users, and probably give them the right to appeal the decision.
The text was updated successfully, but these errors were encountered: