It's interesting to hear from type designer, certainly not a voice that is heard often enough, at least not in the web developer community. His concern that "someone can take one of our fonts, put it in a freely accessible directory on their server, that’s a violation of most of our license agreements" is nothing new. Håkon's "free font" technique does not introduce this problem, nor does it make it any worse in my opinion.
'Håkon's "free font" technique does not introduce this problem, nor does it make it any worse in my opinion.'
It does make it worse - previously, there was no reason to make proprietary fonts available on the Web unless you were (a) the vendor, or (b) deliberately infringing copyright. Håkon's technique gives people a good reason to put proprietary font files online, and hence introduces a new third class of users, each of whom might or might not be using the font legitimately.
Comments
It's interesting to hear from type designer, certainly not a voice that is heard often enough, at least not in the web developer community. His concern that "someone can take one of our fonts, put it in a freely accessible directory on their server, that’s a violation of most of our license agreements" is nothing new. Håkon's "free font" technique does not introduce this problem, nor does it make it any worse in my opinion.
As a side note, I find it incredibly ironic how difficult it is to read that web page due to the "design" choices made. Thank god for readability: http://blog.arc90.com/2009/04/readability_updated_with_some....
'Håkon's "free font" technique does not introduce this problem, nor does it make it any worse in my opinion.'
It does make it worse - previously, there was no reason to make proprietary fonts available on the Web unless you were (a) the vendor, or (b) deliberately infringing copyright. Håkon's technique gives people a good reason to put proprietary font files online, and hence introduces a new third class of users, each of whom might or might not be using the font legitimately.