I seem to be having permission issue using . It manifested last night and I could temporarily not use the tell command either. As far as I know, only gates seem to be problematic at this time and everything else is OK. Just me or any one else having this issue?

Apparently, I can't write in global, trade, etc nor write mail

chest and kits busted, but vault works again for me.

Hrm, all of my vaults are still missing...

Yield wrote: Perhaps I did not word it in the best possible way (I do not have good grammar, by any means). The point I was trying to make was that there are people that 'proxy-vote' for others. Or in other words, log into the voting site and click all their links without even attempting the capchas (which prevents members from illegitimately voting for the server). Your statement just repeated what the last 4 pages of this thread have said. I read it as you knowing absolutely what I was talking about I took it as an insult to my personal competence to read the entire thread. I'm sorry if you took offence at my reply, I tried to write it respectfully anyway. If this is a huge problem it's actually relatively easy to code around and at least determine who is voting erroneously. Assuming the form requires a live session (logged in) then it's a matter of logging session id to the accounts voted. If someone reports fraudulent votes on their behalf then actions can be taken against that logged account/ip address. Relatively easy depending on the skillset of the site maintainers. I've implemented tons of backend code with html/ajax interfaces and even early on the process was not overly complex. Of course, this becomes moot if a system is put in place that will prevent fraudulent activity completely. At that point even if votes are consumed then at least they were completed with a return value to the site and account.