[Disclaimer seeing as the original joke was missed by many - this site link is totally tongue in cheek too. DON'T use the suggested password]
 - https://mostsecure.pw/
An error occurred during a connection to mostsecure.pw. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG
Just me? Is this just too secure™ for Firefox' liking?
I love a good in-joke.
Here, check mine:
For extra credit, I will point out (which you may not know EGreg?) that the password he speaks verbally, and the password that appears on the display visually, are NOT the same and differ by a few digits near the end, a small mistake in production.
The code on the screen (in upper case letters)
What if, instead of a password, the text to be censored is:
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
(That's a code that can be used to crack Blu-Ray discs).
Some people just don't have a sense of humor.
Thanks for your benevolence.
I remember because you showed a similarly poor attitude in another thread. That attitude was so out of line with what I expect from HN that your username was seared in my mind :)
Your profile also says "Commentors with novelty usernames should not expect responses.". What if someone with a novelty username teaches you something and you have a question to further your learning. You won't respond?
The security community I grew up with was welcoming and understanding, and it sparked an interest I never would have realized otherwise.
I feel comfortable assuming the original PR is a joke.
The plural of anecdote is not data, but I have first hand experience with someone who can make a pull request but doesn't understand password best practices at all.
Granted it might be because I taught them to make pull requests, but still...
I know people who wrote code for their thesis in Python but can't grasp why indentation matters. You'd be surprised by what people do and don't know.
How can one write code (that runs!) for one's thesis without paying attention to Python's semantically significant whitespace?
By fiddling around with different indentations levels till the code works.
So much code out there is written this way.
Kind of gives a new meaning to 'iterating' on one's code doesn't it?
I expect it was, as the other commenter said, probably via an IDE like PyCharm. I never asked because there's no good way to ask a question like that.
But that's my point, people's knowledge is all over the place. It's probably a joke, but it could easily not be.
After submitting changes that started 10 indents past the previous line, and had little to no rhyme or reason for subsequent indentation, we asked them to reformat and resubmit. When it became clear that they could not, we reviewed the code itself separately from the indentation and reformatted it ourselves.
Multiple co-workers sat next to them to try to explain how to line things up vertically, but they were unable to do so without said help.
This was over the course of about two weeks in which we were instructed to try to bring them onboard some of our projects. Both our and their projects at the time were frontend web projects.
I have not looked at any of their code outside what was submitted to our side, but I do know they are praised for the quality of their work by management.
That was horrifying to realize that the person writing the front end for an ecommerce application not only could not calculate tax, but would brag about how he doesn't need to know basic math.
You can make these sorts of trivial changes just by clicking around the GitHub web UI, I could probably tell a 12 year old how to make a trivial change like this, regardless of their coding expertise https://help.github.com/articles/editing-files-in-your-repos...
I am not sure the issue poster really uses that password...