| 02:09 | <Hixie> | Lachy: the whatwg blog seems to be the main user of CPU on whatwg.org -- any chance there's something simple we can do to use a cache or something? |
| 02:09 | <Hixie> | it's not a problem now, but if we ever get /.'ed or something, i'd like to be ready |
| 08:28 | <Lachy> | Hixie, this has some instructions on how to improve WordPress performance http://elliottback.com/wp/archives/2007/04/15/why-my-wordpress-site-is-so-much-faster-than-yours/ |
| 08:29 | <Lachy> | I'll set it up tonight when I get home |
| 09:30 | <Hixie> | wow, tv and i agree on something :-) |
| 10:03 | <Philip`> | Hmph, http://www.google.com/search?q=canvex+survey doesn't find my thing's front page any more |
| 10:04 | <Philip`> | Maybe I should use bookmarks rather than Google when I want to find bits of my own site |
| 10:04 | <Hixie> | heh |
| 10:07 | <Philip`> | (Also I should see if MySQL is fast enough at this kind of database, and then move it onto html5.org) |
| 10:52 | gsnedders | has barely any bookmarks at all |
| 10:52 | <gsnedders> | I just use Google for everything |
| 11:32 | <mpt> | gsnedders, that happened to me in 2001 or so |
| 11:33 | <mpt> | and a feedreader has its eye on most of the rest |
| 11:33 | <gsnedders> | mpt: and now? |
| 11:33 | <mpt> | so all I'll end up with is bookmarklets |
| 13:13 | <hsivonen> | should deprecated language tags be conforming? no? |
| 13:14 | <zcorpan_> | i'd say no |
| 13:18 | <hsivonen> | email time |
| 13:20 | <hsivonen> | hmm. region subtag 001 seem really useful... |
| 13:37 | <gsnedders> | hsivonen: I'd say leave it up to the language tag spec whether it is conforming |
| 13:39 | <hsivonen> | gsnedders: "validating processors SHOULD NOT generate these subtags" |
| 13:39 | <hsivonen> | gsnedders: I take that as failing document conformance |
| 13:39 | <gsnedders> | hsivonen: I take that as needing a warning, not an outright failure |
| 13:41 | <hsivonen> | gsnedders: I'd rather not do warnings with attribute datatypes |
| 13:42 | <hsivonen> | (the API doesn't allow it. I'd have to do the checking through a different API) |
| 13:44 | <hsivonen> | gsnedders: in general, I'd like to take SHOULD NOTs that are not subject to human-assessable context as conformance failures |
| 21:18 | jgraham_ | finds his first mail to the whatwg list on 2004-06-22 |
| 21:20 | <jgraham_> | Oddly enough I haven't changed my basic premise since that first message although I don't doubt I would try to disown many of the intermediate ones |
| 21:28 | <hsivonen> | jgraham_: what's your basic premise? |
| 21:56 | <jgraham_> | hsivonen: That solutions which respect backwards compatibility and have a clear path for adoption are superior to technically more advanced solutions which do not take market forces into account |
| 22:08 | <bewest> | can anyone point me to anything that describes the ways the same origin policy interacts with the "browsing context" and what features of a document are defined by that context? |
| 22:09 | <hsivonen> | jgraham_: I agree with that premise |
| 22:11 | <gsnedders> | looks like I'm going to writing a UTF-16 decoder on the plane tomorrow. |
| 22:11 | <jgraham_> | gsnedders: Going anywhere nice? |
| 22:11 | <kingryan> | jgraham_, hsivonen: I agree as well. |
| 22:11 | <gsnedders> | jgraham_: Paris (so I get the fun of the public transport strike) |
| 22:11 | <hober> | yeah, that sounds right on |
| 22:12 | <Philip`> | gsnedders: Are you writing it on a basic multilingual plane? |
| 22:12 | <jgraham_> | I think it's pretty well accepted by WHATWG types |
| 22:12 | <gsnedders> | Philip`: no, the entire UTF-16 range |
| 22:12 | <jgraham_> | Philip`: That was shameful |
| 22:12 | <gsnedders> | (i.e., 0–10FFFF) |
| 22:13 | <gsnedders> | jgraham_: what was shameful? |
| 22:13 | <jgraham_> | I assume that was a joke |
| 22:13 | <jgraham_> | (writing it on a plane) |
| 22:13 | <gsnedders> | oh. |
| 22:13 | <gsnedders> | very funny. |
| 22:14 | <gsnedders> | </sarcasm> |
| 22:14 | <kingryan> | http://en.wikipedia.org/wiki/Mapping_of_Unicode_characters#Basic_Multilingual_Plane |
| 22:14 | <gsnedders> | kingryan: I know what the BMP is |
| 22:14 | <gsnedders> | but I didn't get the terrible joke he was making about it |
| 22:14 | <kingryan> | "Unexpected end tag (sarcasm). Ignored" |
| 22:15 | <gsnedders> | kingryan: I thought from the discussion on the mailing list a while ago there was a |sarcasm| element with optional start and end tags |
| 22:16 | <Philip`> | You need at least one tag, either start or end |
| 22:16 | <jgraham_> | Yeah, that sounds like a /great/ idea |
| 22:16 | <Philip`> | (This isn't SGML, so we can do that) |
| 22:16 | <kingryan> | why not have a sarcasm element with only an end tag |
| 22:17 | <kingryan> | and you have to infer the start tag |
| 22:17 | <kingryan> | ? |
| 22:17 | <kingryan> | coffee time, bbiab |
| 22:17 | <Philip`> | (and otherwise UAs like Google wouldn't be able to extract semantics reliably from sarcastic documents) |
| 22:17 | <gsnedders> | (but where does the tag start/end?) |
| 22:17 | <gsnedders> | s/tag/element/ |
| 22:17 | gsnedders | facebats self |
| 22:21 | jgraham_ | discovers one of the character encoding issues in html5lib only occurs with python <= 2.4 |
| 22:28 | <gsnedders> | oh well, g'bye. see you either sometime soon if I can get online, or next Friday. |