3 ms·
Setting aside the technical point you're making, the pull-based architecture is the main disadvantage from the content-producer side. Suppose there is a hierarc
by sowbug 3y ago
Setting aside the technical point you're making, the pull-based architecture is the main disadvantage from the content-producer side. Suppose there is a hierarchy of customer acquisition:
1. You have the customer's billing information, ideally with a subscription revenue agreement.
2. Your app is installed on the customer's phone, ideally with notification permissions.
3. You have the customer's email address, and ideally you're not marked as a spammy sender.
4. Your SEO is good enough to get sufficient organic traffic.
5. Someone aggregates your content and puts it in front of enough customers for you to be profitable.
6. You publish an RSS feed, or any other fully opt-in technology where the customer normally pulls content from you, but might disappear at any point, and you have no way to re-establish contact with them.
7. Late-night infomercials, classified ads, etc.
I've probably missed a few categories, and maybe the ranking isn't perfect, but you get the idea. Why would a merchant or content producer bet on RSS when its main selling point is that the customer retains full control over the ongoing relationship?
Much as I personally love RSS, I don't see why today's internet would embrace it. Even the little guys dream of making it big, and that's why at a minimum everyone will spam you with a pop-up ad asking for your email address before they place a bet on a pull-based technology like RSS.