W3C home > Mailing lists > Public > www-style@w3.org > June 2009

Re: New work on fonts at W3C

From: Brad Kemper <brad.kemper@gmail.com>
Date: Thu, 25 Jun 2009 10:07:35 -0700
Cc: "Aryeh Gregor" <Simetrical+w3c@gmail.com>, <robert@ocallahan.org>, "Jonathan Kew" <jonathan@jfkew.plus.com>, <www-style@w3.org>
Message-Id: <F35A6F9C-490C-4560-9C0A-DB5FCA826A38@gmail.com>
To: "Levantovsky, Vladimir" <Vladimir.Levantovsky@MonotypeImaging.com>

On Jun 25, 2009, at 10:02 AM, Levantovsky, Vladimir wrote:

>> Referer-based methods are unreliable, and can block users of your own
>> site as well as letting through users of other sites.  Some software
>> will strip referer headers, or even change them.  (For instance,  
>> IIRC,
>> no browser sends Referer headers from an HTTPS site to an HTTP site.)
>> Depending on referer checking isn't a good idea.
> Thank you. I am not a web developer so I would trust the experts on  
> this.
> My point was that font vendors have so far proven to be reasonable  
> people willing to cooperate, which is contrary to Rob's presumption  
> that we would insist on a particular way of doing things (i.e. root  
> strings).

So you would allow your fonts to be served in their raw format if  
referrer based blocking was used? It could provide a large amount of  
license violation, even if it wasn't perfect.
Received on Thursday, 25 June 2009 17:08:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:37 UTC