Umtauscher wrote:So what you are saying: If you go out of business and or your server(s) are down or both our installations will become useless. I cannot see, how that's not a significant change.
That isn't what we said. If our backend server goes down then your already activated license will continue to run fine on your Mac. In fact, that was one of the core requirements we had when switching to the new licensing model. I even implemented it so that the Indigo Server won't pause for a single millisecond on launch waiting for the server. As always, usability and customer experience are a huge focus for us.
This does not, of course, allow Indigo to run on a different Mac than it was activated on, so in the event they we are no longer in business we will release a utility to provide license transferring and/or a bug fix release that allows transferring. But for server outages you will be totally unaffected in ability to run Indigo. Additionally, Indigo 7.1 is a transitional release in that it does not require you to authenticate with our Indigo Server for activation (although it will prompt you upon every launch). Indigo 7.2 will require authentication, but only if it wasn't done in 7.1.
Umtauscher wrote:Is it that you are not trusting your customers or what is the cause for this change?
It is several different things. For one, having licensing tied to a registration code just doesn't work well. People lose their registration codes, they make typos entering them, etc. We also want to get the Indigo Server paired with everyones' backend Indigo Account because there is potential for optional cloud-based functionality we can provide in the future. This is step one in that process of being able to offer some new functionality.
And yes of course, some people "misunderstand" the licensing model and think they can install Indigo Server in more than one house. Having a licensing activation model that more accurately reflects the actual license helps avoid that misunderstanding.
Umtauscher wrote:I am not amused - and I will NOT update until this is resolved.
That is your decision to make. We most definitely will never be going back to the previous activation/licensing scheme.