Re: recomendations for creating a beta with date to expire
Re: recomendations for creating a beta with date to expire
- Subject: Re: recomendations for creating a beta with date to expire
- From: Nick Zitzmann <email@hidden>
- Date: Sun, 14 Aug 2011 16:44:34 -0600
On Aug 14, 2011, at 2:37 PM, Wilker wrote:
> Hi Guys,
>
> I'm thinking about releasing a beta version of my software. Im thinking
> about use the same strategy as Reeder for Mac did, betas with fixed time to
> expire.
>
> What you recommendations to make it safer? Im thinking about do an internet
> request do get a world clock, and check with this time to see if the
> software is expired (and close the software in this case).
>
> You have any other hints for doing this? Maybe any encryption on code to
> make it harder to crack or other things like this?
I would just use the system clock. Most people aren't going to change their clock to run something that's time-limited that has expired, especially if that would interfere with other applications, and the people who will do that probably won't buy the final product anyway. And requiring a network connection to run software that normally doesn't need a network connection, such as your proposal, is a major inconvenience for a lot of people.
Restrictive DRM inconveniences people, and really restrictive DRM drives people to piracy if the pirated edition is more convenient to use than the legit version.
Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden