| 00:16 | <Christine Belzie> | Hi everyone! I made my first PR: https://github.com/whatwg/html/pull/9714 Can someone review it for me? |
| 12:46 | <annevk> | Domenic: just came across https://github.com/python/cpython/issues/102153. Seems like URL security research is still going strong. |
| 12:48 | <Domenic> | Eh, ecosystems which aren't using the URL Standard seem hopeless anyway |
| 12:50 | <annevk> | That's pretty close to one of the comments there from a long term maintainer. That they probably should have added a WHATWG-compliant package to std. |
| 12:50 | <annevk> | I hope they do it now, not sure they have. No time like the present. |
| 12:52 | <Domenic> | Yeah seems like there's some fun drama in the hidden comments |
| 12:54 | <Domenic> | Ah but the RFC partisans come out later in the thread, sigh |
| 12:57 | <evilpie> | The curl author unfortunately seemed very dismissive of the URL standard as well in a related blog post |
| 12:58 | <Domenic> | I still find that so hilarious... his whole thing is that he thinks http:// is pure, http:/// is necessary for compat, but how dare the WHATWG accept more than three slashes, that's just craziness. |
| 12:59 | <annevk> | Yeah, whenever curl encounters some kind of compatibility problem it turns out that following the URL standard would have helped, but following the URL standard doesn't compute for him so the URL standard is at fault. |
| 12:59 | <annevk> | I tried to understand it for a while, but gave up. |
| 13:09 | <annevk> | He's part of a larger group of people on social media that have the ability and experience to influence and improve web standards for everyone, but they rather complain about the status quo. Even when they know and could reach out to the people involved. |
| 13:10 | <annevk> | (And yeah, they bother me a little bit. 😅) |
| 14:13 | <annevk> | Domenic: "HTML-parse a URL", "encoding-parse a URL", something else? |
| 14:14 | <Domenic> | If it's only for use with Document objects, or maybe even Nodes, I like "HTML-parse". |
| 14:14 | <annevk> | Domenic: the idea would be that the current algorithm becomes a sibling to a "parse a URL" that doesn't take encoding into account that we'd promote people to use that need some kind of document/environment base URL |
| 14:14 | <annevk> | Domenic: XMLHttpRequest and xml-stylesheet will use the legacy algorithm |
| 14:14 | <Domenic> | Maybe encoding-parse is best then |