Firefox 3

[alphamale]

Firefox 3, or codename Gran Paradiso has appeared on Mozilla's FTP site.

you can download and play with an Alpha version here: http://releases.mozilla.org/pub/mozi...1/win32/en-US/

the bad news is, idn's in the address bar still display punycode

[Rubber Duck]

I am still trying to work out what was different between 1.5 and 2.0 if anything and that took forever to release!

[alphamale]

actually I am little more forgiving of Mozilla.

Yes they do have a stupid opt-in process for IDN's resolving to Unicode; but it is up to the registries themselves to opt-in.

so far most registries have opted in except Verisign, which of course is why our .com's/.net's show punycode.

so, yes Mozilla your process sucks, but Verisign, pull your finger out - the buck stops with you.

[Rubber Duck]

Originally Posted by Alphamale

actually I am little more forgiving of Mozilla.

Yes they do have a stupid opt-in process for IDN's resolving to Unicode; but it is up to the registries themselves to opt-in.

so far most registries have opted in except Verisign, which of course is why our .com's/.net's show punycode.

so, yes Mozilla your process sucks, but Verisign, pull your finger out - the buck stops with you.

Sorry, but your absolutely wrong on this. Mozilla is trying to get Verisign to comply with its policies, when the only body with authority to form policy in this area is ICANN. Verisign is right in totally ingoring them.

The main reason that dot com and dot net are blocked is that with them there will be little traffic, certainly nothing that Americans are concerned about. MS have developed an effective anti-phishing mechanism. Mozilla is like the emporer in his new clothes, but whilst dot com is shackled in this way they can claim to be stopping phishing. What they don't state is they are also stopping any traffic that matters.

[alphamale]

Yes, and the fact that it is so benile just indicates to me that there is a wider agenda here. I am not even convinced that all these other registeries actually did something.

The bottom line is that Mozilla is trying to duck any responsibility they might have regarding phishing. Microsoft have done much more than anyone could ever have expected. Mozilla have done Zilch. Mozilla are trying to blame Verisign, when infact Verisign have followed ICANN every inch of the way.

Originally Posted by Rubber Duck

Sorry, but your absolutely wrong on this. Mozilla is trying to get Verisign to comply with its policies, when the only body with authority to form policy in this area is ICANN. Verisign is right in totally ingoring them.

The main reason that dot com and dot net are blocked is that with them there will be little traffic, certainly nothing that Americans are concerned about. MS have developed an effective anti-phishing mechanism. Mozilla is like the emporer in his new clothes, but whilst dot com is shackled in this way they can claim to be stopping phishing. What they don't state is they are also stopping any traffic that matters.

I'm not so sure things are as black and white as that.

Mozilla ask that registries have an anti-phishing policy. Now you'd imagine this to be a war-and-peace type document; well the last one i saw (and I can't remember which registry it was from) - looked like it was compiled on the back of a fag packet.

If verisign were serious about IDN, they only need fedex a post-it note with their "policy" on it to Mozilla.

other registries have. Even .JP, and Japanese don't use Firefox, and are the sleeping giants in the IDN world!

sorry - there are more than 1 fingers of blame being pointed, and not just at ICANNtmakeadecision