In case of numeric passcodes, e.g. for numeric locks on doors etc, anyone can agree "poor passwords" are ones with specific pattern, e.g. 1234, 1111, 2468, 1122, etc. (as well as ones that form a clear graphical pattern on the keypad, e.g. "cross", 159-357)
If I want to generate a lot of random ...
@Maltysen You're welcome to develop an idea based on this guy's deeply rooted issues and write it into a challenge. But don't edit the post into a challenge.
how about a truthy/falsey golf, disallowing numbers that are all the same digit, 2 of the same and 2 of the same, linear, and physical lines on a keypad.
@Maltysen If the OP has an actual problem he wants to solve, asking for help via a code golf contest is guaranteed to produce the worst possible solutions to the problem.
Inspired by this badly received migrated post.
The head of security at your company is concerned about your PIN generating system after it gave him 12345. He also didn't really appreciate the Spaceballs joke you made at his expense, so you've been delegated to re-write the PIN generator. Since i...
I've already posted an answer in it...? codegolf.stackexchange.com/a/60313/44713 It's not valid for the question (as it was made after the question), but we still answered it. c:
@VTCAKAVSMoACE I didn't know you posted an answer in it. Also, there are tabs in your Java source code, which guarantees I will never use ShadyAsFuck. :P
@Optimizer From my small experience watching ghost hunter shows, they are active until there is camera around. At that point they change to "only make spooky noises and move things around just barely enough to be mistaken for a little wind" mode.
@flawr Oh - the rows were mixed. x refers to <>, not ><, and o refers to ><, not <>, of which the opposite was in the wiki. I edited the wiki for correctness.