My example is relevant because it directly counters edw519's implicit claim that "if an idea can be used in surprising ways, that is good" by citing open network connections as an example of something used in surprising ways which are bad, and our opposition to that by using a "not open" stance as the agreed best position.
To be convincing that openness is good, it would need to be established that significant good comes from it, or that more good than bad comes from it, or that at least serious bad cannot come from it or similar.
Saying that X can be used in previously unexpected ways is neither here nor there as an argument for open APIs or collaboration, whether or not I like open APIs and collaboration.
Actually, on rereading your original comment, I think I misunderstood that paragraph. The exact wording is still very confusing to me, but what I think you were trying to say is that edw519's implicit argument (for all X, X should be open because it can be used in surprising ways) can be applied to network connections, where network connections are the X. I thought you meant that firewalls were the X, and that idea is what I was arguing against.
And your firewall example is not relevant. Hackers aren't using firewalls against the companies that employ them, they are circumventing the firewalls. What you said is more like "people can climb over fences easily, so we should stop building them around our yards"