User blog comment:Kirkburn/Technical Update: September 2, 2015/@comment-1757994-20150903225322/@comment-5065259-20150904203117

@Saftzie Don't jump to assume something. I have my own global JS and CSS working just fine and am capable of expanding existing JS/css. I have asked DuckSoup during office hours last week, he didn't have an exact answer (weeks rather than months) for when JS would be unlocked. They are still working on it, continuing to pressure staff to give an exact answer will only result in you being ignored.

Staff made the mistake of granting local admins the edituserjs and editusercss permission rights, they have now since removed those and now only users themselves will be able to edit their own personal though for the time being its locked to staff. DuckSoup said admin access to personal js and css was for emergency use only, though we won't know if it was abused at all by abusive or mean admins. those two permission can be granted to other groups despite the default being otherwise, the only case where someone should be allowed to change personal js or css is by a competent user that is trusted rather than any admin on wikia.

The moderator group was in part created due to complaints over regular users improperly removing threads or restoring admin closed threads, these were loopholes that admins could do nothing about besides threaten to give a block.

if a user leaves the wiki for good, you can always maintain their code yourself or ask for a review at the dev wiki. if the dev wiki finds errors and helps to fix the code, simply notify your community to switch scripts then request deletion of the user's page if admins are not granted the right to delete. this is fairly easy to minimize the security risk of this. most scripts created by users competent in css or js will work just fine even without touching them. this is a relatively simple solution, no need to get upset or be concerned about.

i won't be bothering to respond any further