Board Thread:Code Review/@comment-24757753-20160428191600/@comment-24473195-20160429102325

I've had ideas for tools that save stuff to the wiki as well, but the fact that everybody can mess with the settings is annoying, and  it  seemed  bit strange to store JS in CSS. Using CSS as storage for js works, but I would suggest that you use commented CSS instead of plain JS to make sure it is at least a valid CSS file, and strip it when reading it.

Alternatively, you could always use local storage for the settings or if you want to go through extremes store it in a normal user subpage, and only parse the last revision made by the page's author (https://www.mediawiki.org/wiki/API:Revisions -> rvexcludeuser). That would make it easier to ignore spam. Alternatively, you could try to convince staff to project .json pages in a user's subpages (https://phabricator.wikimedia.org/T76554).

It might be a good idea to make a json gui that parses the configuration file and presents it in an interface for the users. There are probably hundreds of tools like that in github.