MeatballWiki does not have any administrators. However, if anyone can figure out how to safely enable those features for anyone to use, we could consider adding them to the site.
That could be a lot of fun since we don't have real authenticated user logins. I'll set Cliff's preferences to replace every 'e' with a link to our favourite .cx domain.
The problem with GlobalReplace is not the implementation. The problem is one of PeerReview. Currently, every action requires only a similar magnitude of review. If we add global actions, then the amount of commensurate review will be much greater than the effort put into the action. Everything must have a BalancingForce. A global action must allow for quick global review. So, one strategy would be to make global search and replace very painful to do. Another option is to improve the power of review capabilities, say by displaying context in the search results. Somewhere in between disabling the action and empowering the review we will reach a balance, and then it will be safe.
So, simply put, how do we throttle the use of this feature? And how do we improve our review capabilities? -- SunirShah
How about some sort of temporary "replace notice" (or "replace object") is created to represent the replace operation? The replace notice would appear on RecentChanges, allowing PeerReview. The replace notice would also allow someone to undo the entire global replace at one stroke through the replace notice. --anon.