You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Yes, I am very rude. I am not a nice person, most especially to people - even the notably competent - who point their weaponry entirely at the wrong target. The problem is not HTTPS, it is busted old infra. Had you come up with a legit HTTPS issue, then sure. Amazon is not one.
HTTPS is going to burn huge portions of the open web, far more than Storify, and no amount of rudeness (or hype) is going to change that. I'm not the issue, although it will wipe out all my work. It's a huge loss for all of us if it actually happens.
…or, you could install certificates and/or press Amazon to plug the functionality gap. Alternately, launch a campaign to deprecate SSH in favour of Telnet.
I don't understand.
Are you using SSH? Yes? Why? Telnet/RSH did a perfectly good job. Oh, wait, SSH is more secure, more tamperproof, more efficient. As-is HTTPS. Both SSH and HTTPS are fit for use in the modern environment. That's why.
Anyone who accesses http://scripting.com , Dave — because they love what you do — is at risk of receiving content which has been tampered-with in flight, possibly had malware injected. Because http://scripting.com is not providing the protection of HTTPSpic.twitter.com/g6ttA7agfm
It's heading towards a world where plain-old HTTP is as irresponsible as casual sex without protection; simply, you're gambling with everyone's health. I, too, have HTTPS criticisms — notably the centralisation risks of cert issuance — but they're becoming less with time.
If it's such a great idea, no need to force anyone to do it, it should sell itself. Anyway, I don't have any more time for this, good luck with your efforts to save Storify content. Eventually I think you will come to understand what I'm saying when the lights go out on the web.
I already some blogs from the misery of "Typepad" and put them onto Wordpress. Software and protocols change, Dave.
This simply isn’t true, Dave. You are ignoring the last 5 years of history in which HTTPS has become easier to manage (even automated with the latest tools), and will be entirely free for the vast majority of websites.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
