RSS has been alive this whole time. Blogs usually have it by default, the big news organizations have it. 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,…
RSS is back as an underpinning to SlackOps
71–80 of 135 posts
Re: RSS is back as an underpinning to SlackOps
#72All I see is people claiming RSS is dead, but I never stopped. Moving between various readers and landed on Feedly for iOS a few years ago. Love it.
It's not dead, but many things I wish supported RSS don't. 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.
Re: RSS is back as an underpinning to SlackOps
#73Is there any way outside of just polling every 1~5 minutes to get realtime updates to RSS? Curious what is standard here? If you do do polling, what interval?
Re: RSS is back as an underpinning to SlackOps
#74Earlier quoted context omitted.
It's not dead, but many things I wish supported RSS don't. 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.
None of those will because they rely on engagement to make money. They need people logging into their servers so that they can see what they are looking at. That's not how RSS works, so of course they won't support it.
Re: RSS is back as an underpinning to SlackOps
#75Earlier quoted context omitted.
There is JSONFeed, but that was pretty much a flash in the pan.
If it was created instead of Atom it would have been nice, but it doesn't have any major advantages so no reason to add yet another format to the mix.
It does have a few minor advantages: multiple attachment support, more "branding" images support (author avatars, post "banners"), easier to build JSON than XML in most API backends these days. The one major advantage is that JSONFeed is easier to work with it in tandem with WebSub and other pubsub systems that assume messages are natively JSON, you can use the same JSONFeed item generating code for both pull (HTTP GET) and push (WebSub) scenarios.
Certainly even the main advantage isn't a huge reason to switch to JSONFeed if you've already got RSS/Atom feeds, but I believe the hope for JSONFeed was always that it would spark some sites/backends that don't want to support XML, don't have good XML libraries, or don't want to use their template languages to drive RSS/Atom feeds to be able to build something simpler instead resulting in more feeds overall than if things were just left to the XML-ish status quo. I don't know how successful it has been on that front, though, but I appreciate it exists for trying.
Re: RSS is back as an underpinning to SlackOps
#76Can anyone recommend a good terminal-based RSS reader? Preferably one that plays nice with small screens.
Re: RSS is back as an underpinning to SlackOps
#77Want to start a subthread here on what makes it great and despite many attempts to kill it, it still rocks! My take 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
Re: RSS is back as an underpinning to SlackOps
#78Earlier quoted context omitted.
One thing that's been corrosive to rss the past couple years have been podcast platforms. I find more podcasts (free ones) that can only be accessed through platforms like Google podcasts, Stitcher, Spotify, or Anchor, with no rss feed link to use in a platform agnostic podcatcher app.
Unfortunately, to Spotify's great delight, the word "podcast" has been successfully embraced, extended, and extinguished. Us technical types have been complicit in it by allowing the word "podcast" to mean audio shows on proprietary platforms that require proprietary players.
Those types have done a lot of the same damage to the word "wiki". It blows my mind that Sourcehut of all places is a willing participant in debasing the term.
Re: RSS is back as an underpinning to SlackOps
#79Earlier quoted context omitted.
One thing that's been corrosive to rss the past couple years have been podcast platforms. I find more podcasts (free ones) that can only be accessed through platforms like Google podcasts, Stitcher, Spotify, or Anchor, with no rss feed link to use in a platform agnostic podcatcher app.
Google Podcasts give you the RSS link of every podcast https://imgur.com/a/bmgzCFb
Re: RSS is back as an underpinning to SlackOps
#80I 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.