I run a few sites for various projects and peer groups, and I configure Discourse with the following ideas in mind:
- Reduce distraction
- Keep it simple
- Content is ephemeral
With that in mind…
…I leave chat channel retention days
at the default 90 days or shorter.
Since my personal/private communities are semi-intentional (meaning everyone knows someone, not random connections from the net), I worry less about moderation in chat, and am more concerned about hosting the personal chat logs of my friends, and hence I want them to disappear fastest of all content on the site!
In this use case, chat might replace SMS… but I am not counting on it! However, today a tree fell over one of two roads leading to the school, and we got multiple email messages about it. I read them after I returned from school drop-off. Maybe there is a role for chat in there, somewhere.
It did not occur to me to break down this use case in this manner, but I will give it a try!
To have this conversation, let’s focus on one at a time: technical/social/legal, in order of how much I think I am an expert.
The Technical
When I composed this list…
…I was surprised by how easy it was to describe what I was building. It is because I actually turned off a lot of Discourse features to get the site how I wanted it.
For discussion, I have two challenges for you:
- What is a great format to capture the technical aspects of a Discourse?
- Ask me anything about how the site is technically configured!