Topic on Talk:Flow Portal/Archive2

Jump to navigation Jump to search

Why the reordering of topic discussions?

Diego Moya (talkcontribs)

Looking at the "board and feed" model in Flow Portal/User to User Discussions, I wonder if the decision to "bubble" active topics to the top of the board is a sound one.

Reordering conversations misses a feature of the old talk pages, which is stability. If topics are ordered according to their creation time (just like a blog) instead of their activity, it's easy to know where a particular conversation is located with respect to all others, and use spatial reasoning and "muscle memory" to remind what you have read and what is on your pending list. You don't need to bubble up the entire topic in order to find updates; the feed takes care of that, providing quick access to any active conversation. With the board-and-feed model, reordering the board is redundant, and even harmful.

You also miss any possibility to have a Table of Contents with a summary of not-archived conversations, a really useful feature that is not present in the Flow prototype (see "substantial knowledge base" comment below). Flow seems to assume that conversations that are not active are not important and can be archived, but that's simply not true of Wikipedia talk pages; inactive conversations can contain knowledge and suggestions that can be acted upon, so they should be stored for reference, in an easy-to-retrieve way that doesn't require searching but mere browsing.

I understand the appeal of "infinite scroll" metaphor for boards, but that can be achieved with static boards ordered by creation time. Instead of modelling Flow boards after bulletin boards at internet forums, I find the blog model a better fit for the way conversations are handled at Wikipedia.

Patrick87 (talkcontribs)
Diego Moya (talkcontribs)

The funny thing is that having these particular two features should be relatively simple to program - they're just a query on topic names to show the topics index (LiquidTrheads have it!) and a database index to keep them ordered by date. It's all a matter of design, and providing a clear metaphor for conversations.

I find the "filtered topics" model in both LiquidThreads and Flow quite confusing; the focus on laser-guiding users to the conversation they're interested make it difficult to assess where a conversation is located, as they are devoid of context. This could be fixed by simply providing a more prominent, always visible link to the board name where the topic is stored, and a board index when the user navigates to the main view (which is ordered by creation time by default in order to provide the required spacial grounding - otherwise Flow_Portal/User_to_User_Discussions#Collaborative_Posts would be quite difficult to grasp).

Surely auto-signing, auto-tracking of conversations and a "reply" button to posts instead of editing the whole thread are needed features, and an improvement in presentation of talk pages. But these are not incompatible with the current main page metaphor. The personal feed is enough to guide users to the conversations they're interested in and keeping them updated.

ImperfectlyInformed (talkcontribs)


Isarra (talkcontribs)

Aye, these are good points.