"Recipient may not use, copy, reproduce, modify, publicly perform or display, create derivative works of, sell, auction, loan, lease, rent, distribute, transfer or disclose all or any part of the Service (including, without limitation, any screenshots, videos, documentation or manuals relating to the Service) except as provided in this Agreement."
I can understand why one would want to keep control over what's being blogged about your new product when it's still in beta. During this phase, it's very easy to damage a products' reputation by unjustly trashing it, before it is even finished. Especially if a tester doesn't really get the 'beta' part, this is a real risk. A few weeks ago, I noticed a similar effect with regards to OpenSim too.
Perhaps Google is to blame here. They keep many of their products in perpetual beta; millions of users have gotten used to using full fledged, essentially finished services which still carry the 'beta' designation and I guess most of them don't pay attention to that label anymore.
Yet, I'm not sure that being restrictive about what publicity you allow during beta, is the best way to create a buzz about a new product. Metaplace might, after all, be able to get some free publicity out of the blogging community, and as far as I'm concerned they are missing out on part of that now.
Back to Metaplace. I think it's pretty safe to tell you that I was able to use it with Minefield, the daily Firefox 3.1 development build. I created my own place, and some new tiles which I used to dress it up a bit:
Anyway, if you want to try Metaplace, I can invite another five persons if the NWN invite codes are all used!