Re: [Fofredux-devel] FoFRedux mailing list

[Benjamin S. <bs...@cr...>]

On Wed, Nov 16, 2005 at 01:09:59AM -0300, Carlos Kozuszko wrote:
> As I told to Andrew, my main interest at hacking fof is my concern about the 
> "reading time" a person assigns to his feeds. I've been working on 
> calculating words per posts averages, an statistics view and i plan to create 
> a view in which you can select "how much time" you want to read of your 
> unread items depending on your reading speed.

Oh, actually I've also spent some time thinking about that, but the
interface issues were more pressing in my initial hacks.  Actually,
several of my interface changes provide even more information gathering
opportunities:

* The keyboard shortcut navigation allows us to gather things like:
  - number of times this item was skipped over without action [1]
  - total time that this item had focus
  - and more

* And my external viewer mode [2] lets you gather roughly the same data,
  but could also track other user activity.

And then we can do things like correlate different "reading moods" with
length of post, which is what it sounds like what you're thinking about,
and from there we can have some controls to help the user select how
he's in the mood to read... yeah.  I like it.  (obviously this is all
just off the top of my head;  it sounds like you've thought about it
more.)

[1] action = mark read, saved, tagged, SOMETHING
[2] Think the frame from google images, but add controls for things like
"next unread [in this feed?]," mark this item read, tag, etc...  

> I've also thought about tagging. What do you think about allowing the user to 
> tag each feed ? Im also thinking about the ability to show the del.icio.us 
> popularity for each item.

It's possible we could use some combination of tagging + delicious to
populate related articles, but I think some of the other stuff would be
more unique and innovative.  Especially some of the ideas about things
we could do with metrics for optimizing reading / attention.

On Wed, Nov 16, 2005 at 06:19:07AM -0500, Andrew Turner wrote:
> An idea I had last night regarding back to the database updating. I
> think we should retain database updates for major release changes. For
> example, v0.2 will change the database, 0.21, 0.22, etc. will add new
> features within the database layout. When we are ready for a database
> change, we will bump to v0.3. At least this kind of numbering scheme
> will minimize database changes by holding them off and making sure we
> have what we want, and also easy to maintain the users' system (update
> them from v0.3 to v0.4 of the db structure)

This seems like a reasonable approach, but that's still only a part of
the bigger DB picture... But I'll save that for Kevin's thread.