{"id":3459,"date":"2018-09-30T19:14:25","date_gmt":"2018-09-30T11:14:25","guid":{"rendered":"https:\/\/www.bytebot.net\/blog\/?p=3459"},"modified":"2018-09-30T19:14:25","modified_gmt":"2018-09-30T11:14:25","slug":"gpgtools-support-subscription-in-situ-license-change","status":"publish","type":"post","link":"http:\/\/www.bytebot.net\/blog\/archives\/2018\/09\/30\/gpgtools-support-subscription-in-situ-license-change","title":{"rendered":"GPGTools Support Subscription – in-situ license change"},"content":{"rendered":"

Not brave enough to upgrade to macOS Mojave on my main workhorse yet, I did however click update on GPGTools<\/a> which only required me restarting Apple Mail. I was very shocked when I saw the following pop-up:<\/p>\n

\"GPGMail<\/p>\n

This was an in-situ upgrade from what was free\/open source software, to a sudden pop-up nag telling me that I would need to get a license to continue to encrypt\/decrypt my mail with ease. I checked out the support plan<\/a>, which is USD$23.90, and might be something I have to pay for yearly<\/strong>, since a major version coincides with a macOS release according to the FAQ<\/a>. <\/p>\n

Being in the open source industry for 22 years (longer than the term has been around; so let’s call it free software<\/em>), I’ve seen many license kerfuffles, and I think one of the worst ways to surprise someone is a license change in-situ<\/strong>. In a world where we do git pull’s and just move on, the license is sacrosanct. I’m glad that these developers didn’t focus on mucking with the license and if you choose not to pay USD$23.90 yearly, you can still compile the software yourself.<\/p>\n

\n
\n

Am I still allowed to compile my own version of GPG Mail \/ GPG Suite removing any code regarding the trial or activation?<\/strong><\/p>\n

You absolutely are, the GPL enforces that. You will find the source code on this website and on Github.
\nWe would kindly like to ask you not to use our names or icons if you plan to publish a binary for others to use.<\/p>\n<\/blockquote>\n<\/blockquote>\n

Am I going to compile from source<\/a>? If this was infrastructure software, definitely, yes. Am I going to pay these developers? I do not know, I still have 30 days to decide. <\/p>\n

They clearly learned their lesson, do read the open letter to their users<\/a> (yes, they’ve had this as a plan for a while, but maybe it wasn’t clear enough). These people aren’t a big evil corp neither did that raise venture capital from what I can tell. They’re independent developers, and if there is something a Mac user tends to do, is that they tend to support indie developers. <\/p>\n

If I already pay an Apple tax, the question then becomes: do I pay for yet another app, that seems to basically be a subscription, or do I compile the software? Comes back to the old adage of, spend money to save time, or spend time to save money.<\/strong><\/p>\n

Share this:<\/h3>