OpenStreetMap
How you participate is up to you, but be ambitious! Sites: promise to add HTTPS, HSTS, and PFS this year.
OpenStreetMap Enhances User Privacy
Today, OpenStreetMap has enabled encryption (SSL) to all of the openstreetmap.org website, thereby enhancing the privacy of its users.
You can now browse the site at osm.org (note the ‘https’). This means your browsing activity is secure from snooping.
https://blog.openstreetmap.org/2014/02/11/osm-enhances-user-privacy/
I just stumbled over a article about this and thought this might be something for OpenStreetMap, considering it also endorsed the “Day We Fight Back” campaign.
As this was on pretty short notice I though I’d just write this diary. I wasn’t really sure who to contact about adding the OSM website or if that should be done at all. I guess it is up to the OpenStreetMap Foundation?
Discussion
Comment from Baloo Uriza on 6 June 2014 at 02:06
I really wish that there was a good way to proxy cache HTTPS. Or, heck, cache HTTPS. Most browsers won’t do it, and (obviously, duh) it can’t be transparently cached with squid. HTTPS is definitely much more bandwidth intensive than HTTP, which is still a big problem: Much of the US is still on dialup, and pretty much everywhere that isn’t Scandinavia or South Korea isn’t exactly doing much better.
Comment from aseerel4c26 on 14 June 2014 at 00:03
@Paul Johnson: Hmm, it seems most browsers do cache HTTPS. See https://bugzilla.mozilla.org/show_bug.cgi?id=531801 or http://kb.mozillazine.org/Browser.cache.disk_cache_ssl .