I don't think it really matters. These things will exist, anyone who matters will realise they're not legit. They won't make significant sales (without significant added value) it won't detract from your reputation; etc.
I don't think it really matters. These things will exist, anyone who matters will realise they're not legit. They won't make significant sales (without significant added value) it won't detract from your reputation; etc.
> The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
If you leave the MIT license anywhere in your server alongside the licensed code, with no public access, you are complying.
The license doesn't require anyone to provide a copy of the license and attribution along with the output, only when the software is distributed.
(I think; IANAL)
I.e. if you don't like it the solution is not AGPL or source available but no reuse allowrd or whatever, it's closed source.
It pains me to say this because I started in a proprietary software world early in my career and I hate it for 99% of the use cases but... proprietary licenses do have a place.
The author also thinks the people they're upset about are jerks, even though they fully acknowledge they have the right to be. They're fairly clear about that. And even if they continued to be jerks, the author would be happier if the license they had chosen required them to be slightly less jerkish.
(Or at least could, and the more it sounds like a small helper lib / WordPress plugin type thing the more likely. As much as some dislike it, this is a big selling point of GitHub and its stars etc. OP's things sound like something I'd find on Sourceforge, and not really be able to work out if it was original or not.)