Live data from Hacker News

It’s Time to Get Back to RSS

danielmiessler.com

51–60 of 376 posts

Re: It’s Time to Get Back to RSS

#51
We should go more old-school and resurrect NNTP instead: Have clients that render Markdown, and servers where users can create their own access-controlled groups.

Have a group where only the owner may post: That's a feed.

Have a group where only the owner may post top-level articles, but anyone may respond: That's a blog.

Re: It’s Time to Get Back to RSS

#52

This is why I was so heartbroken when Mozilla removed first party RSS support from Firefox, for what seemed like an extremely flimsy justification.[1] RSS should be ubiquitous, and seen as an essential part of any service that serves structured incremental content. People should be emailing webmasters asking why there is no little orange icon. It also serves as a back door form of accessibility. But I strongly suspec…

Innoreader can make a virtual feed from changes that appear in any site -- a new feature I haven't tried yet. Used to use Google Reader, but now I pay for Inno, which I'm happy to do.

I used to be a big fan of RSS feeds but with their demise I started using Feedly.

It let's me curate sources into different customizable feeds like news or science. I pay for the pro happily since they let me add specific twitter accounts too. Really saves me time!

Re: It’s Time to Get Back to RSS

#53
RSS is dying (or dead) because it was incompatible with the dominant business model on the internet -- advertising. This is why Google killed it. This is why lots of professional publishers hated it. With HTTP you'd be able to earn money via embedded ads but you'd earn exactly $0 via RSS since the feed was stripped of ads, just content. This forced publishers to put useless blurbs, redirecting to the HTTP version, which was a bad user experience and just sucked.

I'd like to see new innovation around protocols and client 'browsers' that were made with monetization built-in as a first-tier specification.

1) client sends request for content with some header with payment information attached. 2) server verifies payment transferred. 3) server responds to client with content after payment verification.

If this existed, RSS would be alive and well. Internet publishers would be alive and well. The internet would be a more beautiful place with a viable first-party alternative to ads.

Challenges here would be:

- Sufficiently low transaction costs to make micropayments viable. (Bundle payments?) - Verifying proof of payment extremely fast

Someone(s) should create a new protocol.

FTP was invented in 1971. SMTP was invented in 1982. HTTP was invented in 1989. RSS was invented in 1999. Bitcoin was invented in 2008.

The amount of innovation around protocol has been abysmal relative to the explosion in creativity around applications on top of these protocols. And SMTP/HTTP are the only ones with any real mass adoption today.

Re: It’s Time to Get Back to RSS

#54
I’ve been using BAZQUX which is a nice aggregator and reeder4 Since 2013. I have a nice opml file. And my eyes don’t bleed because I could have text only webpages. For those of you who are adventurous you can try TINYTINYRSS. I don’t see why everyone said RSS is dead almost every site still supports it.

Re: It’s Time to Get Back to RSS

#55
post #32

The business model of RSS is harder than just slapping ads on your homepage and encouraging more page clicks. I think that's the real reason you don't see a strong RSS ecosystem. The content producers don't have a strong financial incentive to support it well.

In my experience RSS is at its best when dealing with infrequent publishers or niche audiences. People who don't expect to be paid for their writing because they want a wider audience, like think tanks or university departments.

That's definitely where it shines for me. I follow hundreds of infrequently-updated sites using Newsblur. It's sort of the same value proposition for me as Twitter. I'd never follow the New York Times in either place; what I want is to get beyond what's commercially viable to publish.

Re: It’s Time to Get Back to RSS

#56

If self-hosted is your thing I highly recommend tiny-rss and the iOS app accompanying it. https://tt-rss.org/

I came here via ttRSS, with the Android app. I host it via the hosting service I've used for years, it only requires PHP and a Cron job. The Android app lets me keep ttRSS and its authentication behind a separate HTTP basic auth, which I think keeps the attack surface low and security high-ish.

I think it's fantastic.

Re: It’s Time to Get Back to RSS

#59
post #47
post #39

The single worst offense against the usability of Atom/RSS right now comes from Apple and iOS. If you click a link to an Atom feed in Mobile Safari, iOS will launch the Apple News app. Which will then show you an error message saying the content is unavailable. As far as I can tell there is no way for an installed reader app to take over handling of feed URLs. It just makes the entire feed ecosystem look broken for a…

I wonder if the EU could, in theory, take action about this behavior. Apple is basically monopolizing the whole market for rss readers.

How many EU countries are Apple News available in?

Re: It’s Time to Get Back to RSS

#60
RSS seems to me to have use cases far beyond website updates, if it was extended a little.

Event syndication. Say that I'd collect the event feeds from a load of cinemas, music venues I like around the world, why not, plus those of musicians. I want my RSS-based events reader to narrow down the date field to be this weekend, location to be my town, and ticket field to be available, and why not price to something I can afford, while I'm at it? Bam, everything I could dream of doing this weekend, no Facebook and using a slightly modified version of a two-decade-old tech.

Similar functionality for shopping.

Why couldn't RSS be extended to something like this?

Post reply on HN