Readit NewsI 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.
HTTPS is not only about "asking user for data" It is also: - preventing third party from spying on you - preventing third party from altering the content presented to the user
Yes, yes, 20 years old websites do not have https Is running a 20 years old software a good idea, on the internet ? Of course not
What is the point of this post ? I read the "why google really wants you to use https" and failed to find any sense in this
Is this meaningless ?
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.
https://web.archive.org/web/20230704151648/http://this.how/g...
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.
Breaking the web is the issue folks.
And linking to the PR where it got removed: https://github.com/w3c/feedvalidator/pull/68
Or if you want to really get their attention, pull a DMCA takedown.
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.
Which in effect is understandable from the employees point of view – an RSS board seems vastly more official and stable than a link on a random subdomain of Harvard’s Berkman Center.
Only if you have been a reader of Winer’s multiple different weblogs 15+ years back, you’ll know the issue. Very quick and abridged recap of the Feed Format Wars:
• Winer’s Userland Software took Netscape’s RSS 0.9x, slightly changed it and promoted it as official RSS.
• The RSS 1.0 Working group wanted an RSS in RDF terms and build a rival RSS 1.0.
• Winer published RSS 2.0 in response.
• People still had problems with the RSS 2.0 spec and some lack of clarity and formed a different effort in response, which later morphed into Atom which found a home at the IETF as an RFC.
• People still had questions about parsing RSS 2.0. In 2003 Winer moved RSS 2.0 to Harvard’s Berkman Center – he was a fellow at that time – transferred copyright and “ownership” of the spec and set up an RSS Advisory Board, which could “clarify” open questions.
http://scripting.com/2003/07.html#rss20News
• In 2004 Winer resigned from the RSS Advisory Board, writing that the “process for clarifying the spec is now well-understood.”
http://scripting.com/2004/06/25.html#When:1:30:36PM
• The RSS Advisory Board made minor changes or clarifications in the following years, but mostly is inactive.
https://www.rssboard.org/rss-change-notes
• Rogers Cadenhead, then chair, slightly rebooted the Advisory Board in 2006 with new members and a new website.
https://workbench.cadenhead.org/news/2851/rss-advisory-board...
• That doesn’t go well with Dave Winer:
https://workbench.cadenhead.org/news/2860/rss-means-never-be...
… and he pretty much declared it nonexistent
http://scripting.com/stories/2007/05/24/advisoryBoardFinale....
---
From the RSS Boards perspective it was set up, the initial founder resigned and threw a tantrum, when later the board took its mission seriously.
And from a random reader’s perspective the rssboard.org website seems massively more useful, by publishing the clarified specs, the ecosystem of minor specs around them, a best practice profile and for the first time in RSS history a changelog. Before that we only had Mark Pilgrim’s rant:
https://web.archive.org/web/20060409104917/http://diveintoma...
As usual the feed format wars is a masterpiece in people not working together.
(And thankfully almost nobody cares except the people who back then spend too much time following the wars in the plethora of different blogs, almost all now have fallen victim to linkrot.)
[1] https://opml.org/blogroll.opml
[2] https://alexsci.com/rss-blogroll-network/discover/feed-c550c...
You can also see one in action on my blog's home page.
http://scripting.com/
And on a special site..
https://blogroll.social/
A blogroll is a kind of feed reader.