Fair enough, but then it’s the same thing as open-sourcing the code but not providing support nor binaries.
I mean, personally I also prefer it to FUTO’s proprietary license, that’s for sure. But I’m one of the few privileged users who can build from source.
If this license doesn’t impose any extra restrictions on the code (and as you say, anyone can fork and provide prebuilt binaries), then this would just increase the risk of spreading malware, with no real benefits for the original developers.
In my opinion, if you want to monetize your software without going proprietary, all you have to do is provide the users a convenient way to get it. There are some paid FOSS apps on Google Play, as well as some paid FOSS games on Steam. You don’t want to distribute binaries? Fine, okay, that’s alright and I respect your choice. You don’t want to provide support to non-paying users? Fine, that’s very reasonable in my opinion. But…
…do you want to impose extra restrictions on your code? Fine to me, but then you are no longer doing open source, don’t try to pretend you are. And if you are not imposing any restrictions on the code then you are imho just going to hurt small users. We shouldn’t fight small users imho, we should fight the big corporations exploiting FOSS code for their proprietary businesses. But if there are no extra restrictions on the code, then big corporations wouldn’t care.
That’s my opinion.
As a personal anecdote, recently I installed a co-op videogame on my Linux Steam machine and I couldn’t get past the main menu, I wasted quite a bit of my own and my friend’s time before realizing it was a bug in the Linux build. After reinstalling the Windows version through Proton everything worked flawlessly.
Please don’t publish a Linux build unless you plan to test and maintain it.