Explicit selection of optional features by community owner

The other day I posted a bug (Joe fixed it already) where because I used a html in a post, and because the text included the following characters in order ">D" the display unexpectedly rendered >D.

I thought immediately that my group is business oriented, and that there would be no use for this type of feature anyway for me. Then I thought that a good idea would be to offer the manager the ability to select from a list of such features (check boxes) to avoid the possibility of such situations all together. EX:

⊗ interpret text for emoticons
⊗ automatically subscribe members to discussions
⊗ offer crossposting option in discussions

In this case a business group would NOT opt in for having text interpreted as emoticons, but a social site may. A high traffic site would NOT opt into autosubscription of new discussions, but a smaller group may. Groups with unsophisticated members would NOT opt into use of the crossposting capability.

This could solve many of the issues discussed in other threads regarding features tailored for large vs. small groups, private vs. public groups, and business vs. social groups, sophisticated users vs. unsophisticated users. Allow owners to choose to apply only the set of features most helpful to their community's needs and usage. At the heart of this assumption is accepting that some features just do not wok well with certain types of groups.