Page MenuHomePhabricator

Flow pages should allow users to choose between view modes: classic indentation (by topic/replies), "Flow style" indentation and chronological (by timestamp)
Open, NormalPublic

Description

From
https://pt.wikipedia.org/wiki/WP:Esplanada/propostas/Flow_na_Wikip%C3%A9dia:Contato_%285mar2015%29?oldid=41541009

The new model seems to be mixing two display modes:

  1. Chronological
  2. By (sub(sub(...)))topic

I believe indentation should only be used to provide topic information, not chronological information (which seems to be incompatible with the request to allow changing the position of replies in a topic, and would complicate the task of splitting a topic into subtopics). This is exactly what LQT does (and does well).
For a chronological view, I just want a sequence of messages, without any indentation (as happens e.g. on Gmail or Facebook), where a message is after another if, and only if, it was posted some time after the other.

This would be similar to the view options available for mailing lists such as
https://lists.wikimedia.org/pipermail/wikitech-l/
For each month we have: [ Thread ] [ Subject ] [ Author ] [ Date ].

Event Timeline

He7d3r created this task.Mar 17 2015, 11:23 PM
He7d3r updated the task description. (Show Details)
He7d3r raised the priority of this task from to Needs Triage.
He7d3r added a subscriber: He7d3r.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 17 2015, 11:23 PM
He7d3r set Security to None.
Florian added a subscriber: Florian.
DannyH triaged this task as Normal priority.Mar 18 2015, 5:38 PM
DannyH added a subscriber: DannyH.

This is an interesting idea -- I'm going to mark this as normal right now and put it in our Design/Requirements queue to talk about with the team. Thanks!

He7d3r updated the task description. (Show Details)Mar 18 2015, 5:59 PM
He7d3r renamed this task from Flow pages should allow users to choose between two view modes: indented (by topic/replies) and chronological (by timestamp) to Flow pages should allow users to choose between view modes: classic indentation (by topic/replies), "Flow style" indentation and chronological (by timestamp).Jun 4 2015, 3:11 PM
He7d3r added a subscriber: Risker.
qdinar added a subscriber: qdinar.EditedFeb 5 2016, 1:10 PM

if you want to have the classical "diagonal" threads with full functionality, you probably should also put that functionality also to the new compact indendation.

what are currently missing in the flow's compact comments are : 1) several sub-threads to/from every post/comment/reply .

i have made an image to show that functionality in compact comments. that image also shows idea to put threads one behind another. It is here : https://www.mediawiki.org/wiki/File:Compact-comments.png . and i upload it also here.

fix : i delete "2) subthread for the latest post" - it is not feature of classic diagonal thread comments. so, conversely, it should not be used in "compact thread", to be convertable to "diagonal threads".

qdinar added a comment.Feb 5 2016, 2:32 PM

see edition to my previous post. and:

the classic "diagonal thread" comment system/interface can be "hacked" by users, if they are in agreement, - and, the "several subthreads" can be used as a thread, and "reply" can be used as "create a subthread", but, if they do so, then that system has the "subthread for the latest post" but lacks "several subthreads".

DannyH removed a subscriber: DannyH.Feb 5 2016, 5:45 PM
qdinar added a comment.EditedFeb 6 2016, 5:49 AM

the classic threads system really does not have "subthreads", it has multiple continuations of threads, and second continuation is adopted/interpreted as a subthread in the flow's new indendation model, and third continuation is not possible there in flow.

i have made an image of classic comments modified into compact form, and with multiple continuations put one behind another. see: https://www.mediawiki.org/wiki/File:Compact-classic-comment-threads.gif

Restricted Application added a project: Growth-Team. · View Herald TranscriptMar 10 2019, 3:16 AM