So obviously this would be for communities with very high standards for behavior/etc.
What would you all think about the usefulness of running some sort of basic semantic analysis (or even just word matching) on new posts, and popping up a little “nudge” when the post is questionable? Like so: (sorry, my attempts to be insulting are really lame)
Another option would be to automatically catch txtspeak, all-caps, no-caps, etc, and offer the user an auto-correction before posting. Something like: “Hello Aja! We’ve automatically edited a bit of the spelling and/or grammar in your contribution. Please take a look over these changes, and feel free to make any additional corrections before submitting your post. Thanks!”
It’s a great idea! We talked a lot about the possibility of providing “gentle education” to the user in early Discourse discussions. I believe where we left it was “probably applicable to a plug-in”, but I’ve always been a strong supporter of some these common “catch-alls” in the core game play.
I remember bringing up the ALL CAPS OMG YOU’RE YELLING to @CodingHorror as an easy win, and he felt that it just wasn’t as common in practice as we thought. I have a skewed perspective with the communities I’m involved in…some of which are comprised of users less than technical than us.
I think the last thing you want to do is foster an environment where people think that they can score conversation points by arguing about grammar and posting conventions. These types of rules and ‘standards’ have a habit of becoming ends in themselves, markers of ingroup-outgroup status, rather than means towards good conversation.
However, if a system were to be intelligent enough to handle the capture/education of this on its own, one could argue that the community could keep itself in check by enforcing the abstinence of back-seat pedantry involving said conventions.
Rather than scoring points on calling out each other’s grammar, the points would be scored for exactly the opposite, reminding each other that the system handles it.
I did a fair bit of similar work at Stack Overflow with @codinghorror.
I like the idea, and in high scale communities it can really help tidying stuff up.
Thing is, to build this kind of feature properly you need to have a corpus of data and problem patterns you are trying to eradicate. Otherwise we would be building this based on guess work that very much risks an unbalanced approach.
Keep in mind we already handle some of the more trivial ones with our entropy checks, however its a system we should be constantly refining based on real-world data.
We do enforce a number of fairly narrow, specific rules around topic titles based on noise characters, length, entropy, and so forth – for example, I see topics here that end in multiple question marks, but we should not allow that.
Since then, we also automatically fix a few problems with post titles based on real user behavior @geek saw at his Discourse forum. Titles matter a lot, so things like all caps titles, titles with tons of exclamation points, etc we silently fix for the user behind the scenes.
I should mention that the (great) new book by Dan Ariely covers similar ground
Turns out most people steal just enough so that they can still consider themselves fundamentally honest people… but “just in time” reminders not to steal, to be morally upright, had a shockingly high success rate in reducing these kinds of casual theft rates.
정말 오래된 주제네요! Discourse는 2013년 이후로 ‘적시에’ 주는 알림(just in time nudging) 기능을 많이 추가했고, 마크다운 사용법과 Discourse 내 탐색법을 교육하기 위해 앞으로도 더 많은 기능을 추가할 계획입니다. 오늘 전에 본 적 없는 정말 멋진 새로운 알림을 발견했습니다!
이 답글을 작성하면서 편집기에서 경고가 떴습니다! 잠시 망설이게 했지만, 이 주제를 다시 살리는 대담함을 발휘해 보겠습니다. 편집기에서 이런 알림이 제출하기 전에 알려주어 좋다고 생각합니다. 위에서 보이는 새로운 팝업 알림은 제출한 후에 나타나고 “이 메시지를 다시 표시하지 않음” 옵션을 제공하여 덜 부담스러운 다른 접근 방식을 취하고 있어 흥미롭습니다.
assume you mean send it “locally” for free
