IRC log of webfonts on 2023-05-16
Timestamps are in UTC.
- 15:48:59 [RRSAgent]
- RRSAgent has joined #webfonts
- 15:49:03 [RRSAgent]
- logging to https://www.w3.org/2023/05/16-webfonts-irc
- 15:49:09 [Zakim]
- Zakim has joined #webfonts
- 15:49:22 [chris]
- rrsagent, make logs public
- 15:59:39 [Garret]
- Garret has joined #webfonts
- 16:00:06 [Vlad]
- Vlad has joined #webfonts
- 16:00:53 [Vlad]
- zakim, start meeting
- 16:00:53 [Zakim]
- RRSAgent, make logs Public
- 16:00:55 [Zakim]
- Meeting: Web Fonts Working Group Teleconference
- 16:01:27 [chris]
- present+
- 16:02:48 [sergeym]
- sergeym has joined #webfonts
- 16:02:57 [Vlad]
- present+
- 16:03:04 [sergeym]
- present+
- 16:04:44 [skef]
- skef has joined #webfonts
- 16:05:57 [skef]
- present+
- 16:06:00 [Garret]
- present+
- 16:06:26 [skef]
- First item: Addressing code points and privacy
- 16:06:42 [chris]
- scribenick: skef
- 16:06:59 [skef]
- Simulation results for noise injection
- 16:07:06 [jpamental]
- jpamental has joined #webfonts
- 16:07:12 [jpamental]
- present+
- 16:08:00 [skef]
- Simulation to help determine value of adding noise and how much noise needs to be added, also compare with existing loading methods (like unicode range)
- 16:09:10 [skef]
- Simulation assumes that a system for the initial subset will also work for augmentation
- 16:09:47 [skef]
- Count up pages that match the subset with the additional codepoints
- 16:11:10 [skef]
- Tested against unicode range convention, no additional noise, additional codepoints with equal weights, and additional codepoints weighted by frequency of occurrence
- 16:13:34 [skef]
- Even with latin, not adding noise means that a significant (but small) percentage of pages only have ~10 matches
- 16:14:08 [skef]
- Unweighted noise doesn't help all that much, weighted noise does
- 16:15:31 [skef]
- Japanese: with no noise a significant number of pages can be uniquely identified. Adding noise definitely improves over doing nothing.
- 16:16:51 [skef]
- Summary: Adding noise improves the situation, weighed noise works better, different scripts have different noise requirements
- 16:18:22 [skef]
- Additional findings: Number of added codepoints for a given request should also be randomized. Should change the spec to avoid re-requesting codepoints. Might consider adding a unicode-range in IFT font-faces to allow the client to scope the initial request.
- 16:18:31 [skef]
- Further testing upcoming.
- 16:22:32 [skef]
- Malicious content is out of scope for the noise question
- 16:23:05 [skef]
- Will probably wind up with two recommendations: CJK and non-CJK
- 16:26:40 [skef]
- Some of the group has reviewed the explainer for TAG, others will review it soon
- 16:31:49 [chris]
- We could do with signals from Mozilla - Jonathan Kew, Martin Thomson
- 16:33:38 [skef]
- Next topic: Range Request and CORS
- 16:38:27 [skef]
- (The question is what circumstances a preflight request can be avoided when doing multi-range requests
- 16:38:31 [skef]
- )
- 16:40:50 [skef]
- Next item: Review remaining issues.
- 16:40:58 [chris]
- https://github.com/w3c/IFT/issues?q=is%3Aissue+is%3Aopen+-label%3A%22Range+Request%22+
- 16:44:59 [skef]
- There was an updated QUERY spec published may 10th but only with minor changes
- 16:50:19 [chris]
- rrsagent, make minutes
- 16:50:20 [RRSAgent]
- I have made the request to generate https://www.w3.org/2023/05/16-webfonts-minutes.html chris
- 16:50:28 [jpamental]
- bye
- 16:50:28 [jpamental]
- exit
- 18:20:24 [Zakim]
- Zakim has left #webfonts