>If it's a bug in the theme, the application developer is just not responsible for it.
And how many times would they have to tell the end user who opened an issue on their app's tracker that?
I'm afraid there is no way around that issue with free software.
There's a super clever life hack my wife used when working in e-commerce. She kept a text file with prepared replies to most common issues and questions, and used the OS's built-in copy-paste functionality to quickly responding to messages asking about the same thing. I hear this kind of functionality is even supported directly in desktop e-mail clients these days.
The users always blame the app. And then when they can't get the app to work they stop using it.
Which means the developer just lost a potential customer.
If you don't like people modifying your software, don't publish it under permissive license.
How do you solve the social problem of a large majority who feel entitled to everything for free?
My solution was to give up, publish free stuff anonymously with zero support, and charge for anything I actually care about. My charged-for software has multiple orders of magnitude more users than the free software, and effectively funds the free software that nobody actually uses.
I regularly think about not publishing the free stuff anymore, but I figure that even if a single person benefits from it, it's a net-positive, and so I keep going. It doesn't stop it being incredibly demoralising.
