Yes, redistribution is not listed yet. It could be easily added without damaging the main goal of the license. I'm still wondering what are the pros and cons of "redistribution" for this type of license and the possible use cases: nowadays most libraries can be download as dependencies (e.g. from NPM, RubyGems, etc.), so redistribution outside the official channels seems unnecessary. Why redistribution would be necessary / useful?
Yes, the expression "this permission" is somewhat ambiguous, however the MIT license is widely accepted and has the same sentence, so I think it's ok and the meaning is clear (for historical reasons). Or maybe I could use the expression "this license".
I have compared multiple OSS licenses and extracted the "common" part of the disclaimer. Many parts of the MIT license disclaimer are not present in the BSD for example, so they seem unnecessarily redundant. So I think that what I wrote is enough. I'm not a lawyer, because I graduated in CS, but I studied law in Italy for 2 years.
About using the MIT license directly (that was my first idea) I had a small doubt about the copyright of the license itself: I don't think that there is one, but as a precaution, and in order to create something even more clear, I decided to write everything from scratch.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for your feedback, I really appreciate it!
About using the MIT license directly (that was my first idea) I had a small doubt about the copyright of the license itself: I don't think that there is one, but as a precaution, and in order to create something even more clear, I decided to write everything from scratch.