I wrote an impassioned cri de nerd here about why we risk losing the midterms. I'll spruce it up with hyperlinks and pictures a little later. http://idlewords.com/2018/10/portrait_of_a_campaign.htm …
-
-
You're mistakenly assuming that "malicious forces" aren't already intercepting and rewriting your blog. Perhaps you think "why would they target me?" not recognizing that most intermediaries simply inject *into everything*.
-
I don’t like the cargo cult thinking here. Intermediaries inject ads at worst; it’s all blockable on the client side. The KGB will not subtly edit my links. There’s simply nothing wrong about plain http in this context
-
- that's being unfortunately dismissive of some free and excellent advice of a simple and free way you can help improve the web, if you don't mind me saying so. (
@cscottnet ) -
FWIW
@wikimedia is actively working on ways to improve our distribution into "filtered" areas of the world, and HTTPS is still the best solution we've got. Anything wiki-specific would just get blocked if/when@wikipedia is. -
Just like with bundling small monetary contributions to make a big impact, getting everyone on board with "https by default" makes it more likely that folks who actually need end-to-end security will be able to use it without seeming shifty.
-
It's not perfect (eventually https MitM will probably become common) but it's the best we've got right now. And hey! I'm putting my money where my mouth is:https://twitter.com/cscottnet/status/1049872096367665153?s=19 …
End of conversation
New conversation -
-
-
There's also a privacy issue at play, here. Seeing as there is no cost involved but time spent clicking a few buttons in your management interface, won't you please reconsider?
-
Sorry, what is the privacy issue?
-
Folks who can connect to your blog via HTTPS have the option, by using alternate DNS names and TLS 1.3 with SNI, to hide that they're viewing your site at all. HTTPS helps fight facism in this way.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.