Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
The alert provides a web form to write to your congress person. Please do that. And please put the alert up elsewhere, so that other people can help too.
I'm in Washington DC working on this today, and your support will help.
I'd really appreciate it if you'd create a login on the site and submit articles. Especially original work, which hasn't always been well recieved on Slashdot - they seem to prefer linking to other people's coverage. RDF and RSS are available at http://technocrat.net/rdf and http://technocrat.net/rss, so you can keep track of articles from elsewhere.
Yes, it's tooting my own horn. So what? I seldom get to.
by Damian Yerrick
I got the nick "yerricde" in late 1999 when my former school created my user accounts under a nick based on my legal name (Yerrick, Damian E.) It seems that too many people have seen an extra 'i' (*yerricide) in my nick. To prevent further confusion, I decided to phase out that nick starting in early 2002. I wrote a program in the Scheme language to generate a nick that's not so easy to misread, and the result was "tepples". You may recognize me from NewsForge, gbadev, DDRei, or nesdev.
I'm a quick reader. I'm also a quick typist. And I've held this Slashdot account for nearly four years. Though I have posted nearly 10,000 comments to Slashdot stories, claiming that I "have no life" would be thoroughly misleading. But some trolls seem to imply this, having started some sort of countdown to 10,000 comments by user "yerricde". I'd as soon shed this nick and ho up a new Slashdot account in the 720000's rather than let them win. I might even subscribe this time.
Anita and I will be travelling for the next few days. First down to visit my parents on the Oregon coast, then back up to Portland for OryCon over the weekend. I will try to get the rest of the 'best of' posts up when I can. (I have posted tons more verbage than seems reasonable in the last year, so there is lots to go through.)
Cue music: 'On the Road Again'
Eric Raymond's blog 'Armed and Dangerous' has moved here. Which may be a good thing, he is certainly posting more. His latest rant tears a new asshole out of the ". . . dope-smoking ponytailed dimwits . .
Such have been the bane of my existance when doing websites as well. Nothing sucks more than getting an email saying "Do the page exactly like this." with a 3 mb graphic created in photoshop attached.
P.S. I cut off my ponytail more than a month ago...
Well I know what RSS is of course, but you might not. And I could tell you, except Mark Pilgrim does a better job of answering the question 'What is RSS?' than I could. So you should read that.
But why am I answering a question you haven't asked yet? Well, because even here on
After the Columbia disaster I was fairly upset with the regular media reporting and with NASA's lack of open discussion. However NASA did release some telemetry information gathered right before the shuttle breakup. That information seemed to contain some clues as to exactly what had happened, but it was pretty hard to understand. Being a visual thinker I needed a more graphical view of the sensor results over time, so I created my own animation of the data.
Veiwing my animation and a picture taken of the shuttle right before the breakup led me to the conclusion that one of the leading edge carbon/carbon shielding blocks had failed, just outboard of the wheel well. For whatever it is worth, I turned out to be 100% correct!
However being right did not make me feel good. Instead I was irritated on several levels. First off, I was an amateur using those little bits of information openly released to come by my findings, while NASA engineers with access to even more information were silenced -- even after the 'official' findings were released. Something that took another four months. Certainly they arrived at the same conclusion long before I did; why weren't they alowed to speak and why did it take so long?
Furthermore none of the various news sources, any of whom could have done the same thing I did, paid any attention to this data at all. Yet another case of someone in the blogosphere getting it right while the media yammers about inconsequentials. Oh well. And it didn't even lead to fifteen minutes of fame for me. Probably a good thing...
- Columbia Disaster
- What happened to Columbia? An amateur analyzes the data (Initial release of the animation, February 9th, 2003)
- More indications my Columbia theory is correct (April 3rd, 2003)
- I called it on the Columbia disaster! (The CAB releases their findings, corroborating my own on June 25th, 2003)
According to Richard C. Hoagland NASA may have accidently set off a nuclear explosion on Jupiter when they sent the Galileo probe plummeting into its depths.
A fascinating idea, and the background information is very interesting on its own. However Hoagland's tendancy towards conspiracy theories makes him an unreliable source. In so many ways...
One year ago today I posted my first
Along the way I gathered up a few readers (yourself for an instance) and, hopefully, you have found your time here worthwhile. Although I probably could have boosted my readership by making this journal more of a soap opera that just isn't what I am about. So I am proud to think that you read me for content and (hopefully) quality of prose instead of for titillation. I do know that I intend to continue, although it is certain that I will move off of
Nonetheless I am grateful to
Anyway, to celebrate the one year anniversery of this journal (and maybe to get you to read stuff you might have missed) I am going to post some 'best of' entries over the next couple of days. These will contain links to those entries from the past year that I am most proud of, organized by subject. Enjoy!
Update: Best of: The Columbia Disaster links to posts where I analyze the data from the breakup of the shuttle and get the right answer months before the official findings.
I am driving one handed while I fumble for my cell phone. Quick glance, select the number, press 'Call'. Put phone to my ear. It rings.
"Anita, it's me. I am driving down Pine and guess what I just saw in the sky?"
"What? Oh, the Concorde. Very cool! It was supposed to come in at 3:00."
"Ya, I think it was on final approach to Boeing Field."
"Well, now you have something to blog."
Yes, I suppose I do. But just what do I blog? Do I talk about how this particular Concorde was on its final flight because British Airways had given it as a permanent loan to Seattle's Museum of Flight? How cool it is that I will get to walk through it just as soon as the exhibit is ready?
Or do I talk about the mix of feelings that swept through me as I watched that bright arrow slip through the Seattle skyline as it came in for what may well be its last landing? The joy of being in the exactly right place at exactly the right time to get that amazing view? And the sorrow that I felt knowing that an era which never really came to be was somehow coming to an end? How this was yet another proof that the future had failed to deliver on the promises Heinlein, Clarke and Asimov had made to me when I was a child? How truly bittersweet that moment was?
I don't know what to say. I really don't...