Timelines and RSS Feeds
There have been a couple of interesting apps in the last few months whose concept I don't really like very much. Tapestry and the new version of Reeder are both apps with great pedigree, and I like the interfaces. But the fundamental design feels like it's solving things backwards.
These apps build a chronological timeline out of RSS feeds. This is something you may be used to from social media apps, especially if you used Twitterrific, or if you still use Ivory, for example.
But a timeline is for things that need to be read in order to make sense. Mastodon and Bluesky are good examples. When I read them, it needs to be chronological, because you see things happening then you see people responding to them. And it's why I hate algorithmic timelines on text-based social networks. Reading things out of context completely ruins it for me.
RSS feeds from websites don’t fit that model though. When I read RSS, I want to be able to browse different categories of feeds (e.g. I subscribe to personal blogs, tech news, F1 news etc.). I don't want to scroll through those longer articles in a feed mixed in with short social networking posts. (I certainly don't want to mix in video and podcasts.) I want to read the posts I've subscribed to based on what's interesting me right now. Some of them (e.g. F1) contain spoilers for things I haven't seen yet. Some of them are longer and I don't have time to read them just now. Sometimes I just feel more in the mood to read about iOS development than sport.
If I were to create a smarter RSS reader, I'd go the other way. Instead of copying the chronological timeline from social media apps, copy the algorithmic timeline. Show me the things that are causing the most buzz. Show me recommended stories based on what I'm subscribed to, because it's a good way of surfacing new sources.
If you liked this article, please consider buying me a coffee to support my writing.