# Just-in-time behavior nudging

**URL:** <https://meta.discourse.org/t/just-in-time-behavior-nudging/4829>\
**Category:** Feature\
**Tags:** completed\
**Created:** [3월 16, 2013, 11:23오후 UTC](https://meta.discourse.org/t/just-in-time-behavior-nudging/4829 "2013-03-16T23:23:24Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [3월 18, 2013, 11:27오후 UTC](https://meta.discourse.org/t/just-in-time-behavior-nudging/4829/6 "2013-03-18T23:27:55Z")

</div>

> [@aja](#):
>
> Another option would be to automatically catch txtspeak, all-caps, no-caps, etc, and offer the user an auto-correction before posting

I agree with Sam that this needs to be based on actual problems within a community rather than guessing what the problems may be.

And sometimes the detection is hard – for example we say in the FAQ that people should not end posts with signatures, such as:

> Hello, how do I make a post in Discourse?
> 
> Thanks in advance,
> 
> John Q Public, Esquire  
> [http://example.com](http://example.com)

How do we reliably detect a signature at the bottom of a reply? How do you [reliably detect curse words without creating false positives](http://www.codinghorror.com/blog/2008/10/obscenity-filters-bad-idea-or-incredibly-intercoursing-bad-idea.html)? There is a limit to what you can automatically process here.

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.

---

_[View the full topic](https://meta.discourse.org/t/just-in-time-behavior-nudging/4829)._