51–60 of 314 posts
This topic comes up semi-frequently. I'm personally a fan of RSS but it certainly has issues: (For the purposes of this comment I'm mostly referring to Atom/ 1. RSS is, at the end of the day, a syndication format, _not_ a feedback or posting format. 2. RSS feeds have no real concept of portability between devices or user agents. Kludges like OPML can be used to aggregate feeds for sharing across user agents, but they…
I miss having a standard for uniform syndication that could be read and updated IN-BROWSER. RIP Firefox RSS feeds.
This turned up in my RSS feed of hacker news. Yes, google basically killed RSS through embrace, extend, extinguish. There’s no money in democratizing self-publishing.
how do you have a RSS feed of HN? what links does it include out of the thousands that are posted here daily? also, can I ask you what service are you currently using for you RSS feed? thanks.
Unfortunately, it only includes the title and the submission’s link, no content, which makes it a bit useless if your intension is to read the articles and not just the titles, which you can already do by visiting the home page.
Some people have created complementary RSS feeds like this → https://github.com/cixtor/rssfeed#readme which basically take the submission’s URL, download the web page, and removes the irrelevant HTML tags using Mozilla’s Readability.js library. Although, this project uses a Go (golang) port: https://github.com/go-shiori/go-readability#readme . It seems to work quite well, with minor bugs here and there due to inconsistencies of modern web development.
The author paints it as some kind of conspiracy, but the simple truth is that RSS waned in popularity once push notifications became popular and widespread. Every user's RSS reader polling every website for changes every few minutes for all eternity is horribly inefficient and unfeasible to do on most platforms and devices today (especially on mobile). Pub/sub is the clear way forward, but it's just sad that there is…
Polling isn't a requirement. If your reader is polling it's strictly because the author wanted to implement such a feature; that's it.
There's also ETag and last-modified which are used when checking and have very little overhead (most especially in the case when the content has not changed).
it's embarrassing to admit (i mean, I have a CS degree from a Famous School(TM) and I'm an old school unix and C programmer), and it's been a long time since I've tried, but I could never figure out how to get RSS working. the instructions always had terms-of-art without explanation, like syndication or something. Like, I know what syndication is in terms of newspaper publishing, but that doesn't tell me if that's so…
Unless you mean how to enable publishing an RSS feed for your own website? In that case I have no idea, and I wouldn't expect an old school unix/C person to know how to configure web things (speaking as one as well).
The author paints it as some kind of conspiracy, but the simple truth is that RSS waned in popularity once push notifications became popular and widespread. Every user's RSS reader polling every website for changes every few minutes for all eternity is horribly inefficient and unfeasible to do on most platforms and devices today (especially on mobile). Pub/sub is the clear way forward, but it's just sad that there is…
1) It's not that inefficient, especially if you recalculate your feed only when it changes and use HTTP statuses (particularly 304 Not Modified) correctly.
2) Most people then and now would go through an aggregator. So they'd really be talking to that instead of the source feed.
3) There were push notification standards out well over a decade ago, including RSSCloud and PubSubHubBub.
To be honest, I don't. Websites like Reddit or Hacker News are better because they provide popularity scores into the links, helping me filtered out junk links.