> 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.
> I'd like to see new innovation around protocols and client 'browsers' that were made with monetization built-in as a first-tier specification.
I don't think the solution should be to cater to what big platforms want.
If we did that, then the logical conclusion of that is that we would have to download some bloated locked down app for each platform we wanted to visit, and we would have a plethora of walled gardens. Copying and pasting text would be very limited, and we certainly could not "view source". The best we could do to save content was take screen shots, we certainly could not click on an image and save it. Basically what they are doing now.
Platforms would like nothing better than to completely deprecate access by web browsers all together. (Didn't Instagram do that recently?) Perhaps in the near future, websites will require that you use an "Apple approved" web browser, if they let you access them outside of the app at all.
But, they fact that they present any of their content at all is because of the ubiquity of web browsers. They could probably make more money if they had complete control of their platform, and could do things like prevent ad-blocking.
So, we should have pushed more for RSS to be de-facto requirement of serving content. Firefox, and other browsers, should have advertised when RSS was available, and make it highly discoverable for users.
> 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 don't personally care that much about the protocol itself, I care about the content that the protocol makes available. If reading an RSS story required unpacking a bloated js runtime and fetching even more content, then why not just use a browser?
Publishers also hate SMTP and IMAP, and would love to force users to log into their platform and view ads, just to send an email to someone. And Google is certainly doing their part to eventually kill off these protocols.
AOL and many 90s ISPs did not support these protocols either (even though they used them internally) because they wanted to make users log into their platform instead of using their own mail client.
But the reason that SMTP still exists today is because of its ubiquity. The more RSS is adopted, the more popular it becomes, and the more platforms had to support it, even if they did not want to.
Being able to programmatically send emails is incredibly useful and helpful. I'm sure that when the last SMTP server shuts down, they will tell you that it is ok, because you can still use the mutually incompatible GMail or Outlook.com APIs. Pending approval.