Well put. However, while I agreed eventually with the ssl prompt warning, and I am a strenuous defender of it now, I am not so sure about cookies. Making lynx hang, and making a user interact on a decision they know nothing about the first time they encounter lynx renders the decision meaningless and just makes their initial experience unpleasant.
This is just a userdefs.h default for "out of the box" builds, and doesn't affect user ability to knowledgeably self-manage. Nevertheless, since warn is a default and if that does not change, can [A]lways in LYCookie trigger an [O]ptions rewrite of .lynxrc from LYOptions? On Thu, 13 Jan 2005, David Woolley wrote: > > browsers I am not sure it is entirely necessary. Most users will tolerate > > the > > back and forth of a cookie (if they even know about it) if they see better > > Commmercial browsers suppress cookie warnings by default to benefit > commercial web page operators, not to benefit the users. Although > more privacy then security, it is typical of the unsafe defaulting > of security on Windows. > > Cookie warnings are suppressed, because enabling them might make more > users aware that they are being tracked by cookies. > > Anything that is security or privacy related should always default to > warn. > > > _______________________________________________ > Lynx-dev mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/lynx-dev > _______________________________________________ Lynx-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lynx-dev
