Re: Aggregating and displaying feeds

["Bill Kearney" <wkearney99@hotmail.com>]

> As for context switching, I don't want to mix contexts. But my 
point is
> that if you read 10 feeds on a given subject, there's not a one to 
one
> match between feed and context. For instance, take a feed from 
Moreover
> based on a search for P2P. Mix it with direct feeds from OpenP2P,
> Peertal and a few others on P2P. All the items will be about P2P and
> from the POV of getting the latest news it wouldn't matter which
> particular feed the item came from. So why group them by feed?  

Yes, *you* don't want to mix contexts.  I want the *ability* to mix 
contexts at will.  I suspect I'll only want two or three.  However, 
I'm sure my selections are unlikely to serve everyone's needs.  Thus 
I'm suggesting the client interfaces support a variety of contexts.  
This will drive the need for feeds to actually *provide* useful 
information in support.  So I'm saying the client needs should be 
considered when creating feeds.

I'm thinking along the lines of you reading your synthetic P2P feed.  
You see an article by someone, or from a channel of interest.  You'd 
probably be interested in switching contexts to see other materials 
from that author or presently on that feed.  This is what I mean by 
context switching.  

Let's say I see an interesting author pop up referenced via a rarely-
read feed.  I might want to wander over into the feed to see what 
else is happening.  This is a pain in the ass with most current 
readers.  Not that they're defective, just lacking this ability.  
They're close; tantalizingly so, but not quite there (yet).

-Bill Kearney