Putting together an outline of what we do currently, its advantages and disadvantages, and brainstorming (yet again) possible alternative approaches for comparison.
|Open||None||T95144 Avoid exposure of user IP addresses (tracking)|
|Duplicate||None||T172477 RFC: Attribute anonymous contributions to the first IP address used in a session|
|Open||None||T20981 Allow anonymising of unregistered users ("IP editors")|
|Open||None||T12957 Allow logged in user to reclaim previous anon edits|
|Open||None||T133452 RFC: Create temporary accounts for anonymous editors|
- Mentioned In
- T227733: Draft: Masking IP addresses for increased privacy
E187: RFC Meeting: triage meeting (2016-05-25, #wikimedia-office)
T133452: RFC: Create temporary accounts for anonymous editors
T128055: Obfuscate old IP addresses in database
T92889: New Project: Privacy
- Mentioned Here
- T133452: RFC: Create temporary accounts for anonymous editors
T172477: RFC: Attribute anonymous contributions to the first IP address used in a session
T227733: Draft: Masking IP addresses for increased privacy
T228575: Decrease number of open tickets with assignee field set for more than two years (aka cookie licking) (March-June 2020 edition)
That's probably fine. I only filed a task because I felt pressured to by https://www.mediawiki.org/wiki/RFC, but really the wiki page is where the meat is here. This issue keeps coming up, so we need a clear outline of the current technical decisions so that we can better discuss and assess alternatives, in my opinion.
This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)