Log in

No account? Create an account

Previous Entry | Next Entry

Jack has alerted me to a security issue with most browsers that support IDN. Whatever, I don't know what it's about either, but there's an easy fix. Here is a demonstration/test of the problem.

Today has been data cleaning, laughing at absurd pet names (Dippy Doodle!!##&^%^#$), and contemplating slowing the hell down, because last night I caused 5 people including myself to attend an event that is not scheduled until next week.

I also learned that I'm not the only person who is too emabrassed to publicly attempt a process that no one has instructed me in, i.e. grinding coffee AT the Trader Joe's. We are now the proud new owners of a coffee grinder. Now I just need to know: what is the best fair trade coffee?

Also it is time, due to financial considerations, to give up on the built-in shelves. I know what this means; it means we are going to have prefab stuff indefinitely. But I need to have shelves, and we need to not spend much money, so there you have it. Ikea, here we come...

I'm sorry Joe. :(


Feb. 10th, 2005 11:31 pm (UTC)
This IDN thing has been a major, major headache. The annoying thing about is that according to the letter of the specification, this is the correct behavior [1] - so some parties, like Opera, are making noises that their implementation is correct, it's the registrars problem, and that they're not going to fix it.

I'm pretty sure the Spoofstick cracks this nut now, and might be a bit easier to install than Jacks suggestion, which sadly disables IDN completely ( it does have some legit uses ). If you're using the I.E. IDN plugin, I definitely recommend installing it, because while Mozdev have patched this problem in trunk, I'm not sure if the I.E. 3rd party guys will.


[1] This seems to happen every time we uncover something which is 'spec compliant' but 'real world broken'.
Feb. 11th, 2005 03:53 am (UTC)
Thanks for the tip!