– A view which includes all opened threads with unread replies, in addition to any unopened favorited threads.
Yes.
I'd be inclined to sort by continuity, I think, and allow this to be changed by clicking header links
The reason I suggested “group by continuity” is to make it easy to scan the list and pick something without accidentally reading out of continuity order. (Note that grouping is “just” sorting followed by inserting headers in the HTML whenever the sorted column changes value from one row to the next.)
Possibly if there were a way to sort by last read, that'd be convenient?
I think there's enough possible-things-to-do-here that effort should be put towards
somewhat more general sort-and-filter features so users can do things that weren't Thought Of Explicitly and there isn't an explosion of slightly different views in the UI and code.
Now, my personal super-awesome-sort-order preference would be to magically discriminate between "reading from the beginning" and "caught up" threads. Within the “caught up”, they should be sorted by
most number of replies first, which makes for the most efficient and contextful reading and slightly discourages “oh look, there's 1 more reply in the last minute, let's read it”. “Reading from the beginning” would be separated so as not to be perpetually on the top of the sort order. But I totally don't want you to bother implementing
that.
Also a note that this is probably not highest priority right now – I think we're focusing on tests and smaller added behaviors, so we can upgrade Rails and then continue development.
I have no objections there!