Timeline for answer to Loopholes that are forbidden by default by rydwolf
Current License: CC BY-SA 4.0
Post Revisions
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 21, 2023 at 19:58 | comment | added | rydwolf Mod | @Iamkindofalanguagedev Still invalid. How it's implemented is unobservable and irrelevant to the reasons for why this is annoying | |
| Jul 21, 2023 at 18:48 | comment | added | The Empty String Photographer | What if you implement it yourself? | |
| Apr 30, 2021 at 3:26 | comment | added | rydwolf Mod | @forest Changed it to "near impossible". Thanks! | |
| Apr 30, 2021 at 3:24 | history | edited | rydwolfMod | CC BY-SA 4.0 |
deleted 10 characters in body
|
| Apr 30, 2021 at 2:30 | comment | added | forest | mathematically impossible – It's not impossible, it's just computationally infeasible. | |
| Sep 8, 2020 at 21:22 | comment | added | The Fifth Marshal | Here's a challenge that explicitly allows cryptographic functions. Not that it matters, because challenges are allowed to override standard loopholes, but pointing it out anyway. The only problem with it is the large number of invalid answers. | |
| Sep 8, 2020 at 4:26 | comment | added | the default. | "some very specific challenges may not be susceptible": I think relatively few challenges are. | |
| Sep 8, 2020 at 2:49 | comment | added | Bubbler | Related discussion here and here. | |
| S Sep 8, 2020 at 2:01 | history | answered | rydwolfMod | CC BY-SA 4.0 | |
| S Sep 8, 2020 at 2:01 | history | made wiki | Post Made Community Wiki by rydwolfMod |