The AniBlog Tourney (where I completely approve of blatant bribery) gave me the impetus to start an updating exercise of my AniBlog Google Reader subscriptions and to review the way I have been using Google Reader. (BTW I used to use Bloglines but having one less sign-in was too big a draw.) I am also belatedly trying to recall and reflect on the advice of an audio book (title: Blogging for business? author: Chris Andersen??) about using feedreaders as well as to do some wish-listing:
1. If there’s a huge backlog (due to, for e.g., AFK or lack of internets connection), just Mark all as read and live to read another day.
I use this selectively. Previously if I had missed a couple of days, the thought of the hundreds of unread entries would prevent me from opening my Reader until I had a big block of time to launch an all out assault which would exhaust me rinse repeat. I also had this hang-up about having to finish all the entries at one go because I was trying to avoid unread items stuck in between my current and previous reads (set to new items only, sort by oldest?).
Eventually worked around this by, sometimes, opening up the folders and reading subscriptions by blog rather than folder. Also using the List view (rather than Expanded view) also helped to cut down on loading and reading times. List view is great especially for blogs that have a lot of screencaps but don’t define the width/height of the images which can be annoying to read in Expanded view when the loading images constantly bumpabump the text down (Aroduc, I’m looking at you). Unfortunately, unlike in Expanded view, I don’t know how to get items marked as read simply by scrolling past them. Nor do I know how to get individual items marked as read/unread.
2. Unsubscribe feeds that you never read
Sounds like common sense housekeeping but, in the context of the aniblog ecosphere, this is not ideal for me. Sometimes I enjoy an author’s writing but, for one or two seasons, she might not blog any series that I’m watching or interested in following. Luckily it’s not too difficult to manage by marking all as read in each individual subscription using List view (easy win!).
I realize there is some element of aniblogging that is about advocacy, trying to get others to join in the watching and, subsequently, the discussion of a particular series. But unless I find two or more bloggers, whom I use as trusted proxies for particular genres, doing such advocacy, it’s more likely than not that I will simply Mark all as read without reading. Elliptical or comparative blog entries are more effective in swaying me though.
WRT blog feeds that I do actually unsubscribe, I would prefer it if there was some way to keep the feed URL on file but not actually draw from the feed. This is a testament to how much I like the “You are already subscribed to this feed” warning in Google Reader. Possible workaround is to stuff all these into an Unsubscribed (haha!) folder and then just Mark all as read whenever I open Google Reader. But I feel kinda dumb doing this (which is not onerous in of itself except for the frequency of experiencing this sensation in my life).
Also I would be megas-happy if there was also a way to include some kind of non-public notation, within Google Reader, to remember why I unsubscribed in the first place. (Can use Notes but there’s a snag as it’s linked to Shared Items?)
In Windows, the “There are unused icons on your desktop” prompt can be pretty annoying (I only have the recycling bin on mine) but something similar which announces “The following feeds have been silent for (user specified time period)” could be useful for periodic spring cleaning i.e. shifting into the dead/hiatus folder (who knows? They might just totali pop up again!). Or for the more manually inclined, show “Feed subscribed since (date)” and “Most recent post on (date)” under the Subscriptions tab.
3. Things the Blog Owners Could Do
It would nice if blogs offered a choice of full and summary feeds but using List view seems to allow me to have my cake and eat it too.
For team blogs, I can see that there will be (a) demand (or two) for author feeds. Under WordPress this can already for done by using a plugin (prolly) or creating a category for the author and then subscribing to the category feed (definitely). From a producer perspective, this could be seen as an unwelcome way to disaggregate a team blog but while I believe a blog owner’s sovereignty over said blog is absolute, the reader is still, ultimately, king and this kind of functionality will probably come offered as standard in the future.