I'm going to step out here for the sake of argument and say, "Why?!?!?" You want a setting that requires you to specifically /msg (via some syntax) the cb, or someone, or what you type goes where? /dev/null? And you want the setting to be off by default, only selectable if you want it? By the time most people will want it, it is because they've made that error and it is already too late. I also suspect it would be cumbersome enough that very few would leave the setting on for long once they did turn it on. Also, would it affect just the CB interface on the webpage, or all clients you may use? In the latter case, depending on the syntax chosen for it, would that require modifications to all the various other CB clients? How much additional load would be generated by having to look at an incoming posting to the CB, look up the user's setting, then determine if it should be posted or not?

I have to say I am not as crazy about the idea as the much simpler one of thinking before you hit submit. ailie reminded me of an old saying a few nights ago in the CB: "Choose your words carefully/make them short and sweet/for you never know from day to day/which ones you may have to eat." Besides those factors above, you can only make any reasonably-complex system proof against foolish errors only to a point, or make it unusable, and Nature is always coming up with better combinations of foolishness. (And please do not take that to mean that I think anyone herein a fool, only that we all may make foolish errors or typos from time to time.) To be quite honest, I actually can't recall any time such an accident has occurred where there were aftereffects that were anything other than perhaps a slight embarassment or a short period of jesting as a result (although I could very well be wrong in this point).