1,572 karma · joined May 31, 2011
Passwords should be hashed non-reversible (ideally using a slow hash). The original password is to no use of the application.
And sending plain-text passwords to users is even more bad[1].
Problem solved.
Major changes are PSR-0 support (conventions for naming files and directories for autoloading purposes), and better Request / Response isolation.
In git, it just creates one file with a 40 byte hex.
If you are learning a set of 'incantations', git will always seem hard to use. But if you take some time to learn how git works on the inside (which is really not that hard), it gets much easier to understand why and how you need to use a certain command.
Some argue that this is why git is bad, but I'd argue that this in the end is a good thing, because it gives you so much more power.
Learning how to use git is an investment, bit in my opinion an investment worthwhile.
The problem right now is that the user mostly has very little opportunity to improve his question, because most of the time it has already been closed, and has very little chance of getting opened again (unless the question is flagged for moderator attention).
> 983.544.651.006.435.431.129.340.665.918.456.708.968.598.498.835
or 9.8 * 10^47 combinations are possible. Although this doesn't give the complete picture, this shows how big the sha1 space is.
Validating on the other hand is checking if the values satisfy the expected requirements.
You only want to apply certain filters if you know they apply the current output. (htmlentities if output as html, mysql_real_escape_string if embedded in a query).
Libraries with different code styles can be used together without problems. It seems like they are using the PSR to declare they're own style as superior.
At this point they had to make a choice and they chose for their paying customers and drop pastie.org
That's why they enforce people to incubate a topic site and only allow it to go through if it's substantial enough.