Live data from Hacker News

Now Is the Perfect Time for an RSS Renaissance

neflabs.com

1–10 of 358 posts

Re: Now Is the Perfect Time for an RSS Renaissance

#3

Can part of the renaissance be switching to a JSON format? Please?

https://jsonfeed.org/ has had some preliminary traction. Of course, the reason RSS works so well is that everyone uses the same format. So you wouldn't see so much of a "switch" as a bunch of readers accepting either format, for a very, very long time.

That being said, I don't see what's "wrong" with XML in this context.

Re: Now Is the Perfect Time for an RSS Renaissance

#4

Can part of the renaissance be switching to a JSON format? Please?

Yes, and while we are at it. Can we make HTML JSON based, as well?

    { 
       "head" : [...],
       "body" : [ { "name" : "H1", "text" : "Hello JSON" },
                   ... ]
    }
So much easier on the eye. ; )

Re: Now Is the Perfect Time for an RSS Renaissance

#6

Can part of the renaissance be switching to a JSON format? Please?

https://jsonfeed.org/ has had some preliminary traction. Of course, the reason RSS works so well is that everyone uses the same format. So you wouldn't see so much of a "switch" as a bunch of readers accepting either format, for a very, very long time. That being said, I don't see what's "wrong" with XML in this context.

Most of the complaints I've seen with the 'wrongness' of xml are centered around its human unreadability, which doesn't matter in this context. I'm curious if there's another reason.

Re: Now Is the Perfect Time for an RSS Renaissance

#7

Can part of the renaissance be switching to a JSON format? Please?

https://jsonfeed.org/ has had some preliminary traction. Of course, the reason RSS works so well is that everyone uses the same format. So you wouldn't see so much of a "switch" as a bunch of readers accepting either format, for a very, very long time. That being said, I don't see what's "wrong" with XML in this context.

There's nothing "wrong" with XML but with JSON there's no need to add another 5 pounds (2.2 KG) of JavaScript to convert XML to JavaScript objects. For any other language it doesn't matter since you're re-mapping to objects, most likely, but with JavaScript eating the web (even on the server side) I think the question should be "why shouldn't this be JSON" as a default. In the end either way works. I would love to see Google Reader resurrected... stopped reading blogs and switched to Twitter and Hacker News once Reader died.

Re: Now Is the Perfect Time for an RSS Renaissance

#8
RSS never went away for me. Try FreshRSS[1], it's awesome. It works well on shared hosting and it runs on SQLite.

TTRSS only gave me trouble. Threw all kinds of strange errors at unexpected times. I don't know how many times it died on me after an upgrade. I eventually gave up and found FreshRSS. Been running (and updating) it over a year, without a single problem.

One of the best things about it is escaping the algorithmically curated feeds.

Every and service that I use has an RSS feed, except for Twitter. I use https://twitrss.me/ to follow users. If you don't find a feed, sometimes you just have to dig a little. You learn at which URIs the most commons CMSes presents their Atom/RSS feeds (hello /feed/).

Re: Now Is the Perfect Time for an RSS Renaissance

#10

RSS never went away for me. Try FreshRSS[1], it's awesome. It works well on shared hosting and it runs on SQLite. TTRSS only gave me trouble. Threw all kinds of strange errors at unexpected times. I don't know how many times it died on me after an upgrade. I eventually gave up and found FreshRSS. Been running (and updating) it over a year, without a single problem. One of the best things about it is escaping the algo…

I'm reasonably happy with TTRSS running on Sandstorm.io, but it's web client sucks. To me, the reason TTRSS wins is because there are about a dozen different clients that work with it, and most of them are vastly better than the server's UI.
Post reply on HN