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.
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.