AJMACSERVE  Well, firstly...I'm not ripping you off or trying to take advantage of you. Secondly, you stated "higher end programs that take a long time to code were shareware", ok, my app is only a GUI but it doesn't mean I haven't put a lot of time and effort into the project.

I never wanted to become a programmer, and actually, I still don't. I won't be relying on my software to make a living; I will be getting a job and programming will be a hobby as you described and this is my attempt at "making a little bit of money off it".

Personally, I don't think my software is overpriced. Now of course, you could say I'm biased, but the fact that so many people have purchased my software and have been completely satisfied with it is proof enough on it's own that my software isn't overpriced. If anything, I think the price is very reasonable.

If someone brought out some software for the Mac that did exactly what my app did but for free, good for them. Of course, I'd feel disappointed, anyone would, but not offended; it's new competition that you didn't need to worry about before. However, it doesn't mean I would act any differently about selling my software.

Last but not least, a license for iVPN costs £14.99. The license that people received in version 2.5 is the same as the license that they receive now with version 2.9 and this is the way it will stay. I personally know what it is like to buy something one day and then the next week, a newer version or a newer model is out for the same price; I would never do this with my software because I know how annoying this is.

I don't want to sound like I've been having a go, I'm merely defending myself. If everyone thought like you, no one would be able to sell software; everyone has to start somewhere.  
(Version 2.9)

AJMACSERVE  I'd just like to say that I'm sorry if I have upset quite a few people; this was absolutely not my intention. I would just like to explain to you how this "backdoor" or "home-phone" feature, as you are referring to it, actually works. Since the beginning of iVPN, the software has checked for updates by checking for a file on my web server that contains the most recent version of the app. The only thing I have changed since version 2.4 is that when it detects a version newer than itself, it asks the user to register. There was no underhanded attempt at getting personal information or anything like that, which is what I would refer to as a "backdoor" and a security liability. Also, I would like to remind everyone that iVPN does not actually deal with any of the security features it provides, it merely configures another program that is included with Mac OS X to do this. 'vpnd' is the program that is used to create the VPN server. It is a UNIX application that has been around for years and that anybody can use and configure themselves if they know how.

To show you that I am sorry for any ill feeling that I have caused, I now propose to do the following:

To physically remove the lockout feature of versions 2.4 and 2.45 is not a possibility, and so, I will enable the use of these versions by setting the current version number that is checked for, to version 2.4.

I am aware that some of you will already have versions 2.5 and 2.6 due to an flaw in my code that allowed bypass of registration. This is a learning curve for me.

I will continue development of iVPN (with the registration bypass fixed!) and will put my web server back online, and hope that there are people out there who appreciate all my hard work and will be happy to pay the small amount that I am asking for.

Whilst there have been many of you happy to use my program free of charge, the few users who did donate were happy to pay more than £14.99 for this software, and in some cases, considerably more.

Once again, sorry for this whole misunderstanding. And if any one still has any more queries about these misunderstandings, just let me know.  
(Version 2.6)

AJMACSERVE  The 'backdoors' I put in place were only in version 2.4 and 2.45 and it was so I could start charging people for the software. Anyway...all it did was check for the most recent version of ivpn, and if it was higher, then it would ask you to update and buy the software. I've taken the lock off now anyway because so many people got annoyed for me wanting something in return for my endless hours of work on this software. I'M ONLY 16 FOR GOD'S SAKE!!!   
(Version 2.6)

AJMACSERVE  I've taken the lock of iVPN 2.4 and 2.45  
(Version 2.5)

AJMACSERVE  Sorry, my comment was directed at MU Frequenter. He seems to think I have violated some open source agreement or something. I know you meant no offense.  
(Version 2.5)

AJMACSERVE  iVPN was closed source since version 2.4. I have the right to remove MY OWN software, open source or not, from SourceForge.net's download page.  
(Version 2.5)

AJMACSERVE  You know what, I don't care, have it!  
(Version 2.5)

AJMACSERVE  Who's going to buy iVPN if they can get it for free though? I know what I've done will annoy a lot of people but if I'd have known how popular iVPN was going to be, I would have charged for it from the start. SORRY! Alright? But I need to make money too, just like everyone else.   
(Version 2.5)

AJMACSERVE  Well I'm sorry for wanting something in return for all my hard work. Do you know how many hours of work have gone into developing this application!? I didn't think my app would be so popular and so released it as opensource. Once I saw how many people were downloading it, I realized I could actually make some money from this. If I'd have released it as commercial ware in the first place, then you wouldn't be complaining. More of you should have shown some gratitude by donating.   
(Version 2.5)

AJMACSERVE  Yes, I think vpnd is capable of running both PPTP and L2TP at the same time but it is much more complex to configure if you want this and I'm only 15 and it's exam season so I really don't have the time. I'm struggling to keep up with the feature requests as it is. Sorry.  
(Version 1.5)

AJMACSERVE  Thanks for your comments! I will definitely be taking your advice, you are completely right. About the documentation though. Do you think I need to make a documentation file, or is documentation on my site adequate?  
(Version 1.1)