Page MenuHomePhabricator

Avoid exposure of user IP addresses (tracking)
Open, Needs TriagePublic


Putting together an outline of what we do currently, its advantages and disadvantages, and brainstorming (yet again) possible alternative approaches for comparison.

Event Timeline

MZMcBride raised the priority of this task from to Needs Triage.
MZMcBride updated the task description. (Show Details)
MZMcBride added a project: TechCom-RFC.
MZMcBride subscribed.
daniel subscribed.

Tagging this as "draft" for now, assigning to MZMcBride for lack of better knowledge.

That's probably fine. I only filed a task because I felt pressured to by, 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.

TechCom views this as needing to be a product and movement decision first. Needs resourcing and some kind of rough consensus then we can weigh in.

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