3 ms·

The people who draft these licenses are pretty smart and explain VERY CLEARLY what is and is not allowed. For instance! > The following are allowed by this agr

The people who draft these licenses are pretty smart and explain VERY CLEARLY what is and is not allowed. For instance! > The following are allowed by this agreement; you may: > 1b. Use the WOFF, WOFF2, and EOT web font formats provided by Process to style text on your websites via the CSS @font-face rule for an unlimited number of websites whose content is controlled by you. You agree to use reasonable measures to ensure the fonts are available only for the process of styling text on websites. At a minimum, and by way of illustration not limitation, reasonable measures include i) preventing unlicensed third-party access, i.e. hotlinking and, ii) not allowing direct download of the fonts unrelated to the process of styling text for your website. and > This agreement expressly prohibits the following; you may not: > 2e. Store or use the fonts in any way that makes them accessible to the public or non-licensed third parties, except where such use is expressly allowed by this Agreement. This includes, but is not limited to, distribution of the fonts through file sharing services and online version control repositories accessible by the public. https://processtypefoundry.com/help/base/webfont-license-agreement/ https://processtypefoundry.com/help/base/webfont-license-agr... Seems pretty clear!

lol768 7y ago
>At a minimum, and by way of illustration not limitation, reasonable measures include i) preventing unlicensed third-party access, i.e. hotlinking and, ii) not allowing direct download of the fonts unrelated to the process of styling text for your website. It's not clear. How on earth are you supposed to implement ii)? I'm not interested in answers which mention the Referer header. There are a myriad of factors which can prevent it being sent with the original request required the style elements on the site.
- roywiggins 7y ago
  Yes, that one's a bit tricky, isn't it? You might inspect the user-agent to at least try and only serve the font to browsers. You might also make sure that if there is a Referer, isn't not someone else's referer. I don't think it has to be foolproof to satisfy the terms of the license. It might also just be: you have to check the referer. If your website has technical issues such that sometimes the referer isn't available, you have to change it so it always is. Or host it on one of the approved third-party hosts referenced in the license.

lol768 7y ago

>At a minimum, and by way of illustration not limitation, reasonable measures include i) preventing unlicensed third-party access, i.e. hotlinking and, ii) not allowing direct download of the fonts unrelated to the process of styling text for your website. It's not clear. How on earth are you supposed to implement ii)? I'm not interested in answers which mention the Referer header. There are a myriad of factors which can prevent it being sent with the original request required the style elements on the site.

roywiggins 7y ago
Yes, that one's a bit tricky, isn't it? You might inspect the user-agent to at least try and only serve the font to browsers. You might also make sure that if there is a Referer, isn't not someone else's referer. I don't think it has to be foolproof to satisfy the terms of the license. It might also just be: you have to check the referer. If your website has technical issues such that sometimes the referer isn't available, you have to change it so it always is. Or host it on one of the approved third-party hosts referenced in the license.