ty mannah! Yep, fixed the review notification issue yesterday (it'll be an ongoing manual task until the software is finished being rewritten and users can choose that for themselves). I don't know what it is with reviews, honestly. We encourage the users TO review. Of course, if they're CHILDREN visiting this site, they'll not review so they don't get caught. If you take a peek at moderation stats, you'll see exactly what I mean on that end...as far as how many are deleted all the time.
Because of how the tables are set up, even with the new engine in place (once we get to the upgraded search function), I'm not sure that it'll be feasible to do a search across all the subdomains for stories. Possibly, but we'll see. The concern there is that the query load for that kind of search can shut down the database server, because of too many queries run. Servers are set with a query limit per hour. With 8.2GB of data, we could easily exceed that limit. When the query limit is reached and/or exceeded, the server has to reset itself, which can take up to an hour. Which means nothing will work, at all. Most commonly, when you see "MySQL error, could not connect to the database" it's either caused by query overload, or misconfiguration. In this for instance, it would be query overload. So, I think you can see when the new search function using the better engine is implemented, we're going to be careful in just how that's done.