61–65 of 65 posts
Earlier quoted context omitted.
That is very ambiguous phrasing.
Firefox removing RSS support was the nail in the coffin for their support of the Open Web. How long after Google Reader was canceled did FF remove RSS?
Firefox removed RSS support in version 64 on December 11, 2018, approximately 5 years and 5 months later.
I generally try: /rss, /feed, /index.xml, /rss.xml, /feed.xml, etc. And at various root or /directory/* locations. https://blog.jim-nielsen.com/2021/feed-urls/ is a good article with statistics on naming. I've been adding to my feeds.opml since reddit started dying in ~2015 and now I'm up to around ~1700 feeds and mostly independent from aggregators; though I still collect new feeds from HN/IRC/etc. Mostly I just alw…
You should also check if the web page actually exposes this information in a tag. If you're running Chrome, the "RSS Subscription Extension (by Google)" extension [1] will do this for you automatically and light up an orange icon in the extensions bar. It also integrates with popular RSS aggregators so you can subscribe directly from the extension. [1] https://chromewebstore.google.com/detail/rss-subscription-ex...
Earlier quoted context omitted.
Firefox removing RSS support was the nail in the coffin for their support of the Open Web. How long after Google Reader was canceled did FF remove RSS?
Google shut down Google Reader on July 1, 2013. Firefox removed RSS support in version 64 on December 11, 2018, approximately 5 years and 5 months later.
Earlier quoted context omitted.
“Who's updating their RSS feeds once an hour 24 hours a day?” RSS is a pull-type system, no?. So the end-user is causing the overload problem by hitting the publisher’s RSS feed every hour? The problem is out of the hands of the publisher…
> RSS is a pull-type system, no? Yes. The web in general is also a pull-type system. > So the end-user is causing the overload problem by hitting the publisher’s RSS feed every hour? There is no overload problem. And again, this math is off, because an end user is not even awake 24 hours a day: "If 2 million people subscribe to your feed and try to update it once an hour, that is 48 million requests a day just for RS…
Sorry, I wasn't thinking about the end user literally pushing a button. I was reading into the discussion here what I imagined to be a gap in the overall design philosophy of RSS where the end-user, using their own app or preferred methods, poll all of their favorite websites selecting among common defaults (Select the frequency you like to poll this RSS feed: weekly? daily? hourly? hehe minutely? secondly?).
In this scenario the user doesn't need to be awake 24 hours a day. They just need to use software which stupidly hits someone's server like they're doing a denial of service attack. As your comment alludes no one needs to be that up-to-date.
In contrast, there was another solution: "...service that polls RSS on behalf of its users."
Again, reading the discussion I imagined the wild west of the internet has inexpert users choosing unsane defaults and overloading small self-hosting content providers. Compared to third-party aggregators who are trying to make money by solving a "Tragedy of the Commons" problem.
Earlier quoted context omitted.
> RSS is a pull-type system, no? Yes. The web in general is also a pull-type system. > So the end-user is causing the overload problem by hitting the publisher’s RSS feed every hour? There is no overload problem. And again, this math is off, because an end user is not even awake 24 hours a day: "If 2 million people subscribe to your feed and try to update it once an hour, that is 48 million requests a day just for RS…
> "...an end user is not even awake 24 hours a day..." Sorry, I wasn't thinking about the end user literally pushing a button. I was reading into the discussion here what I imagined to be a gap in the overall design philosophy of RSS where the end-user, using their own app or preferred methods, poll all of their favorite websites selecting among common defaults (Select the frequency you like to poll this RSS feed: we…
But the user's computer would need to be awake 24 hours a day, which is usually not the case.
And once per hour is not a DoS attack.