User blog comment:Deadcoder/Petition to Allow Verbatim/@comment-24473195-20150918173652

The security risk of verbatim is too high to ignore. They've allowed its use for many years, so I'm not at all surprised that they are killing it.

Rather than implementing stuff using verbatim, the best approach is to identify those edge use-cases and develop solutions for them. But looking at the numbers of Js/verbatim users, it doesn't seem like a feasible solution.

First, every single extension that they activate undergoes a security, usability, and performance evaluation. They can't do this for verbatim, because it is like leaving a window permanently open (a great security risk).

Second, it is a very "cheap" solution to a bigger problem. Wikia didn't and doesn't have the infrastructure to develop all widgets and tools people may need, so instead it allowed a tool that facilitates this, despite them knowing from the onset that it was a great security risk.

Thirdly, though some admins and communities may be trustworthy, what's to happen when those admins leave, become disgruntled with wikia, or simply allow someone else to use their account?