Featured Articles
- Gottfried Leibniz: Shoulders of Giants
- The Art of Noise
- Jeremy Allison gets a name check from Fidel Castro
- That Which Survives
- The twenty-four hour loaf
- Orbiting Debian: Bdale Garbie
- Diving for Perls: The poetry of programming
- Hacking after midnight
- Why should we not tag our politicians?
- Always Crashing
- The Viral Clause
- Tivo, phone home...
- Machine smashing ain't what it used to be
- Requiem for Bell Labs, Unit 1127
- Shakespeare, think tanks, Linux, Atlantis & the AdTI
- Vista - The Tipping Point
- The terminal man & the semantic web
- Benjamin Franklin, Copyright Pirate
- The Executable's Song
- A Free Software Odyssey
- DNA: The Software of Life?
- Let Them Eat Megabytes
- Linux in the Special Effects Industry
- Roll Your Own Hardware
- The land of the Patent Trolls
- Hackers of Ancient Greece
- John Cage and the Copyright on Silence
- The Magician of Budapest
- The Revolution will be Plagiarised
- Against Nature - Viral Computing
- Programming as an Aesthetic Experience
- John Clare's enclosure - a tale of copyright law
- Powerpoint: A Pig through the Python

Siberian explosion
I would take the supposed sabotage of the gas pipeline story with a large grain of salt. There isn't a shred of evidence for it, aside from the reminisces of a couple of retired spies decades after the supposed event, embroidered to spice up their autobiographies.
These comments from a Slashdot post on the subject cover many points:
http://it.slashdot.org/comments.pl?sid=95184&cid=8160185
"The fact still remains that there was simply no component available in those days that was complex enough for it to be practical to hide a trojan in"
Not to mention, if the Russians had suspected it was sabotage, they could easily have retaliated by blowing up any number of things in the US.