Issue 261 data list #519
Issue 261 data list #519
Conversation
…emoval * This is a "getting started" list * The text box is free form text input so if a preexisting reason isn't available type one in. * Moderators and up should specify specifics when possible e.g. "Obfuscated code packer/packed" * Currently the datalists are alphabetized instead of priority... ones reason priorities may be different than anothers so please keep it that way. :) **NOTES**: * The trailing space in the value **is intentional** and should be maintained... the reason will be trimmed on submission thus saving some typing * If anyone is wondering why the `option` tag doesn't have a close tag it's due to [the spec](http://www.w3.org/TR/html-markup/option.html) under [Tag ommision](http://www.w3.org/TR/html-markup/option.html#option-tags) * Accessing the datalist should be accomplished by two single clicks *(currently one to focus and one to activate)* with a pointing device, pressing the space bar when nothing has been previously entered, and of course if you already know it just start typing the first part and it should filter the datalist. * When possibly adding new values try to mirror them into whichever modal datalist with/without a plural value e.g. a repeat offender so usually that User will go away... this won't always be the case and it may eventually veer from this structure a bit. * *Try not to abuse* a generic reason without elaborating e.g. like spamming. * I don't consider "silly scripts" to be a valid reason and neither should anyone else. Remember the "Have fun but at the same time not at some other persons expense." part of the TOS. :) * This is option 2 Applies to OpenUserJS#261
* Pair up JSON with respective `*Modals.html` in includes folder... seems to be the optimum place
**NOTE**:
*mu2* still has a bug where it throws an error if `option` tag doesn't have a close
``` sh-session
mu2/lib/mu/parser.js:158
throw new Error("Unclosed section " + name);
^
Error: Unclosed section modTools.removeReasons
```
... so in short close the tag to avert it.
Closes OpenUserJS#261
Martii
added
CODE
|
Going to leave this available for comment until Sunday evening'ish in case someone wants different default reasons added or a bug detected... if nothing replied then will merge it. |
* Minor glitch perhaps down the line Applies to OpenUserJS#261
|
I wanted to explain "Undocumented auto-like" here. These are scripts that Auto-Like something without the Users permission. Currently we have at least one script now that actually seems nice about auto-liking and documents the Code itself and does not just add their own personal group ids and user ids on FB to improve their stats. This is currently okay in my book because it is clear and concise. However those scripts should always be watched in case they get overzealous and don't document in plain english what groups and users they are auto-liking. e.g. no one here should appreciate an "undocumented auto-like" to an unknown id without their permission. |
Issue 261 data list Auto-merge ... no additional comments
|
There's now an example in the Graveyard on pro with what was detected. This particular author and script also had an undocumented auto-like to a particular user via xhr since it claims to increase likes by using click events... e.g. not fully documented as doing this. |
Martii
added
enhancement
* for possible common reason for removal. Applies to OpenUserJS#519 and OpenUserJS#261 and OpenUserJS#261 (comment) and
See commits for detailed specifics
Root issue is #261