Here's a question for the WPMU pros out there - and maybe an enlightening moment for anyone who hasn't peeked too far under the hood yet.
I am working on a cloning tool in php that will take any specified blog id and clone it to any target blog id including theme, plugins, posts, all settings, etc.
In the process I'm looking at the sql output and noticing a LOT of data bloat and garbage in the wp_*_options table (even with my relatively young wpmu installation). They're _transient_feed entries and I definitely don't want to clone them along with the useful data.
From what I gather, it's stuff that is fed into the dashboard from WP planet and whatever. Even more concerning is the idea that every single blog has copies of all this garbage (http://mu.wordpress.org/forums/topic/14504) and even after excluding from a clone programmatically it will just start to fill up again. With hundreds or even thousands of sites, this would add significantly to database size, backup time / size, performance.
So, for those that know about this, is there a way to turn this off - to prevent the options tables from getting stuffed with all that clutter? To delete any current clutter? Maybe something simple I am missing?
And if not - does anyone run any routine scripts to keep those entries cleaned out?