We should be testing with The Big List of Naughty Strings

(User Story, Investigate , Priority: High, Test Status: No automated tests yet , Reported By Justin du Coeur, )
Summary: Aaron pointed out the BLNS, which is simply a text file full of problematic strings that sometimes cause issues. We should come up with a test for running through those in various places.
Note that doing this test properly is apt to be slow-running, since we probably should be trying them individually.
It should be a full integration test, going all the way through the UI to the back end and checking the resulting output. While it would be much easier to simply run these as a unit test, it's much more useful if they hit both the UI and the database.
That said, we should also write a test that sends these directly into the API. We shouldn't count on the UI to screen them out. The API-driven tests are, if anything, more important than a full functional test.
Make sure to try these in the MySQL stuff, even more than the user-level code. Try them as handles and as display names, for example, as well as Space and Thing names.