I have no idea how this code actually operates, so pardon my ignorance.
If the computation takes place on the users machine, would it not be
possible to strip the location data and other concerning bits from it
serverside and have only the barebones needed to complete the
transaction? Or is this "leakage" a byproduct of the way Chromium
functions in this little "handshake"?
I don't see local data processing as a problem. Usually, users
controlling their data is preferred. If it has to bounce to a third
party before it touches DDG, or if the sensitive data has to be passed
through to said party, then it would be of concern. Again, I don't know
how this operation functions, so I'll leave the technical details up to
you hackers.
As for the naming thing (: long story very short:
Yegg mentioned your handle in this thread, so I promptly went up to the
tweeterz to see if any mention was made in this regard. Your twitter
handle is nil and the domain listed is opensesame.st, that coupled with
the fact that I have been heavily playing around with Plan 9 lately and
their having a rather small wiki, I recognized you immediately.
http://plan9.bell-labs.com/wiki/plan9/People/index.html
http://plan9.bell-labs.com/wiki/plan9/contrib_index#JAMES
OK, turning it off.
That's too bad. I do hope we can at least keep this feature in mind and work on it to iron out the issues
if possible and technical flaws permitting.