 How can we address the issue of security and intellectual property for these applications because the base code is open source and therefore open and available to everyone? So there's two parts to that, security. And there's always this worry that if you open up your software, somebody is going to put a Trojan horse in it. In practice that doesn't happen. There are some log arguments that security is better in an environment where all your code is visible to a large number of people. And most open source projects you don't get, you just put your code straight into the code base for that open source project, it gets checked over before it goes in. So there's much better checking I think on an open source, at least to better security. When you're working with an open source project, I think that the primary, and this comes to another question also about how to commercialize it, the primary push is not about getting everybody to buy your project, it's getting people to use it and getting people to contribute back to it and again back to the community. And I think that the protection for the project in itself comes out of the people who are using it and the people who recognize your moral right to exercise the authority of having started or being the primary maintainer of such a project.