| 00:46 | <cwilso> | Notes doc for WHATUP: https://docs.google.com/document/d/1XQLLjETtdBPv-xGiGPRALR4X7hgSb_Lk13bdBucEJ_g/edit?usp=sharing |
| 00:56 | <cwilso> | https://docs.google.com/document/d/1XQLLjETtdBPv-xGiGPRALR4X7hgSb_Lk13bdBucEJ_g/edit?tab=t.0#heading=h.51akrqmzup50 https://webirc.w3.org/?channels=WHATWG |
| 07:37 | <hsivonen> | Is scribing happening in a different GDoc now? |
| 07:48 | <annevk> | It happens on W3C IRC #whatwg due to lack of Matrix bots |
| 08:51 | <cwilso> | note new draft Thursday schedule :https://github.com/whatwg/html/issues/11711#issuecomment-3515612334 |
| 09:07 | <emilio> | TabAtkins: https://github.com/mstange/samply / https://docs.python.org/3/using/cmdline.html / https://share.firefox.dev/43n45Vy |
| 11:38 | <Zoltán Kondér> | I fail to understand why whatwg is focusing on various API's in different browsers. I do protecting my API's to prevent fingerprinting. To me anything that needs the API to work is a threat and it must be contained with urgency. I hardly see any discussion about HTML here it's more like developing full applications that will use the browsers capabilities but completely disregarding the dangers of this. In my opinion anything that depends on specific API's in the browsers is a significant threat. |
| 11:54 | <Zoltán Kondér> | Far as I know W3C and others do working on prevention of fingerprinting, I never seen any discussion regarding this issue in whatwg. The more API's are there which implemented by browsers the bigger the threat. I do not support more and more API's and more and more proposal to depend on them especially not when fingerprinting and privacy is completely left out of discussion. |
| 12:03 | <Zoltán Kondér> | Probably the biggest most meaningful standard would be a new high-level API that mediates or annotates other APIs. One for all - all for one. This way it is possible to protect users privacy, resist fingerprinting etc. Pretty sure a lot of browsers would implement it. The API itself would be difficult but not impossible. Once there is a working version the development would be easier. |
| 12:32 | <freddy> | I think there's significant overlap between whatwg/w3c that I presume most people in either group have seen things like https://www.w3.org/TR/fingerprinting-guidance/ |
| 18:45 | <dveditz> | There's not much discussion of HTML because there aren't many newly-proposed declarative HTML features, and cross-browser compatibility/ambiguity problems are largely addressed or at least known and added to web platform tests. |
| 18:46 | <dveditz> | Most of the activity in non-scripted features is happening in the very active CSS working group, but that's hosted by W3C so it doesn't come up here in WHATWG |
| 18:48 | <dveditz> | And most of the proposals to restrict capabilities of existing APIs are happening in the Privacy WG and CG. Often by the same people who are in this channel! |
| 20:25 | <Noam Rosenthal> | zcorpan, annevk OK to move https://github.com/whatwg/html/issues/11819 to stage 1 following yesterday discussion? |