Google Reader reader? Would you find this service useful?
box.plc.vc
box.plc.vc
I assume this feature made its way into the genre as a legacy from the traditional email clients that seem to have inspired most feed readers, but while an unread count has a place in email (albeit a complicated one, cf. Inbox Zero) it seems utterly bizarre in the world of RSS. And for two reasons.
First, it's just stressful. It represents yet another item on this long list of things I haven't accomplished (and probably can't accomplish), a list that only grows longer as I come across more sources of information on the internet, subscribe to more feeds, follow more Twitter accounts, etc.
And second, as an offline analog, I've never walked into a library or a bookstore or a newsstand and been given a list of books or periodicals I've not yet read. Similarly, when my newspapers pile up in the recycling bin they don't proffer me with a running tally of all the articles I skipped. While I understand this is a feature that an RSS reader can offer that these examples cannot, it still seems to me to be a stifling and oppressive thing whose benefit doesn't nearly outweigh the stress it adds to my life.
At the end of the day it's ok to miss something. As Dave Winer said, "if it's important it will come back around again; if not, well no one can know everything."
(related/full disclosure: I'm actually hard at work on my own RSS reader intended to address this and other issues, which explains why I've been thinking so much about this stuff.)
You've inspired me to rethink my perspective of my RSS reader. Thanks.
You could try to improve this with ML or stasticial models, but I don't even think you'd have to get that sophisticated to make a big improvement.
I don't think something like that would be hard to implement. Ranking metrics could be simple at first: whether a site is "preferred", whether content is agreed with or disagreed with (the software should display both prominently, otherwise it ends up as a circlejerk), and whether the content is interesting or disinteresting.
However, the big problem I saw with such a setup was that it de-socializes the web; while I get a custom news feed, I don't get the quality comments I generally find on aggregators like HN or Reddit (so long as it's a decent subreddit anyway). So, the next iteration could use a distributed database backend (like CouchDB) to allow comments to be shared cross-node; people share a small web presence on their site, and you can choose to follow their comments on articles, like some sort of distributed Twitter.
The self-defeating part of the exercise that got me was that at that point, you've basically made discovery difficult. Which you'd address with a central hub. At which point, why not just use HN/Reddit anyway?
Google Reader's "Sort by magic" attempts to do this. It'd be nice to have more information on how it works though.
Also, don't underestimate the power of tagging your RSS feeds. Just like people set up GMail/Outlook/etc labels for important people or emails, you can set up tags for important feeds that you don't want to miss. Why not tag all of the "must read" feeds, the "skim" feeds, and the "eh" feeds, so that you can click on the "eh" label, and mark all as read if you get behind?
Google Reader is already a pretty powerful tool for feed reading (especially in conjunction with Yahoo Pipes or similar), and a lot of issues with RSS can already be solved with the tools at hand.
You can also turn off display of unread counts with the menu under the little downward triangle in the left column. These features are pretty undiscoverable, but they're there.
Since this Google Reader reader would track you as you move between sites (and has a heuristic for determining which story you're hovering over or scrolling past), you would not have the read counts in front of you.
My typical feed reading experience is bounce between the few sites that have updated content. I use RSS because it means I don't have to hit the site as frequently, and only when it has new content. If this had a way of both showing the unread counts of all feeds as well as allowing you to read the original site, I think it would be the solution to the problem that RSS readers originally solved.
This is just an idea for the service. I developed something very similar, but you can't go to the original site and still get stories marked as read as you read them. But I moved to RSS to get to those counts of all of my feeds in the first place. The loss of context (the site's styling and design) was a big negative to RSS, but the loss of inline counts would be harder to swallow.
Keep the left side of Google Reader, but replace the much larger right side.
And if anybody is interested, the similar idea that I'm working on is at: http://www.newsblur.com.
My implementation of the solution to the feed reading problem is very, very similar, but those unread counts, man, are the reason I even use RSS. And having to jump between tabs (Google Reader -> Original Site), would separate me from those counts.
It's not a business, just a side project where I learn as much as I can about a huge variety of topics from server maintenance, to pattern recognition, to distributed systems (feed fetching).
I guess Newsblur and the subject of this topic solve different problems.
Bonus points for marking feed items as read if its only content is a link to a page I've already seen.
It'd be neat if there was a way to detect when a piece of content was just a reblog of some picture or article or link that's doing the rounds: maybe if the content is only a link plus less than a hundred words?
We will never be able to read everything. The question is: will I spend my time allotted for newsreading by reading the most important things, or will I randomly read important and unimportant things. The real problem is the lack of importance information in the RSS protocol. As a feed creator, no matter how many items I publish each day, people will be unhappy - some want more, some less.
Somebody has to choose which news elements are more important than other elments in a feed. And the only entity to do that is a human. We can outsource it to all users (like Google Reader does with its "like" button and the "magic" view, but this only works for very popular feeds in practice). We could let a third party do it (basically an editor. This makes for complicated 3-way protocol, plus this editor probably wants to get paid). Or we could ask the feed creator to give each item an importance value (1-100 or so). The feed creator is in a unique position: he already invested some time writing the entry (so adding a number isn't a lot of additional effort), plus he already has a certain point of view visible in his writing, so adding importance information wouldn't add a lot of surprises.
RSS readers can then work with that additional metadata in different ways: show a cutoff slider (between 1-100), or prompt the user how many minutes he intends to spend reading and compiling a good selection of all sources.
Options: average the numbers of each feed to catch those that try to gamble the system cut their numbers down.
Suggestions, feedback welcome.
Why? Putting a limit on how many articles you read will mean you don't feel any pressure to read more. It'll also mean that you'll make sure to spend your time reading things that are interesting to you. Your daily selection of 10 articles could be used by a stumbleupon-type learning algorithm (I know NOTHING about these, by the way).
I recently instead made a personal rule to just use google reader for blogs that don't post heavily, usually ones curated by a single person.
That's still too many and I plan to cut it down even more... but it's a weight off my mind to just let all of them go.
A good place to start when pruning your feeds is the "trends" page. http://www.google.com/reader/view/#trends-page
What I really am looking for is a way to manage my Reader feeds so that links to similar sources (or similar stories) either get grouped or prioritized based on the number of shares a la Techmeme.
Here's the use case. When Google shut down Wave or when the EFF did their analysis of the Google/Verizon deal I had at least 20 feeds linking to the same story, which I didn't really need. I should be able to exclude my Tier 1 feeds so they don't get caught up in these rules (i.e., if Gruber talks about it I want to see it, no matter what). The rest of these stories get buried in a Folder similar to the Gmail spam folder (or label, more accurately); I don't see their unread count but they're there if I suspect I'm missing something.
Plus maybe a bonus option to exclude any stories based on productivity or 8-bit cupcakes.
This has much to with your habits. I usually first open Email, Feeds, Twitter and FB and open in new tabs the articles I am interested in. Then if by any chance the ones I find out via twitter or IM, I've already read them before, I don't have to re-read them.
It would be most useful if it could integrate with my Instapaper workflow. If I visit a page and then hit "read later", that shouldn't be marked read in Google Reader until I've archived or deleted it in Instapaper. Similarly, it would be great if marking something read in Google Reader would archive any matching items in my Instapaper account (this might be way beyond the scope of what you're talking about though).
I would be okay with sharing my Instapaper username/password to make that integration work.
The benefit would be that I could easily use different reader applications/services, for example depending on the device I'm using or other needs. This would also make trying out new things, such as the Newsblur much more convenient.
This is why I like the Hacker News format of up voting.
Killer app: hacker news style up-voting across any news topic (aka...reddit?)
2) Why can't Google do this? They have my search/navigation history and my feeds.
3) I was kinda hoping this provided an aggregated RSS feed of my Google reader. Why? Because I have other devices that accept RSS feeds but I don't want to export OPML and then have 2 separate feeds to keep in sync.
Also, speaking of unread flags [grating record scratch sound] I wrote a Chrome extension to add unread flags to HN comments: https://chrome.google.com/extensions/detail/imeeonmdbakdmiln...
Ugh, that was awkward. Sorry about that.