it is a good idea, however it is hard for ICANN to be able to say: this is a good plug-in and this is a bad one. We simply cannot check all applications and all plug-ins as there are too many of them around. In addition to the volume this is a grey-zone area for ICANN’s mandate.

However, if you have specific experience using some of these then you can start by adding the information on the wiki.

If you are merely talking about general warnings for users the this should not be related to IDNs only. Kieren, lets talk about this the week after next when im back in the office…there are many different channels in the ICANN community leading to end-users that I am sure would be available to help out further on this.

Tina

Will ponder how best to direct people.

Kieren

At the same time, ICANN should be cautioning new users about casually downloading plug-ins, patches or new applications to test IDNs. Let’s remind them to deal only with trusted websites and scan for viruses and malware. (let’s do that in multiple langauges and scripts, of course)

Otherwise, our “next billion” users could accidentally host the “next billion” bots capable of generating spam, phishing fraud, and denial-of-service attacks.

The 1-weeks stats will be correct. Sorry about the mistake and inconvenience.

Tina