I’m not @Heffalump_and_Roo; but I think they were asking not how to get to the post being quoted, but whether @codinghorror’s reply to that post was meant to imply that codinghorror thought that Heffalump_and_Roo had intended to allocate blame in it.
FWIW, it looks to me like codinghorror had just hit ‘reply’ to the post instead of to the thread as a whole; that probably being the last post in the thread at the time when they did so. I’ve done that on occasion by accident. – another post did intervene, but judging by the timestamps may have done so while codinghorror was typing.
I can create it if you like, or perhaps someone more familiar with that aspect of the discussion would be willing to excavate the relevant bits from this topic to the new one?
Welcome back, @codinghorror! I just wanted to say that I’ve gotten much more used to the new board software in the last few months. There’s a few nitpicks here and there, but overall it’s a very solid piece of software. Thanks for your efforts, and I hope you stick around.
BTW, I hope you restore your avatar to the cool “hair-standing-on-end” one.
I’ll tell you one thing, there are far worse out there. More than a year since the Adobe Community forums moved from Jive to Khorous and we’re still having issues. It is far, far less functional than Discourse. For example, we just (as in the last week or so) got the ability to quote text from earlier messages and it’s not what you’d call easy. And the system will randomly start kicking people off after 15 minutes so they have to re-sign in while leaving other users signed in for days at a time; in a month or so it’ll move on to a new group. Although Adobe does let you insert graphics without having them hosted on another site, but that’s because it’s a user support site and that’s sort of necessary.
I’ll admit to having been a bit wary at first, but for the most part I’ve been pretty happy with how Discourse works.
That’s good to know! If we had a sales team, I’d sic them on Adobe
In general I (and we, as a team) are adamant that the moment-to-moment experience of “playing” Discourse should be enjoyable and satisfying – like a fun conversation at a fun dinner party with interesting people. We might even learn something!
A lot of that depends on the Shadowy Powers That Be treating moderation and moderators with respect and empowering said moderators to keep things cool, because there are a lot of deeply un-cool people out there.
Everyone reading this is, of course, are very cool. As am I. Those are just, like, facts, man.
No one in charge of the forums knows why TPTB picked Khorus, or why there are so many issues for the Adobe forums using it. Rumor has it that it is in use for other sites (such as Autodesk) with far fewer issues, but it’s been one loooooong bitchfest for us. Unfortunately, since Adobe has only been on it for about a year and a half, I doubt if there’s any interest in another migration even if I knew who to point you to (or you had sales teams to be pointed).
Something else they only JUST added was a notification that a new post has been made to a thread and a way to know if you’ve already responded. Who leaves that sort of thing OUT of forum software and then makes such a production of adding it in and drags their feet in doing so?
FWIW, I really like Discourse. I’ve had no problem getting it to do what I need. It’s pretty intuitive for the basics. I have to search around for some things, but I’ve been on VBulletin for years and still have to search around with it, too.
The smileys are the now-standard set of emoji that come with a modern OS, both desktop and mobile. I do appreciate the inclusion of the full set of flags, something that Windows 10 will probably never have.
Still hate it. The endless page length and the search hijacking is what makes it intolerable for me.
My vastly, vasty reduced participation is largely attributed to this. But, I’m just one inconsequential person, and no one will miss my charter subscription once it lapses.
One form of that is a consequence of infinite scroll: the normal browser “search in page” doesn’t work because there’s no page, only a variable-sized window into a variable-length thread.
If you’re used to hitting ctrl-f and getting the browser’s search facility, Discourse intercepting it for its own search tool (which behaves differently) is an unpleasant difference.
