It's a simple chat, and that's all I wanted or needed.

Only one suggestion. Actually it's a major oversight that may force me to restrict it to back end use. I'm on a shared host and have to cut the sql queries way back (I've set them to 60 seconds). Unfortunately there is no flood control, and there really ought to be. It's a pretty basic need in any Web based chat function. When entries are only sent every 60 seconds, it's going to be tempting for users to get frustrated, and make multiple sends to each other thinking they are not being answered. The chat window being so small, (I don't want it any bigger), it could be a real pain for users to have to scroll up and down trying to make sense of the delayed exchanges.

Could we please, please get flood control in this???

Please? Thanks for the hard work. I'll be looking for updates to this!