Thanks for moving the comment, probably a better home for it!
I don’t dislike Discourse in principle - I just don’t think it’s neccessarily appropriate for BoingBoing. It’s certainly an interesting replacement for a forum, which might be a nice addition; but certainly not an appropriate replacement, IMO.
Something like Reddit (which I believe is a comparable example to what this system is trying to achieve) has a journey that plays out like so:
Homepage > Post (with comments) > Source
But BB’s journey is now:
Homepage > Post > Comments
OR
Homepage > Post > Source
It’s clunky and doesn’t really achieve the same thing. It’s certainly not a user journey that anyone would design intentionally. It’s very disjointed. Also getting back to the actual BB site is a pain; if you’re 100 posts in on a discourse thread you have to scroll all the way to the top (waiting for each set of previous comments to load in), chasing the second menu-bar, so you can hit the BB logo. It shouldn’t really be quicker to just type in the URL, but it is. This IMO is the biggest impact on BB as a business, as it doesn’t encourage the user to explore more content; it just dumps them into a forum.
The platform itself is pretty slick, the features, how stuff works etc. It’s very nicely put together, but in my humble opinion it’s not right for BB. As I noted in my OP you just end up either wanting the comments on the article, or the article in the comments. Which just brings us back to what existed before.
However…
Discourse in-line on the article would be fine. Although the threading issue doesn’t change - it’s like all the bad stuff about forums, combined with the bad stuff with comments. I can’t help but feel that you’ve been defending something for a while now @codinghorror, and there comes a point where you have to wonder if it’s something that may work for you, but doesn’t work for others. I honestly can’t imagine any user getting any benefit from a combination of threaded comments and chronological comments - as it just confuses everything - it should really be one or the other. Have you guys done any UAT on the system? Maybe it would shut us all up from complaining if there was actually something qualitative to back up the system, rather than just 1 persons opinion.
I also think it’s pretty crazy to not have mobile support on day 1; I don’t have access to your metrics, so maybe it was a business decision, but a mobile-first approach would have catered for everyone and minimised any extra workload.
tldr; it’s not the end of days, I’m still commenting (hello!), but it feels like a step in the wrong direction.