The only thing I'm not satisfied with reading news on RSS, is that news organizations push too many articles, to the point that reading the headlines alone takes quite some time. There's nearly 100 articles per day per source sometimes. Unlike a newspaper, which has a natural structure of priority and hierarchy, in an RSS reader, every head line has the same salience, and it's a pain to weed out what's important.
I kinda hope news organizations would make a separate "weekly digest feed", 30 or so articles per week.
Unfortunately training is per feed, there's a newer Premium Pro tier with global training coming out with it, but it is much more expensive [2].
1. https://www.newsblur.com/faq (under Intelligence section)
2. https://forum.newsblur.com/t/global-keyword-training/5419/6
I assume this is targeted at professionals that are trying to stay abreast of developments around certain topics/subjects. If you think about it through that lens it's reasonably priced, I suppose.
mike@klaus:~$ rss --list|grep ycomb
155. https://news.ycombinator.com/rss
mike@klaus:~$ rss --list-grep 155
74. title = (?i)\b((e-?|web)?mail|hardenize|irc|internet relay chat|grpc|hashicorp|rust|debian|c\+\+|perl|(bit|name)coin|tor|pgp|gpg|gnupg|openpgp|digitalocean|ovh|linode|grepular|email\s*privacy\s*tester|parsemail|ssl|https|backdoor|apache|exim|distribut|peer (to|2) peer|vpn|secur|anonym|webrtc|torrent|webtorrent|nextcloud|owncloud|graphql)(ity|ous|e?s|ing?|ed?)?\b
I'd be more than happy if you give it a go and share how it seems.
[1]: https://codemadness.org/sfeed-simple-feed-parser.html
(You can see my setup at https://acdw.casa/planet)
We need to get back to a world where we’d have daily or weekly issues of news that we all read so that we can’t point at the same thing and say, “that’s right” or “that’s wrong”.
So you can have a different feed for Science and Technology, and one for Australia, and one for New York. By not using the front page firehose, you can keep the number of inbound articles to a more manageable level.
Though like many sites, I have no idea how you would reach the "feeds" page from the front page (I gave up and searched Google for it)
(I actually still listen to them on an Apple iPod nano....)
I could believe it being true of some of other platforms, trying to have "our-platform-only" content but I haven't seen it and am not finding confirmation. I don't think it's true of Google Podcasts, that they have any of their own content.
I migrated my podcasts to GNOME Podcasts app by selecting the RSS link manually from Google Podcasts app when I switched to a Linux phone.
Facebook. Twitter. Instagram. These would be incredibly useful things to have native RSS feeds for, but instead I have to dig around and either use some tool someone built for the purpose - a tool at the mercy of the walled garden whose wall they're peeking over - or build my own nightmare factory.
It used to; killed off ~2013:
* https://brodiesnotes.blogspot.com/2013/06/twitter-has-killed...
If Facebook had any kind of API I could probably build this, and stop using facebook otherwise. Which is probably why they don't?
> […] The company spent a good portion of its presentation specifically focused on podcasts, which it said had been “largely unchanged” for years before its entry into the market, due to the limitations of RSS.
> Spotify cited how unbundling podcasts from RSS technology has paved the way for Spotify to generate revenue through these popular audio programs — a sentiment that’s not universally beloved by those who support an open podcast ecosystem. Spotify has disrupted that market by bringing some podcasts in-house, where they can only be heard on its service, and competitors have followed. This has fractured the ecosystem and left consumers at a disadvantage as some shows are no longer broadly available.
> “We’ve been able to replace RSS for on-platform distribution, which means that podcasts created on our platform are no longer held back by this outdated technology,” Maya Prohovnik, Spotify’s head of Talk, told investors.
When I recently asked friends for podcast suggestions... several were spotify-only, i don't think the suggestors even realized it, cause they just listened on spotify anyway regardless.
So I think Spotify agrees with you and is working on it...
It wasn't very fun constantly having to switch between my RSS app and my browser, so I just stopped using it.
Some publishers offer full RSS feeds as one of the benefits of their subscriptions. It might be something to explore for your favorite must-read sources.
I occasionally venture onto Reddit or HN to see if I've missed anything big but rarely do.
1. Widely adopted protocol, clients in all programming languages.
2. Publicly readable without password
3. Get notification for new items in many tools like Slack
4. Easy to produce and consume
5. Many nice Web UI Reader available
<Add yours>
There's still this lurking mess of RSS 0.91 vs 1.0 vs 2.0 vs Atom. As one of the folks involved in creating Atom I'm frustrated with the outcome.
These days it'd probably be JSON, right?
Maybe in theory, but as a heavy RSS user this has never been an issue in practice. For example, WordPress sites support both by default — RSS at /feed/, Atom at /feed/atom/, but apps like Feedly hide this implementation plumbing during normal use.
I’ll repurpose an older comment[1]. It was in response to “I doubt very much [JSON feeds] will catch on”.
> There’s little incentive for websites to change to JSON feeds when their RSS feeds are already implemented, working well, and generated automatically. But several good RSS readers added support for JSON feeds when the format was introduced and that’s all you need for it to be viable; it isn’t important if it “catches on” after that when the flexibility is there.
> JSON feeds were great for me because I generate my own feeds for personal consumption and can now do so with simpler code. I understand I’m in a minority—most people consume feeds and never create their own—but the larger point is JSON feeds may have already done their job: they exist and are supported if you need them.
Are there any technical reasons to use RSS instead of Atom in new deployments?
(I can perhaps see leaving legacy RSS links created pre-Atom in place.)
There's no technical reason. Unfortunately many CMSes still emit barely usable RSS v2. There's also the branding issue of RSS the format essentially being the name of the technology. Someone saying "I want an RSS feed" ends up with the implementer making an RSS v2 feed rather than a better Atom feed and just labeling it RSS.
You could also just get the unique email address of a channel and let the email notifications go there, same result: https://slack.com/help/articles/206819278-Send-emails-to-Sla...
… and using Slack to consolidate RSS turns RSS from pull to push. (Slack probably has caching mechanisms across all workspaces to reduce pull bandwith).
This was created to avoid unnecessary polling of RSS/Atom feeds:
* with `HTTP 304: not modified` result, I'll come back in 60 minutes * if there is any update, I'll come back in 4 hours * if there is no cache control header, such as etag or last-modified, I will poll every 12 hours.
I actually prefer the ability to push things like the top stories of the day to me through either Slack on email rather than having the temptation to constantly refresh an RSS feed app. An added bonus is that I frequently add some custom logic to curate the feed to my liking (based on the feed).
I'm slowly extending support for other social networks, to my surprise, they are not that "social" and it's quite a pain to scrape anything from them.
A lot of these online feed-readers have terrible UIs for managing large numbers of feeds, but I guess they allow the same benefit of keeping track of state (read vs. unread) that email also offers.
It... wasn't ideal though, in hindsight we should've hacked together a UI so that the people sending the message could confirm the message and see how many people would be receiving it first. There have been a few Incidents of accidental test messages sent out. One was my fault, early on, because production and test were the same machine. The other was the operators' fault, but by then the app had two million installations and it caused a bit of a social media storm that day (#hajo).
It was funny to see that one play out, and how quickly there are print companies making and advertising merchandise about whatever is trending on twitter that day.
Prior HN discussions: Turn GitHub into an RSS Reader (https://news.ycombinator.com/item?id=27010144)
It wasn't long before people discovered that and began using our service to deliver relevant stories to their Slack teams and stakeholders. As the author says, RSS is the closest thing to an open MVP-style API that "just works," and hasn't been plagued by a company's closed garden rules.
I am wondering, what else could one use RSS for.
Long live RSS!
Google makes ad revenue, cuts out most of the sites themselves and increases google value, while reducing the value of the actual site producing the content.
I would advise against co-mingling an RSS feed with your team's main communication or coordination channels.
Isn't Feedburner part of Google nowadays? I remember reading somewhere that they inject ads in the feeds.
I feel like Slack has already become a black hole equal to my Inbox in all respects and am hopeful that the Interoffice Mail envelope will stage a comeback for the things I really need to see.
[1]: https://github.com/maubot/maubot#readme
[2]: https://github.com/maubot/maubot/issues/110
[3]: https://github.com/maubot/maubot/pull/147#issuecomment-99722...