[assetlabel]

Consumers of content don't get to choose the system or protocol of the person they follow.

I want to see a good client that supports many different ways of following content: RSS, Atom, Twitter, Mastodon, nostr, youtube, whatever... with smart ways of dealing with different kinds of content (tweets versus blog posts versus videos).

[jacobobryant]

Agreed, and this is actually my "top level" recommendation for anyone building apps in this space: if you make a reading app, make it read from anything; if you make a publishing app, make it readable anywhere; etc. Don't fixate on implementing a specific protocol. This is what I'm trying to do with Yakread.[1]

I see these RSS-related recommendations as the next step: what can an app developer do to reduce the effort it takes for others to interop with them?

[1] https://yakread.com/