User talk:Rillian: Difference between revisions
Martin.leese (talk | contribs) (→https: new section) |
(→https: respond to https link question) |
||
| Line 8: | Line 8: | ||
You converted a load of links on [[OggOpusImplementation]] from "http:" to "https:". Why? These all look like public web pages (so would not be restricted to HTTP Secure), and the few I tried worked fine using non-secure HTTP. (If you wish to respond, please do so here.) [[User:Martin.leese|Martin Leese]] 06:59, 24 January 2014 (PST) | You converted a load of links on [[OggOpusImplementation]] from "http:" to "https:". Why? These all look like public web pages (so would not be restricted to HTTP Secure), and the few I tried worked fine using non-secure HTTP. (If you wish to respond, please do so here.) [[User:Martin.leese|Martin Leese]] 06:59, 24 January 2014 (PST) | ||
This change was motivated by the decision at the [[https://www.ietf.org/proceedings/88/minutes/minutes-88-iab-techplenary IETF 88 Technical Plenary]] to treat surveillance as an attack and address it in that body's work. Using https links improves reader privacy and therefore is preferable when it is available. This had also become Xiph.Org policy since the draft was initially written. | |||
You are correct that the linked resources are generally also available over http. Did you have trouble accessing the draft references over https? | |||
Revision as of 08:45, 27 January 2014
Thanks
Thanks for correcting my spelling mistakes. (I cannot get Opera's spell checker working anymore. No idea why.)
https
You converted a load of links on OggOpusImplementation from "http:" to "https:". Why? These all look like public web pages (so would not be restricted to HTTP Secure), and the few I tried worked fine using non-secure HTTP. (If you wish to respond, please do so here.) Martin Leese 06:59, 24 January 2014 (PST)
This change was motivated by the decision at the [IETF 88 Technical Plenary] to treat surveillance as an attack and address it in that body's work. Using https links improves reader privacy and therefore is preferable when it is available. This had also become Xiph.Org policy since the draft was initially written.
You are correct that the linked resources are generally also available over http. Did you have trouble accessing the draft references over https?