Mittwoch, 20. Februar 2008

USA suppressing foreign freedom of expression?

Scenario: A Swiss bank’s Cayman Islands branch has issues with content published by the website wikileaks.org. They take the issue to an American court. As the individuals behind the Wikileaks site are not American citizens and are not presently in the USA, nor is the servers located in USA, the court has no direct jurisdiction over the matter. Instead they order a third party, a compliant domain registrar, to purge the site from DNS records.


Let me come up with a simile: This is equivalent to a Swedish court deciding that because an American paper publishes something that a Norwegian company doesn’t like, it orders a Swedish postal company to redirect all mail going to the address of that American paper to be redirected to a storage box. And so all postal companies globally now redirects all mail that formerly went to that American address to this storage box.


That simile is weak not because it’s quite ridiculous, but because it’s way narrower than the actual issue - it only affects mail to the American paper, when the real issue is more analogous to replacing the building in which that paper is printed with an empty warehouse.


Wikileaks’s main server is in Sweden (abundantly mirrored elsewhere), individuals involved are non-Americans outside of the USA. This is clearly not a case covered by American jurisdiction. Still, an American court is able to pressure an American company into purging the address of this organisation from the DNS system, which has global effects. Thereby suppressing Swedish freedom of expression.


I don’t like it. Not one bit. The DNS system should not be susceptible to attacks from within one nation on entities outside of that nation’s borders. At least, something should prevent court decisions made in any single nation from having global effects. The internet is not owned by the USA, and American courts should not have jurisdiction over it.


Also see Global Integrity Commons: Internet Censorship: A Comparative Study


USA suppressing foreign freedom of expression?

Scenario: A Swiss bank’s Cayman Islands branch has issues with content published by the website wikileaks.org. They take the issue to an American court. As the individuals behind the Wikileaks site are not American citizens and are not presently in the USA, nor is the servers located in USA, the court has no direct jurisdiction over the matter. Instead they order a third party, a compliant domain registrar, to purge the site from DNS records.


Let me come up with a simile: This is equivalent to a Swedish court deciding that because an American paper publishes something that a Norwegian company doesn’t like, it orders a Swedish postal company to redirect all mail going to the address of that American paper to be redirected to a storage box. And so all postal companies globally now redirects all mail that formerly went to that American address to this storage box.


That simile is weak not because it’s quite ridiculous, but because it’s way narrower than the actual issue - it only affects mail to the American paper, when the real issue is more analogous to replacing the building in which that paper is printed with an empty warehouse.


Wikileaks’s main server is in Sweden (abundantly mirrored elsewhere), individuals involved are non-Americans outside of the USA. This is clearly not a case covered by American jurisdiction. Still, an American court is able to pressure an American company into purging the address of this organisation from the DNS system, which has global effects. Thereby suppressing Swedish freedom of expression.


I don’t like it. Not one bit. The DNS system should not be susceptible to attacks from within one nation on entities outside of that nation’s borders. At least, something should prevent court decisions made in any single nation from having global effects. The internet is not owned by the USA, and American courts should not have jurisdiction over it.


Also see Global Integrity Commons: Internet Censorship: A Comparative Study


USA suppressing foreign freedom of expression?

Scenario: A Swiss bank’s Cayman Islands branch has issues with content published by the website wikileaks.org. They take the issue to an American court. As the individuals behind the Wikileaks site are not American citizens and are not presently in the USA, nor is the servers located in USA, the court has no direct jurisdiction over the matter. Instead they order a third party, a compliant domain registrar, to purge the site from DNS records.


Let me come up with a simile: This is equivalent to a Swedish court deciding that because an American paper publishes something that a Norwegian company doesn’t like, it orders a Swedish postal company to redirect all mail going to the address of that American paper to be redirected to a storage box. And so all postal companies globally now redirects all mail that formerly went to that American address to this storage box.


That simile is weak not because it’s quite ridiculous, but because it’s way narrower than the actual issue - it only affects mail to the American paper, when the real issue is more analogous to replacing the building in which that paper is printed with an empty warehouse.


