I think if I were presented a choice about including "my preferences"
and found out that actually meant "also my command history", I would be
very upset, even if it were opt-in. Even making it possible for the
command history to be included sounds sketchy to me, actually.
Ryan
On 09/27/2011 08:37 PM, Robby Findler wrote:
Would you think it unwise if it was another field behind the
"synthesized info" button? (Perhaps with some other name, but in
roughly the same manner.)
Robby
On Tue, Sep 27, 2011 at 9:35 PM, Neil Van Dyke<[email protected]> wrote:
Or you could make it opt-in, and have a disclosure by the button that
preferences file contains private info. People who are concerned won't
click the button, or they will go find the file and check before deciding.
This gets you out of writing any GUI for viewing the data. (Maybe you
provide a button to open the file in DrRacket.)
Or, if you're adding info from various sources, rather than having special
GUI for each like now, collect all the info, put it in one big text field,
and people can look at it just as they'd look at at the free-form text they
write describing the problem. I think there has actually been
implementation work in the past to hide this information, when exposing it
might have been quicker to implement.
Robby Findler wrote at 09/27/2011 10:06 PM:
Hm. That seems like more work than just asking people when it seems
relevant. Maybe the status quo is best, after all.
--
http://www.neilvandyke.org/
_________________________________________________
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/dev
_________________________________________________
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/dev
