Marti Martz

This issue is still open because it would nice to have another QSP, maybe `model`, that would just return results from the items from the model removed and ignore everything...

And perhaps a "not" flag QSP... to invert the search. --- `depth` with `shallow` vs `deep` vs `surface` ?? ... script searching is quite "deep" right now since it goes...

Added tracking upstream label due to [`content.*`](https://github.com/OpenUserJs/OpenUserJS.org/blob/c431410d908db1e84a53f1e8d9bb4f65b75bd97e/libs/modelQuery.js#L136) not working currently.... and it would be nice to find the documentation for this. I never did find the syntax reference for it.

Make sure we triple check the html markup sanitizing and md _(gfm)_... there's currently an issue with content in code fences being stripped nicely... haven't reported it yet because everyone...

> but what exactly is wrong with that json? Should look like this: ``` json { "Monkey Barrel": [ "/scripts/show/114843", { "recent posts": "/posts?kind=all", "recent topics": "/topics", "recent comments": "/comments",...

> Would not stripping the `class` attribute be horrible? You mean whitelisting the `class` attribute? It all depends on if `javascript:void(0)` and everything else script related in the value would...

**NOTE**: More links added in [previous post](#issuecomment-46105687) to examine --- Going to do some tests here... so this particular reply may change some: Define a table with GH gfm |...

So bringing this back to topic basically we're missing "pin" which I don't recommend keeping our comment reply box open constantly. It has full screen editing now which is pretty...

> What buttons does anyone want to see? Reiterating again... will close soon if there isn't any interest.

Investigated this. *bootstrap-markdown* only supports jQuery `$('selector').markdown({ additionalButtons`... Due to migration away from jQuery in our core, esp. in the client-side scripts, this is now not programmatically an option. e.g....