21–30 of 32 posts
How many of my TL;DR points here https://www.earth.org.uk/RSS-efficiency.html do you already deal with, out of interest?
2 and 3 so far, but I am planning to support the others as well, thanks.
Looks nice. But I'ts strange that there are so many "simple" feedreaders. Where are the tools for powerusers? How many feeds and formats are people using usually to be satisfied with simple?
What poweruser tools are you missing in newsboat?
I've started working on my own "power user" RSS reader that lets you weight the keywords you're interested in (so an article that hits important keywords but is older could be displayed above an article that's newer) but it's still closer to a proof-of-concept than a complete app.
Earlier quoted context omitted.
In addition to performance it also has to do with politeness: it’s not polite to ask for the same resources again and again from a server when you could cache it, especially when it has explicit headers about it in its response. Think of small self-hosted blogs with hundreds of readers that constantly poll it.
Even with a small self-hosted blog, assuming you have more than a 56k hookup to the internet, a raspberry pi can service up 100s of requests per second. At the time of writing this, the HN rss feed is 12kb. That'd mean you'd need 10Mbps upload to handle 100s of requests to the rss feed per second. (Again, not saying you shouldn't optimize this, just questioning how big a problem it is).
Earlier quoted context omitted.
In addition to performance it also has to do with politeness: it’s not polite to ask for the same resources again and again from a server when you could cache it, especially when it has explicit headers about it in its response. Think of small self-hosted blogs with hundreds of readers that constantly poll it.
Even with a small self-hosted blog, assuming you have more than a 56k hookup to the internet, a raspberry pi can service up 100s of requests per second. At the time of writing this, the HN rss feed is 12kb. That'd mean you'd need 10Mbps upload to handle 100s of requests to the rss feed per second. (Again, not saying you shouldn't optimize this, just questioning how big a problem it is).
One podcaster halved its bandwidth bill overnight getting just one of these fixed, see "A saving bandwidth special!":
How does this compare to newsboat?
What are you using to store feed urls? It would be kind of cool and interoperable if you used newline separated textfiles
Earlier quoted context omitted.
What poweruser tools are you missing in newsboat?
Not the OP but my biggest missing features would be: - the ability to send the output of one smart query into the input of another - not needing to escape every quotation mark in a query, and maybe the ability to combine operands eg ( title =~ {linux,macos} as opposed to title =~ \"linux\" or title =~ \"macOS\") - a dashboard mode that can show a snippet of the top headlines and maybe autoscroll - ability to mark an…
Earlier quoted context omitted.
The link claims we could save "100kWh per day" and there is a dataset provided (I didn't dig in that yet)
I am trying to better assess this number as part of an arXiv paper I am putting together. Maybe even this weekend! RSS/podcast feed polling is a load for which Apple/Amazon/Spotify/Podbean are currently wasting 99%+ of the network and CPU bandwidth for, and thus money and carbon emissions. Many of the creators have limited budgets, and reaching Net Zero is not going to happen by ignoring really easy cases such as thi…
I have a home-brew solution for pulling feeds and will be cross reference with your info. One small impact!