I have noted that people have been asking about what we are doing for fund raising. I actually have been reluctant to talk about our funding situation simply because it never has been successful. We our participating with the FSF in fundraising through the working together for free software fund and I think we have now for more than a year. The main reason I had been reluctant to do crowd funding, for example like mailpile did, rather honestly, is, based on all other funding experiences I have ever had, I feared it would be entirely unsuccessful as well, and that would be even more of a motivational set back than not doing so.
Our primary public resource is a development server hosted by a volunteer entirely for free, and we were very lucky to finally get that earlier in the year. Some have asked what funding we might need. I do think just to keep things going the way we do actually need to, we would need to find a minimum of 10k, and most ideally we would wish to secure 100K for the next year or two.
In regards to success and failure of other SIP based VoIP clients, which so often is discussed, one of the reasons I held back on doing one for so long is that I did not want to create yet another client that would also be too complex for normal people to setup and actually get working in real world environments. I feel we have finally come up with a design that offers the true simplicity needed for our goals, and have worked through enough of the other problems that I believe we can finally provide one that can finally just work out of the box when it is complete. Antisipate is not meant to address all the many complex enterprise integration needs and specialized features, or to support multiple protocols, that many other existing VoIP applications provide, but rather will provide a simple and reliable means to do secure communications that just works, while remaining faithfully standards compliant and fully inter-operable with other people who may be using such things.
Antisipate is also helping us address issues in sipwitch itself, particularly in that it has made completion of sipwitch media proxy integration, and other sipwitch features, much more urgent. I believe the sipwitch 2.0 feature set will be completed and delivered in conjunction with completion of the first widely usable antisipate client. Our goals do require delivering both together.