Drake Wilson wrote: > Quoth Mike Perry <[email protected]>, on 2010-09-30 15:57:48 -0700: > > This release features "tor://" and "tors://" urls that will > > automatically enable Tor before loading the corresponding http or > > https url. > > Ick. This sort of layer-mixing is the sort that forces people to use > a certain protocol for no actual reason. (Cf. the "feed" schema, > which similarly forces HTTP with a certain interpretation, last I > recall.) Tor doesn't just work with HTTP, and URIs don't only refer > to HTTP resources, even if HTTP is one of the most popular protocols > in use today and possibly the only one many non-technical people would > recognize. > > Is there a reason not to use something like tor+http and tor+https for > the schema, thus opening up the space for (as a facetious example) > tor+nntp or analogous usages later?
I really like the idea of "tor+http" or "tor+https" over tor/tors just like the way I hate the way Google Chrome has dropped "http://"; from their URL bar. Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/ *********************************************************************** To unsubscribe, send an e-mail to [email protected] with unsubscribe or-talk in the body. http://archives.seul.org/or/talk/
