The defunkt Google Reader had a way of "starring" posts, which then showed up in their own feed, but this interaction was local to the reading interface rather than pushed out to the original content. However it introduced an "in-reply-to" element which was latter adopted as the simpler rel-in-reply-to for HTML. There was a proposed RFC (4685) " Atom Threading Extensions" that went unimplemented. This trend was one of the motivations behind the deliberate development of POSSE as a way for indieweb sites to stay in touch with their friends/users/readers that prefer to use silos as their primary aggregrator. Standalone feed-readers have for the most part been superseded by the much nicer overall UX of integrated read/post UIs as exemplified by Facebook and Twitter, where you can read, publish, comment, repost, like, RSVP and so on in one place - more and more users have switched to using these silos as their "aggregator" instead of aggregators that actually pull in content from around the web. In fact Mozilla Thunderbird has feed subscription capabilities built in.Įmail servers receive and collect your email for you regardless of whether you open your email program or not, whereas legacy desktop feed readers on the other hand typically DO NOT collect/accumulate posts from feeds you're subscribed to while you're not using them - this is not the case for hosted services, or native apps which sync with them. Google Reader) often resemble an email program.
WordPress plugin allowing an integrated feed reader on one's site Open Source Owncloud application with a web frontend and an API