martin-braun
commented
2 months ago I'm a victim to this. I paid for this software to support the developer, but to be fair, I recalled it was closed source back when I bought that. However, to my "positive surprise" I learned it's "open-source" simply by looking at the repository at a later stage, just to feel dump for being that naive, thank you for bringing attention to this.
Like you, I have no problem for this being closed source, and I bought PRO while believing it to be closed-sourc, too. No issue with that, I just feel tricked in my later false-positive discovery of this being "open-source".
If its not open source, you should not keep this stuff here with downloads from releases inside github WITHOUT ADDING A BIG DISCLAIMER on the readme stating that is not open source. its not an empty repo either, you have old code there, so its REALLY misleading.
Its ok to be closed source, but be HONEST about it. There is nothing in the readme saying its closed, and you have a big "Download from github releases" which imply its at least source available (you know, there is even a source code.zip there). Yes, you have a TINY statement in FAQ of your website (not on readme) saying this is not open source anymore, but this is not enough and you know you are doing a misleading scammy thing for better marketing. And there is another comment in here from more than a year stating the same thing and you agreed with it but didnt change anything...
I was literally about to pay for PRO thinking this was open source until I realized its not and I had been deceived. I would probally have bought pro anyway if it was clear it was closed from the start, but will for sure not anymore.
(edit: seems I had actually finished the purchase so I will actually have to ask for a refund)