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.

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.

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.

http://this.how/googleAndHttp

Breaking the web is the issue folks.

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.

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/2022/07/16.html#a172934

I use the feedparser package in my JS work written by my friend Dan MacTough, that hides the differences between all flavors of RSS, RDF and Atom.

https://www.npmjs.com/package/feedparser

I don't know what role you think I played in RSS, but I never had the power to change what people were doing. I could only do things in my own software and with publishing partners.

I had influence only because I had (at the time) popular products and some good ideas (like podcasting).

the mess was created by vendors who wouldn't work with each other.

i stepped back after 2.0, people could've done anything they wanted.

Now you're going to have to get systematic about finding out what you like to do, and make a good list, and when you're feeling depressed, just do one of those things. It'll lift you out the funk. It really works.

What you should not do as view the money as buying you anything other than freedom. Sure buy yourself a nice TV, car, computer, take trips, etc. But don't overdo it, live a human-size life.

One other thing, do not hire a money manager. Just invest in the S&P 500. It's the best investment possible and requires no thought.

Anyway, what Twitter did is repeat the body of the tweet in the title and description sub-elements of item.

The reason they did this is probably that the dominant reader of the day, Google Reader, pretty much required titles. So when you'd read a tweet in a feed reader you'd see the text of the tweet twice. Not a good user experience.

The problem isn't with RSS, because it allows for titleless items, rather with the reader.

And that problem is still with us today because there isn't much consistency among the readers other than the Google Reader model. They are all following GR, not RSS.

And that makes tweet-like-things-in-RSS pretty much a non-starter.

For examples, look at my blog on any given day most of what's there is too short to have a title, like a tweet.

http://scripting.com/

Hope this helps.

Thanks for the respect, much appreciated. ;-)

http://scripting.com/2016/05/31/1296.html