On 2015-03-18 11:31 PM, Isarra Yos wrote:
On 19/03/15 01:42, Danny Horn wrote:
Brad: unfortunately, it's really hard to tell very much from a conversation with messages like "3: Post C: reply to Post A". You could do that with the old model, the new model or the perfect magic Nobel-Prize-winning discussion threading still to be discovered, and it would probably look like nonsense in all three.
We've tried in our testing to pretend that we're having real conversations, so we could see whether there's any logical way to get to eight levels of nested threading. It's not easy to organize make-believe conversations, but if you want to start a thread, I'd be happy to fire up a few sockpuppets and pretend to talk about something with you.
I'm a little confused. Didn't LQT already solve this problem? Why not just nest/thread things the same way it does, or how well-formatted wikitext conversations in general do? That seemed to work fine; the issues with LQT lay elsewhere, and the issue with wikitext really just seems to be it all needs to be done manually and users often don't get it right as a result, hence a good chunk of why we're trying to replace it in the first place.
-I
Yes, Wikitext conversations did have a threading pattern.
From what I can see looking at a long discussion on a random FA talkpage
archive it goes like this: Users indent after each message. Then when it gets too deep someone starts their message with 0 indentation. Conversations with larger messages end up reset quicker.
Unfortunately this model cannot be applied to LQT or Flow.
LQT just keeps indenting even when you would break because the indent is too deep.
Flow tries to fix this by only indenting when replying in a spot where you can't just append.
Frankly the WikiText indentation practice doesn't make sense in LQT or Flow. As I understand we always change the indentation in WikiText in part because it's hard to see where one user's message becomes another with just a signature to break the paragraphs into messages.
That doesn't make sense in LQT or Flow where messages are structured and have an interface to differentiate them.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]