Wikileaks’s main server is in Sweden (abundantly mirrored elsewhere), individuals involved are non-Americans outside of the USA. This is clearly not a case covered by American jurisdiction. Still, an American court is able to pressure an American company into purging the address of this organisation from the DNS system, which has global effects. Thereby suppressing Swedish freedom of expression.


I don’t like it. Not one bit. The DNS system should not be susceptible to attacks from within one nation on entities outside of that nation’s borders. At least, something should prevent court decisions made in any single nation from having global effects. The internet is not owned by the USA, and American courts should not have jurisdiction over it.


Also see Global Integrity Commons: Internet Censorship: A Comparative Study


USA suppressing foreign freedom of expression?

Scenario: A Swiss bank’s Cayman Islands branch has issues with content published by the website wikileaks.org. They take the issue to an American court. As the individuals behind the Wikileaks site are not American citizens and are not presently in the USA, nor is the servers located in USA, the court has no direct jurisdiction over the matter. Instead they order a third party, a compliant domain registrar, to purge the site from DNS records.


Let me come up with a simile: This is equivalent to a Swedish court deciding that because an American paper publishes something that a Norwegian company doesn’t like, it orders a Swedish postal company to redirect all mail going to the address of that American paper to be redirected to a storage box. And so all postal companies globally now redirects all mail that formerly went to that American address to this storage box.


That simile is weak not because it’s quite ridiculous, but because it’s way narrower than the actual issue - it only affects mail to the American paper, when the real issue is more analogous to replacing the building in which that paper is printed with an empty warehouse.


Wikileaks’s main server is in Sweden (abundantly mirrored elsewhere), individuals involved are non-Americans outside of the USA. This is clearly not a case covered by American jurisdiction. Still, an American court is able to pressure an American company into purging the address of this organisation from the DNS system, which has global effects. Thereby suppressing Swedish freedom of expression.


I don’t like it. Not one bit. The DNS system should not be susceptible to attacks from within one nation on entities outside of that nation’s borders. At least, something should prevent court decisions made in any single nation from having global effects. The internet is not owned by the USA, and American courts should not have jurisdiction over it.


Also see Global Integrity Commons: Internet Censorship: A Comparative Study


USA suppressing foreign freedom of expression?

Scenario: A Swiss bank’s Cayman Islands branch has issues with content published by the website wikileaks.org. They take the issue to an American court. As the individuals behind the Wikileaks site are not American citizens and are not presently in the USA, nor is the servers located in USA, the court has no direct jurisdiction over the matter. Instead they order a third party, a compliant domain registrar, to purge the site from DNS records.


Let me come up with a simile: This is equivalent to a Swedish court deciding that because an American paper publishes something that a Norwegian company doesn’t like, it orders a Swedish postal company to redirect all mail going to the address of that American paper to be redirected to a storage box. And so all postal companies globally now redirects all mail that formerly went to that American address to this storage box.


That simile is weak not because it’s quite ridiculous, but because it’s way narrower than the actual issue - it only affects mail to the American paper, when the real issue is more analogous to replacing the building in which that paper is printed with an empty warehouse.


Wikileaks’s main server is in Sweden (abundantly mirrored elsewhere), individuals involved are non-Americans outside of the USA. This is clearly not a case covered by American jurisdiction. Still, an American court is able to pressure an American company into purging the address of this organisation from the DNS system, which has global effects. Thereby suppressing Swedish freedom of expression.


I don’t like it. Not one bit. The DNS system should not be susceptible to attacks from within one nation on entities outside of that nation’s borders. At least, something should prevent court decisions made in any single nation from having global effects. The internet is not owned by the USA, and American courts should not have jurisdiction over it.


Also see Global Integrity Commons: Internet Censorship: A Comparative Study


USA suppressing foreign freedom of expression?

