Out of curiosity, why did you opt out of your former idea of going with Communiteq hosting? — Leontiskos
Fair question.
I'm sure Communiteq is good but I think we're better off long-term with
Discourse.org . My strategy is to go with the official premium product and see if we can afford it—we can always move to Communiteq or self-hosted later on if it proves to be too much. But I don't see why we couldn't cover $100/month. We've just been too relaxed about subscriptions—if we'd made a bigger deal about it I'm sure we could have got more members to subscribe.
This is a serious website and we want it to keep going for a long time. It deserves the real thing, not just a cheaper third party alternative. I realize this might seem shallow or impressionistic but I think it's significant nonetheless.
Discourse.org seems like the professional option.
On
Discourse.org we're dealing with the people who develop the software. They know what they are doing. Updates and plugin compatibility and what-have-you are handled by those who know the code most intimately. Support is fast and definitive, and the service is extrememely reliable.
It also has better performance due to differences in their server infrastructure, apparently.
Incidentally, I tried NodeBB for a couple of weeks and XenForo for a couple of days, and some other more Enterprisey things like
circle.so . I was almost ready to go with NodeBB but then I tried Discourse again and the experience was substantially better than NodeBB.
Also, ↪regarding
"form and content in philosophy," I would suggest "zen mode reading" (and not just composing), where one can devote their entire screen to the topic at hand (example). Although I think Discourse allows this modification on a user level by default...? — Leontiskos
I can't see this functionality anywhere but I just tried the Firefox reader-view and it worked fine, so I presume other browsers can achieve the same thing. Anyway look:
When the sidebar is collapsed it's pretty distraction-free, no?
It's also worth noting that once web pages and forums became asynchronous the distinction between live vs. non-live chat was largely superseded. Older forum software which was not asynchronous (and required a page re-load after submitting a post or PM) is now gone. It was that page load that made it feel "non-live." Of course, that model was nice insofar as it felt more "long form" (like sending a letter), but the current Shoutbox is this weird amalgam between short-form and long-form media. An instant message style UI would simply be better for the TPF Shoutbox (although the non-paginated Discourse format is already more "live" than a paginated format). It would also help discourage short-form bleed into the main forum. — Leontiskos
Yes, good points. The difference is partly in how the functionality is presented: in the long-form discussion, the big serious composer window is obviously for long posts, whereas it's just a small bare-bones textbox in live chat. Also we can implement minimum post length in the discussions.
Relatedly, I would propose time limits on editing. The perpetual editing of TPF leads to careless composition, in my opinion. — Leontiskos
Yes, I'll be looking into that. I might make it subsciber-based. I'm pretty sure it can be implemented in Discourse anyway.
You can, but the search is wonky. It isn't thread-indexed, but rather functions via a search on common words in the thread title. So it will return results for any thread with similar titles. There are other problems too, such as the fact that threads containing special characters are unsearchable, and users with special name formats are not present in the mentions dropdown. — Leontiskos
Yeah, the search here is seriously defective.