Timeline for answer to Things to avoid when writing challenges by xnor
Current License: CC BY-SA 3.0
Post Revisions
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 11, 2017 at 23:35 | history | edited | Riker | CC BY-SA 3.0 |
added 423 characters in body
|
| Mar 16, 2017 at 16:03 | history | edited | CommunityBot |
replaced http://meta.codegolf.stackexchange.com/ with https://codegolf.meta.stackexchange.com/
|
|
| Mar 16, 2017 at 16:03 | history | edited | CommunityBot |
replaced http://meta.codegolf.stackexchange.com/ with https://codegolf.meta.stackexchange.com/
|
|
| Mar 16, 2017 at 16:03 | history | edited | CommunityBot |
replaced http://meta.codegolf.stackexchange.com/ with https://codegolf.meta.stackexchange.com/
|
|
| Mar 16, 2017 at 16:03 | history | edited | CommunityBot |
replaced http://meta.codegolf.stackexchange.com/ with https://codegolf.meta.stackexchange.com/
|
|
| Mar 16, 2017 at 16:03 | history | edited | CommunityBot |
replaced http://meta.codegolf.stackexchange.com/ with https://codegolf.meta.stackexchange.com/
|
|
| Oct 3, 2016 at 16:43 | comment | added | Nathan Merrill | Broadly allowing standard loopholes is a bad idea, but we frequently have good challenges that allow a single loophole. For example, Fetching the desired output from an external source has been "overriden" a couple of times, such as for Automate the OEIS | |
| Jul 27, 2016 at 5:09 | comment | added | user45941 | I'd argue that it's worth removing the allowance from the challenge completely, even if the author wants it to stay. We as a community have overwhelmingly voted to disallow the standard loopholes across the site, so one user should not be able to override that strong consensus. | |
| Jul 27, 2016 at 3:13 | history | answered | xnor | CC BY-SA 3.0 |