| Blog | # of Comments |
|---|---|
| The Unofficial Apple Weblog (TUAW) | 118 Comments |
| Engadget | 134 Comments |
| Download Squad | 22 Comments |
| Engadget HD | 3 Comments |
| Joystiq Playstation | 1 Comment |
| Joystiq Nintendo | 1 Comment |
| WoW | 10 Comments |
| Engadget Mobile | 3 Comments |

Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
paypaǀ.com ("l" replaced with U+01C0)
googǀe.com ("l" replaced with U+01C0)
The problem is that when you suddenly support the entire world's alphabets, there is a lot of visual overlap and subtleties. Browsers are going to have to get very smart about this to make the distinction visible to end users. Here is a sample of characters that visually resemble their ascii counterparts with enough to fool people. Any domain name containing one of these letters is potentially vulnerable (and this is just one quick casual pass through a small subset of unicode):
ɑаʙϲԁеʜјιĸǀחоƨтρυⱱԝ