 | This user account is a bot that uses AutoWikiBrowser, operated by bender235 (talk). It is used to make repetitive automatedorsemi-automated edits that would be extremely tedious to do manually, in accordance with the bot policy. The bot is approved and currently active – the relevant request for approval can be seen here. To stop this bot until restarted by the bot's owner, edit its talk page. If that page is a redirect, edit that original redirecting page, not the target of the redirect. Administrators: if this bot continues causing harm after receiving a message, please block it or remove from the approved accounts. |  |
Emergency bot shutoff button
Administrators: Use this button if the bot is malfunctioning. (direct link)
Non-administrators can report a malfunctioning bot to Wikipedia:Administrators' noticeboard/Incidents.
The purpose of this bot is to convert existing external links on Wikipedia, wherever possible, from HTTPtoHTTP Secure (HTTPS), i.e. from an unencrypted to an encrypted transport protocol. There are three reasons for using HTTPS: (i) data is sealed from eavesdropping on the internet cable (privacy) which also prevents censorship, (ii) data cannot be manipulated (integrity), and (iii) data came from the correct source (authentication). Rather than further elaborating (but have a look here), here are some news reports emphasizing the importance of each point.
As we discussed earlier, your ISP can't see what you do on an HTTPS-enabled website. For example, the ISP knows when you visit https://arstechnica.com, but it doesn't see which articles you're reading.
In fact, our study finds there was less censorship in June 2016 than before Wikipedia's transition to HTTPS-only content delivery in June 2015. [...] This finding suggests that the shift to HTTPS has been a good one in terms of ensuring accessibility to knowledge.
The tl;dr is for Android users to ensure they are encrypting their communications by using VPNs, [or] ensuring the sites they go to are encrypted [...]
The findings of this report also illustrate the urgent need for ubiquitous adoption of HTTPS by website developers.
Done Archive.org (WP:BFRA) Done Google News, Google Books (WP:BFRA) Done YouTube (WP:BFRA) Done Electronic Frontier Foundation, Human Rights Watch, Amnesty International, American Civil Liberties Union (WP:BFRA) Done The Guardian (WP:BFRA) Done Yahoo.com (WP:BFRA) Done New York Times (WP:BFRA) Done The New Republic, The Atlantic, Wired, Bloomberg, Wall Street Journal, Die Welt, Handelsblatt, Foreign Policy, ForaDeJogo (WP:BFRA) Done Vox, Nobel Prize, Office of the Historian, Ars Technica, British Museum, Boston Globe, TechCrunch, Oyez, Cornell Law, Supreme Court, United Nations Done ProQuest, ProPublica, NASA, Science Daily, FindLaw, Mother Jones, IEEE Spectrum, The Diplomat Done Knesset, Whitehouse.gov Done Internet Assigned Numbers Authority Done LacusCurtius, Digital South Asia Library, Perseus Project, Hebrewbooks.org
Doing... Find a Grave, National Science Foundation, ESPN
Not done German Football Association, University of Manitoba
