>>551
Unfortunately, there is not. In its development, the biggest problems with the tag repo code have been in dealing with its growth, and admin and user controls took a back seat behind the back seat.

This is now a bigger deal, and the PTR janitorial team have given me some suggestions as well. I do not know if I can make it as nice as you want, but when I next do a big iteration on tag repo content updates, I expect to add better client knowledge of clientside changes, the ability to make changes locally and not upload them, and likely some sort of anon 'petitioner id' so you can see your petitions' results and exchange anon messages with janitors.