Could you elaborate? I thought upgrading to HTTPS wouldn't involve redoing any sites, no changes to the HTML/CSS/JS/server side code, except for the TLS configuration and maybe replacing links from "http:" to "https:" but that's optional. I'd like to hear how it requires redoing a website?
did you read the part about how https doesn't protect us from the browser vendor, ie google?
They tell us to worry about man-in-the-middle attacks that might modify content, but fail to mention that they can do it in the browser, even if you use a "secure" protocol. They are the one entity you must trust above all. No way around it.
All other arguments you're presenting about HTTPS being easy (it is, have you tried Caddy) are moot. It's the sites that were made before Google took over control that aren't maintained that are at issue. And the idea that a for-profit company that no one should trust is saying they're the only ones you have to trust.
And the fact that many of us adopted the web because it was a platform that no company controlled. If it had been presented as Google's platform I would have run the other way and would have advised you to do the same. But now I'm invested. My freedom as a developer depends on the integrity of the web. And a web controlled by Google isn't the web.
Google has a nasty habit of taking control of open protocols and then trashing them.
Roll up your sleeves, make some quiet time and actually READ THE DOCUMENT.
Works on a few machines / connections I tried. Perhaps you should switch to a better browser or change your ISP if they don't let you visit websites that are on the web.
my perspective is that my name and copyright were removed from a document i wrote and re-published on the W3C site and that should be fixed. please don't speak for me. thanks.
i doubt if it will come to a DMCA takedown but that is a creative an interesting idea!
maybe someone else could post an issue to their repo. but as the author of the spec i really shouldn't have to do anything to get an esteemed organization like the W3C to respect a CC license and copyright.
of course any document can go missing, but the RSS 2.0 spec has been at that location for 20+ years and was put there specifically to preserve it over time.
and of course it's no excuse for ignoring a copyright notice and removing authorship credit.
and if harvard's website should disappear then grab a copy from archive.org. or use the github repo we created for the spec.
there are lots of backups of that spec. it would be hard to lose it. ;-)
http://scripting.com/rss.json
I started generating the JSON version in 2011.
http://scripting.com/stories/2011/03/17/jsonifiedRss.html
It took a few minutes to write the JSON rendering code, that’s how close the two serialization formats are, so if you want JSON, you can have it.