[82446] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Non-English Domain Names Likely Delayed

daemon@ATHENA.MIT.EDU (Neil Harris)
Mon Jul 18 18:14:32 2005

Date: Mon, 18 Jul 2005 23:14:03 +0100
From: Neil Harris <neil@tonal.clara.co.uk>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: Brad Knowles <brad@stop.mail-abuse.org>, NANOG <nanog@merit.edu>
In-Reply-To: <1BC24526-2C63-41EE-8556-C833D310CD63@muada.com>
Errors-To: owner-nanog@merit.edu


Iljitsch van Beijnum wrote:

>
> On 18-jul-2005, at 22:49, Brad Knowles wrote:
>
...snip...

>>     If you're not a programmer with direct commit access to Mozilla  
>> and Opera, just how exactly do you expect to have any control over  
>> this process?
>
>
> Hopefully they make this stuff user configurable. This stuff is a lot  
> like SSL certificates that come with browsers. You can manage those  
> yourself if you jump through the hoops.
>
> It's not so much that many people will actually do this, but the fact  
> that users can vote with their feet keeps the people in control down  
> the chain honest. (Well, more honest than they would be otherwise, at  
> least.)
>
> You can't have an effictive dictatorship when people are free to move  
> to the next country.
>
>
I can't speak for Opera's implementation, but the Mozilla folks have 
made their implementation eminently configurable, using the standard 
configuration variable mechanism, with one variable for each domain to 
be whitelisted.

That means it can be altered by any of:
* editing the human-readable configuration files
* using the interactive about:config interface to edit the files from 
within the browser
* loading a third-party browser extension

-- Neil



home help back first fref pref prev next nref lref last post