Since Google Reader shut down, a number of independent projects have taken off. someone liked it, reposted it or simply created it themselves. Twitter and Facebook on the other hand also makes it very clear of why you have received a piece of content – if it's because eg. The inbox focus of many feed readers also means that they are often more concerned with what content they have received from whom rather than why they have received that particular content. The focus of such an interface is to read it all, whereas the focus of the continuous content streams of social medias is on getting a good snapshot of the moment.Īs continuous content streams isn't concerned with an unread count or with giving a good overview of of the content left in the inbox they can provide a simpler interface where content can often be displayed fully inline in one large, infinitely scrolling list.
Whereas many social medias focuses on a continuous content stream, feed readers are instead often designed around an inbox, with unread counts and sometimes even sub-folders. On the indieweb, replying is done by creating a reply post on your own site that links (with rel-in-reply-to) to the of the post you're replying to, and then sending a webmention to the post's webmention endpoint.Ĭontra: tt-rss-micropub provides a reply interface with the Tiny Tiny RSS feed reader. 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.
Microsoft Outlook has a feed reading feature to read feeds similar to email lists: other feed reader examples that community members have used (or are using) RSS client that works with web readers and local RSS feed files Open Source with a web frontend and an API for external clients Self-contained, open source, OS native feed reader.Īpp & web-based feed reader site (Substack & RSS) WordPress plugin allowing an integrated feed reader on one's site Open Source Owncloud application with a web frontend and an API social reader for interactive readers that let you can respond to posts, e.g.reader for current work on integrated indieweb readers.To further the goal of empowering individuals to post (and read) on the indieweb, it makes sense to develop indieweb-design-centric feed readers which address the limitations with legacy feed readers.
Feed readers are useful for keeping up with people's posts wherever they post, especially their own site.
0 kommentar(er)
