| 00:34 | <MikeSmith> | annevk: no clue about that spam |
| 00:34 | <MikeSmith> | the headers show it coming from 66.53.221.33 |
| 00:34 | <MikeSmith> | annevk: no clue about that spam |
| 00:35 | <MikeSmith> | the headers show it coming from 66.53.221.33 |
| 00:36 | <Hixie> | ok path primtives are in and now paintable |
| 00:36 | <Hixie> | i'm gonna leave it like that over the weekend to see how many revert requests it gets before moving on to the next feature (ellipses) |
| 00:36 | <Hixie> | ok path primtives are in and now paintable |
| 00:37 | <Hixie> | not really happy with the way i'm planning on doing ellipses, btw; if anyone has a better api idea please put it on the wiki http://wiki.whatwg.org/wiki/Canvas#Ellipses |
| 00:37 | <Hixie> | i'm gonna leave it like that over the weekend to see how many revert requests it gets before moving on to the next feature (ellipses) |
| 00:37 | <Hixie> | not really happy with the way i'm planning on doing ellipses, btw; if anyone has a better api idea please put it on the wiki http://wiki.whatwg.org/wiki/Canvas#Ellipses |
| 00:39 | <MikeSmith> | annevk: hmm but the fantasai one was sent from 66.194.95.2 through a different smtp server |
| 00:39 | <MikeSmith> | annevk: hmm but the fantasai one was sent from 66.194.95.2 through a different smtp server |
| 00:40 | <MikeSmith> | eh? |
| 00:41 | <MikeSmith> | https://www.google.com/#hl=en&safe=off&output=search&sclient=psy-ab&q=66.194.95.2&oq=66.194.95.2&aq=f&aqi=&aql=&gs_sm=3&gs_upl=1648l1648l0l2154l1l1l0l0l0l0l384l384l3-1l1l0&gs_l=hp.3...1648l1648l0l2154l1l1l0l0l0l0l384l384l3-1l1l0&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.,cf.osb&fp=25cdb3d2f0978fa0&biw=1275&bih=658 |
| 00:41 | <Hixie> | those e-mails are spamming a url to get w3 page rank |
| 00:41 | <Hixie> | look at their sig |
| 00:41 | <MikeSmith> | tabatkins⊙6192 |
| 00:41 | <Hixie> | (it's a phone sex page) |
| 00:41 | <MikeSmith> | ah |
| 00:41 | <MikeSmith> | eh? |
| 00:41 | <MikeSmith> | https://www.google.com/#hl=en&safe=off&output=search&sclient=psy-ab&q=66.194.95.2&oq=66.194.95.2&aq=f&aqi=&aql=&gs_sm=3&gs_upl=1648l1648l0l2154l1l1l0l0l0l0l384l384l3-1l1l0&gs_l=hp.3...1648l1648l0l2154l1l1l0l0l0l0l384l384l3-1l1l0&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.,cf.osb&fp=25cdb3d2f0978fa0&biw=1275&bih=658 |
| 00:41 | <Hixie> | those e-mails are spamming a url to get w3 page rank |
| 00:41 | <Hixie> | look at their sig |
| 00:41 | <MikeSmith> | tabatkins⊙6192 |
| 00:41 | <Hixie> | (it's a phone sex page) |
| 00:41 | <MikeSmith> | ah |
| 00:42 | <Hixie> | some day w3c will start using rel=nofollow and it'll stop happening :-) |
| 00:42 | <Hixie> | bbiab |
| 00:42 | <Hixie> | some day w3c will start using rel=nofollow and it'll stop happening :-) |
| 00:42 | <Hixie> | bbiab |
| 00:45 | <MikeSmith> | ok, I marked both the www-dom one and spec-prod one was spam in the archives |
| 00:45 | <MikeSmith> | if anybody notices others, lemme know |
| 00:45 | <MikeSmith> | ok, I marked both the www-dom one and spec-prod one was spam in the archives |
| 00:45 | <MikeSmith> | if anybody notices others, lemme know |
| 00:47 | <MikeSmith> | ah oops |
| 00:47 | <MikeSmith> | spec-prod one was from 66.53.221.33 also |
| 00:47 | <MikeSmith> | not 66.194.95.2 |
| 00:47 | <MikeSmith> | ah oops |
| 00:47 | <MikeSmith> | spec-prod one was from 66.53.221.33 also |
| 00:47 | <MikeSmith> | not 66.194.95.2 |
| 01:13 | <zewt> | except rel=nofollow wouldn't really make sense for mail archives |
| 01:14 | <zewt> | except rel=nofollow wouldn't really make sense for mail archives |
| 02:30 | <Hixie> | zewt: why not? they're not trusted |
| 02:30 | <Hixie> | zewt: why not? they're not trusted |
| 02:36 | <zewt> | too big a hammer; people linking to pages in mailing list conversations definitely should affect things like page ranking |
| 02:37 | <zewt> | i wonder if rel=nofollow affects link: searches on google; http://support.google.com/webmasters/bin/answer.py?hl=en&answer=96569 isn't really clear about that, but suggests they won't work, either |
| 02:37 | <zewt> | too big a hammer; people linking to pages in mailing list conversations definitely should affect things like page ranking |
| 02:38 | <Hixie> | i don't see how it's any different to a forum |
| 02:38 | <zewt> | i wonder if rel=nofollow affects link: searches on google; http://support.google.com/webmasters/bin/answer.py?hl=en&answer=96569 isn't really clear about that, but suggests they won't work, either |
| 02:39 | <zewt> | forums shouldn't use it, either |
| 02:39 | <zewt> | would be pretty bad if people linking to a webpage in discussions didn't "count" |
| 02:39 | <Hixie> | i don't see how it's any different to a forum |
| 02:39 | <zewt> | forums shouldn't use it, either |
| 02:40 | <zewt> | would be pretty bad if people linking to a webpage in discussions didn't "count" |
| 07:07 | <MikeSmith> | hsivonen: time for a new HTML parser release? |
| 07:07 | <MikeSmith> | it's been a year since the last release |
| 07:07 | <MikeSmith> | hsivonen: time for a new HTML parser release? |
| 07:08 | <MikeSmith> | it's been a year since the last release |
| 08:49 | <annevk> | you got to love how Microsoft first boasts on their blog how they are not shipping things prematurely and now are all like "we cannot change the Indexed DB... IMPOSSIBRU!!!!" which has shipped exactly nowhere unprefixed yet |
| 08:50 | <annevk> | such hypocrites |
| 08:50 | <annevk> | you got to love how Microsoft first boasts on their blog how they are not shipping things prematurely and now are all like "we cannot change the Indexed DB... IMPOSSIBRU!!!!" which has shipped exactly nowhere unprefixed yet |
| 08:50 | <annevk> | such hypocrites |
| 09:30 | <annevk> | maybe TC39 should read http://unicode.org/faq/utf_bom.html#utf32-4 |
| 09:30 | <annevk> | "Given that any industrial-strength text and internationalization support API has to be able to handle sequences of characters, it makes little difference whether the string is internally represented by a sequence of UTF-16 code units, or by a sequence of code-points ( = UTF-32 code units)." |
| 09:30 | <annevk> | maybe TC39 should read http://unicode.org/faq/utf_bom.html#utf32-4 |
| 09:30 | <annevk> | "Given that any industrial-strength text and internationalization support API has to be able to handle sequences of characters, it makes little difference whether the string is internally represented by a sequence of UTF-16 code units, or by a sequence of code-points ( = UTF-32 code units)." |
| 10:11 | <annevk> | I think http://www.reddit.com/r/circlejerk/ might be new favorite subreddit |
| 10:11 | <annevk> | I think http://www.reddit.com/r/circlejerk/ might be new favorite subreddit |
| 12:50 | <bga> | http://webintents.org/ |
| 12:50 | <bga> | http://webintents.org/ |
| 13:03 | <Velmont> | So... They mean the shim doesn't work in Opera? |
| 13:03 | <Velmont> | So... They mean the shim doesn't work in Opera? |
| 13:04 | <Velmont> | And I still don't like their angle. Making something entirely new instead of extending registerprotocolhandler. Can even use it as a backend, but still have a higher level API on top. |
| 13:04 | <Velmont> | And I still don't like their angle. Making something entirely new instead of extending registerprotocolhandler. Can even use it as a backend, but still have a higher level API on top. |
| 13:14 | <Ms2ger> | Velmont, "Googl" |
| 13:14 | <Ms2ger> | With an e, even |
| 13:14 | <Ms2ger> | Velmont, "Googl" |
| 13:14 | <Ms2ger> | With an e, even |
| 13:20 | <Velmont> | Hmmm. I keep pressing "specification" but it doesn't go anywhere. |
| 13:21 | <Velmont> | Thought I'd take a look at how hard it would be to change the underlying technology in it. |
| 13:21 | <Velmont> | Hmmm. I keep pressing "specification" but it doesn't go anywhere. |
| 13:21 | <Velmont> | Thought I'd take a look at how hard it would be to change the underlying technology in it. |
| 13:27 | <Velmont> | Meh, the examples work even worse in Firefox than Opera. Half baked, non-working stuff. |
| 13:27 | <Velmont> | Meh, the examples work even worse in Firefox than Opera. Half baked, non-working stuff. |
| 15:04 | <MikeSmith> | scott_gonzalez: so I now have something that I think will work for you guys |
| 15:04 | <MikeSmith> | still trying to figure out what would be the least kludgey way to do it |
| 15:04 | <MikeSmith> | scott_gonzalez: so I now have something that I think will work for you guys |
| 15:05 | <MikeSmith> | but it's doing as expected in my workspace at least |
| 15:05 | <MikeSmith> | still trying to figure out what would be the least kludgey way to do it |
| 15:05 | <MikeSmith> | but it's doing as expected in my workspace at least |
| 15:08 | <MikeSmith> | scott_gonzalez: anyway, should require not build but you'll need to have 4-5 particular jar files around |
| 15:08 | <MikeSmith> | scott_gonzalez: anyway, should require not build but you'll need to have 4-5 particular jar files around |
| 21:37 | <Ms2ger> | http://www.slashdot.org/article.pl?sid=12/03/10/2134253 |
| 21:37 | <Ms2ger> | http://www.slashdot.org/article.pl?sid=12/03/10/2134253 |
| 22:09 | <yuhong> | http://ln.hixie.ch/?start=1137740632&count=1 |
| 22:09 | <yuhong> | "I'm not even going to try to specify quirks mode parsing. Hopefully, by making the DOCTYPE short and memorable, it will encourage authors to use it more." |
| 22:09 | <yuhong> | http://ln.hixie.ch/?start=1137740632&count=1 |
| 22:09 | <yuhong> | "I'm not even going to try to specify quirks mode parsing. Hopefully, by making the DOCTYPE short and memorable, it will encourage authors to use it more." |
| 22:12 | <yuhong> | Two years before X-UA-Compatible was created. |
| 22:12 | <yuhong> | Two years before X-UA-Compatible was created. |