Scenario: A Swiss bank’s Cayman Islands branch has issues with content published by the website wikileaks.org. They take the issue to an American court. As the individuals behind the Wikileaks site are not American citizens and are not presently in the USA, nor is the servers located in USA, the court has no direct jurisdiction over the matter. Instead they order a third party, a compliant domain registrar, to purge the site from DNS records.


Let me come up with a simile: This is equivalent to a Swedish court deciding that because an American paper publishes something that a Norwegian company doesn’t like, it orders a Swedish postal company to redirect all mail going to the address of that American paper to be redirected to a storage box. And so all postal companies globally now redirects all mail that formerly went to that American address to this storage box.


That simile is weak not because it’s quite ridiculous, but because it’s way narrower than the actual issue - it only affects mail to the American paper, when the real issue is more analogous to replacing the building in which that paper is printed with an empty warehouse.


Wikileaks’s main server is in Sweden (abundantly mirrored elsewhere), individuals involved are non-Americans outside of the USA. This is clearly not a case covered by American jurisdiction. Still, an American court is able to pressure an American company into purging the address of this organisation from the DNS system, which has global effects. Thereby suppressing Swedish freedom of expression.


I don’t like it. Not one bit. The DNS system should not be susceptible to attacks from within one nation on entities outside of that nation’s borders. At least, something should prevent court decisions made in any single nation from having global effects. The internet is not owned by the USA, and American courts should not have jurisdiction over it.


Also see Global Integrity Commons: Internet Censorship: A Comparative Study


USA suppressing foreign freedom of expression?

Scenario: A Swiss bank’s Cayman Islands branch has issues with content published by the website wikileaks.org. They take the issue to an American court. As the individuals behind the Wikileaks site are not American citizens and are not presently in the USA, nor is the servers located in USA, the court has no direct jurisdiction over the matter. Instead they order a third party, a compliant domain registrar, to purge the site from DNS records.


Let me come up with a simile: This is equivalent to a Swedish court deciding that because an American paper publishes something that a Norwegian company doesn’t like, it orders a Swedish postal company to redirect all mail going to the address of that American paper to be redirected to a storage box. And so all postal companies globally now redirects all mail that formerly went to that American address to this storage box.


That simile is weak not because it’s quite ridiculous, but because it’s way narrower than the actual issue - it only affects mail to the American paper, when the real issue is more analogous to replacing the building in which that paper is printed with an empty warehouse.


Wikileaks’s main server is in Sweden (abundantly mirrored elsewhere), individuals involved are non-Americans outside of the USA. This is clearly not a case covered by American jurisdiction. Still, an American court is able to pressure an American company into purging the address of this organisation from the DNS system, which has global effects. Thereby suppressing Swedish freedom of expression.


I don’t like it. Not one bit. The DNS system should not be susceptible to attacks from within one nation on entities outside of that nation’s borders. At least, something should prevent court decisions made in any single nation from having global effects. The internet is not owned by the USA, and American courts should not have jurisdiction over it.


Also see Global Integrity Commons: Internet Censorship: A Comparative Study


Mittwoch, 13. Februar 2008

ECMAScript 4 again

A new pre-release of the reference implementation has been released. Head on over to the ECMAScript - Downloads site to get it. What are the changes? Well, taken directly out of Graydon’s announcement message to the ES4-discuss mailing list:


This release covers the cumulative set of fixes, enhancements, and adjustments to track spec discussions since October. Full details can be found in the bug tracker, but the summary entry in the HISTORY file follows:



Newly supported constructs:



  • Super expressions

  • Like types

  • Wrappers (preliminary)

  • Slice expressions

  • __ES4__::Map.

  • __ES4__::Vector.

  • __ES4__::hashcode()

  • __ES4__::DecimalContext, new decimal pragma

  • uint32ops::*



Corrected behavior:



  • Overhaul type system to conform to “valleyscript” model

  • Strictness pragmas

  • Cyclic type term prevention

  • Type parameter scoping

  • Property enumeration order

  • Builtin prototype chains

  • Builtin constructors

  • Builtin conversions

  • Builtin non-magic wrapper types

  • Prototype property shadowing

  • Scope rules for let expressions

  • Arithmetic rules

  • Function self-name binding

  • Union types use “|” rather than “,”

  • Regexp character class bug

  • Hoisting bug

  • Property-enumerability bug

  • Nullability enforcement

  • REPL error handling






