My thoughts on ACC and privacy
editFirstly, as an active editor at ACC, I think that all the data is required to make an informed decision.
However, recently there have been discussions about privacy issues - so here are some of my thoughts on the issue - I do not think that we need to change anything, so this is more of a thought-experiment.
On the main screen, IP addresses and email addresses are not needed, it could look like this:
| Open Requests |
| #12345 Requested-name-1 [Mark as being handled] |
| Flagged user needed |
| #67890 Requested-name-2 [Mark as being handled] |
Once the request is being handled, the handler (no one else) can see the email address (and see the notes below on how we might not need to see the IP details). Please note that I say that the handler needs to be able to see the email address, as this may indicate that the username is a violation (e.g. if the email is from fred@fred-windows.co.uk and the requested name is Fred Windows, it is likely to be a role account, if the email for the same request is fred.windows.junior@gmail.co.uk, it is less likely to be so!)
Here is what I think a handler needs to be able to see for each of the checks (please note that I am not a developer, so I don't know how feasible these are) - but they would all involve getting the data as the handler would now, and then removing IP details, etc:
| c (contribs) | Only show contributions made by the IP from 1 hour before the request was initially made (i.e. when the requester first sent their request, not when they replied to the confirmation email) - if it possible to show this is some way (e.g. diffs) without revealing the IP, then do that. If the contribs are older than an hour before the request, it is feasible that it is not the same user |
| gc (global contribs) | |
| b (blocks) | If there is an active block, show the expiry date and the blocking admin's comment - IP isn't needed. If there was a block which expired within the previous 48 hours, show this too (again, no IP) |
| r (range block) | |
| gb (global blocks) | |
| gr (global range block) | |
| w (WHOIS) | The IP does not need to be revealed - it would be enough to have the country (and location if available) and registrant (e.g. Wisconsin Internet Provider Inc; WI; USA) |
| af (Actions that tripped a filter) | Similar to 'c' and 'gc' |
| Creation | No problems - goes by requested user name, no IP issues |
| SUL | No problems - goes by requested user name, no IP issues |
| List | No problems - goes by requested user name, no IP issues |
| No problems - goes by requested user name, no IP issues |
If there are more than one request from the IP, a list of the dates created and names can still be given - this won't reveal the IP used.
The only privacy issue remaining is the email address, but I feel that this is required to be seen by the request handler, as mentioned above.
-- PhantomSteve/talk|contribs\ 11:20, 27 May 2010 (UTC)