You are reading a single comment by @bq and its replies. Click here to read the full conversation.
  • The problem with quoting a whole message every time is that it may be lengthy and then results in amplification.

    1 line gets quoted, the next person replies to the prior and that quotes the whole message included the quoted bit, and so it goes until you have a Christmas Tree of HTML blockquotes.

    This is then the worst possible outcome for the very devices you mentioned: mobile phones or tablets. The page becomes a scrollfest, and the blockquotes squash the text into ever diminishing horizontal width... itself causing the page to lengthen even more and amplifying the effect of that scrollfest.

    I know that because we tested it. Then we laughed, hard... and agreed not to do that because it was plainly silly. Very funny, but ultimately silly.

    The chaining of replies works best, but ideally we'd have finished the implementation more fully... as in, if you clicked "in reply to" we wouldn't jump you away but would have fetched that single comment via AJAX and shown it in context. We didn't finish that unfortunately, but that would resolve the "what was this in reply to" thing.

    It doesn't solve fisking though. But then again, those who fisk are indistinguishable from trolls most of the time, so I'm cool with not encouraging that.

  • @mashton - I've just tried the highlight and reply functionality on my iphone and it puts the chevron in the right place. It's not broken everywhere.

    @Velocio - selecting on iOS is cumbersome - could you have a quote button next to 'reply' that automatically quoted the first 40 or so characters of the post? That, in many cases, would be sufficient. And always more satisfactory than

    lines starting with a 'greater than' denote quoted text

  • What browser are you using on the iPhone? I use chrome and you get no quote at all.

About

Avatar for bq @bq started