ECMAScript 4 again

A new pre-release of the reference implementation has been released. Head on over to the ECMAScript - Downloads site to get it. What are the changes? Well, taken directly out of Graydon’s announcement message to the ES4-discuss mailing list:


This release covers the cumulative set of fixes, enhancements, and adjustments to track spec discussions since October. Full details can be found in the bug tracker, but the summary entry in the HISTORY file follows:



Newly supported constructs:



  • Super expressions

  • Like types

  • Wrappers (preliminary)

  • Slice expressions

  • __ES4__::Map.

  • __ES4__::Vector.

  • __ES4__::hashcode()

  • __ES4__::DecimalContext, new decimal pragma

  • uint32ops::*



Corrected behavior:



  • Overhaul type system to conform to “valleyscript” model

  • Strictness pragmas

  • Cyclic type term prevention

  • Type parameter scoping

  • Property enumeration order

  • Builtin prototype chains

  • Builtin constructors

  • Builtin conversions

  • Builtin non-magic wrapper types

  • Prototype property shadowing

  • Scope rules for let expressions

  • Arithmetic rules

  • Function self-name binding

  • Union types use “|” rather than “,”

  • Regexp character class bug

  • Hoisting bug

  • Property-enumerability bug

  • Nullability enforcement

  • REPL error handling






ECMAScript 4 again

A new pre-release of the reference implementation has been released. Head on over to the ECMAScript - Downloads site to get it. What are the changes? Well, taken directly out of Graydon’s announcement message to the ES4-discuss mailing list:


This release covers the cumulative set of fixes, enhancements, and adjustments to track spec discussions since October. Full details can be found in the bug tracker, but the summary entry in the HISTORY file follows:



Newly supported constructs:



  • Super expressions

  • Like types

  • Wrappers (preliminary)

  • Slice expressions

  • __ES4__::Map.

  • __ES4__::Vector.

  • __ES4__::hashcode()

  • __ES4__::DecimalContext, new decimal pragma

  • uint32ops::*



Corrected behavior:



  • Overhaul type system to conform to “valleyscript” model

  • Strictness pragmas

  • Cyclic type term prevention

  • Type parameter scoping

  • Property enumeration order

  • Builtin prototype chains

  • Builtin constructors

  • Builtin conversions

  • Builtin non-magic wrapper types

  • Prototype property shadowing

  • Scope rules for let expressions

  • Arithmetic rules

  • Function self-name binding

  • Union types use “|” rather than “,”

  • Regexp character class bug

  • Hoisting bug

  • Property-enumerability bug

  • Nullability enforcement

  • REPL error handling






ECMAScript 4 again

A new pre-release of the reference implementation has been released. Head on over to the ECMAScript - Downloads site to get it. What are the changes? Well, taken directly out of Graydon’s announcement message to the ES4-discuss mailing list:


This release covers the cumulative set of fixes, enhancements, and adjustments to track spec discussions since October. Full details can be found in the bug tracker, but the summary entry in the HISTORY file follows:



Newly supported constructs:



  • Super expressions

  • Like types

  • Wrappers (preliminary)

  • Slice expressions

  • __ES4__::Map.

  • __ES4__::Vector.

  • __ES4__::hashcode()

  • __ES4__::DecimalContext, new decimal pragma

  • uint32ops::*



Corrected behavior:



  • Overhaul type system to conform to “valleyscript” model

  • Strictness pragmas

  • Cyclic type term prevention

  • Type parameter scoping

  • Property enumeration order

  • Builtin prototype chains

  • Builtin constructors

  • Builtin conversions

  • Builtin non-magic wrapper types

  • Prototype property shadowing

  • Scope rules for let expressions

  • Arithmetic rules

  • Function self-name binding

  • Union types use “|” rather than “,”

  • Regexp character class bug

  • Hoisting bug

  • Property-enumerability bug

  • Nullability enforcement

  • REPL error handling






ECMAScript 4 again

A new pre-release of the reference implementation has been released. Head on over to the ECMAScript - Downloads site to get it. What are the changes? Well, taken directly out of Graydon’s announcement message to the ES4-discuss mailing list:


This release covers the cumulative set of fixes, enhancements, and adjustments to track spec discussions since October. Full details can be found in the bug tracker, but the summary entry in the HISTORY file follows:



Newly supported constructs:



  • Super expressions

  • Like types

  • Wrappers (preliminary)

  • Slice expressions

  • __ES4__::Map.

  • __ES4__::Vector.

  • __ES4__::hashcode()

  • __ES4__::DecimalContext, new decimal pragma

  • uint32ops::*



Corrected behavior:



  • Overhaul type system to conform to “valleyscript” model

  • Strictness pragmas

  • Cyclic type term prevention

  • Type parameter scoping

  • Property enumeration order

  • Builtin prototype chains

  • Builtin constructors

  • Builtin conversions

  • Builtin non-magic wrapper types

  • Prototype property shadowing

  • Scope rules for let expressions

  • Arithmetic rules

  • Function self-name binding

  • Union types use “|” rather than “,”

  • Regexp character class bug

  • Hoisting bug

  • Property-enumerability bug

  • Nullability enforcement

  • REPL error handling






ECMAScript 4 again

A new pre-release of the reference implementation has been released. Head on over to the ECMAScript - Downloads site to get it. What are the changes? Well, taken directly out of Graydon’s announcement message to the ES4-discuss mailing list:


This release covers the cumulative set of fixes, enhancements, and adjustments to track spec discussions since October. Full details can be found in the bug tracker, but the summary entry in the HISTORY file follows:



Newly supported constructs:



  • Super expressions

  • Like types

  • Wrappers (preliminary)

  • Slice expressions

  • __ES4__::Map.

  • __ES4__::Vector.

  • __ES4__::hashcode()

  • __ES4__::DecimalContext, new decimal pragma

  • uint32ops::*



Corrected behavior:



  • Overhaul type system to conform to “valleyscript” model

  • Strictness pragmas

  • Cyclic type term prevention

  • Type parameter scoping

  • Property enumeration order

  • Builtin prototype chains

  • Builtin constructors

  • Builtin conversions

  • Builtin non-magic wrapper types

  • Prototype property shadowing

  • Scope rules for let expressions

  • Arithmetic rules

  • Function self-name binding

  • Union types use “|” rather than “,”

  • Regexp character class bug

  • Hoisting bug

  • Property-enumerability bug

  • Nullability enforcement

  • REPL error handling






ECMAScript 4 again

A new pre-release of the reference implementation has been released. Head on over to the ECMAScript - Downloads site to get it. What are the changes? Well, taken directly out of Graydon’s announcement message to the ES4-discuss mailing list:


This release covers the cumulative set of fixes, enhancements, and adjustments to track spec discussions since October. Full details can be found in the bug tracker, but the summary entry in the HISTORY file follows:



Newly supported constructs:



  • Super expressions

  • Like types

  • Wrappers (preliminary)

  • Slice expressions

  • __ES4__::Map.

  • __ES4__::Vector.

  • __ES4__::hashcode()

  • __ES4__::DecimalContext, new decimal pragma

  • uint32ops::*



Corrected behavior:



  • Overhaul type system to conform to “valleyscript” model

  • Strictness pragmas

  • Cyclic type term prevention

  • Type parameter scoping

  • Property enumeration order

  • Builtin prototype chains

  • Builtin constructors

  • Builtin conversions

  • Builtin non-magic wrapper types

  • Prototype property shadowing

  • Scope rules for let expressions

  • Arithmetic rules

  • Function self-name binding

  • Union types use “|” rather than “,”

  • Regexp character class bug

  • Hoisting bug

  • Property-enumerability bug

  • Nullability enforcement

  • REPL error handling