It's a bird! It's a plane! It's SuperOreo!
This is without a doubt one of the most horrifying pictures my friends have ever taken. Worse even than the rubber water balloon slingshot turned G-string picture or the surveyor's tape photo.
Warning: Not an office-safe photo, nor suitable for viewing by children. Possibly not even suitable for viewing by adults.
Pardon me while I go scrape the image from my brain and gouge out my eyeballs
This Flash cartoon was sent to me by my wife. I thought it was pretty funny.
Warning: Language is not appropriate for young or sensitive ears.
Sadly, there will be no more Friday Fives. The maintaner is calling it quits. I suppose when something stops being fun for you, you might as well stop doing it. I hadn't been doing them for very long, but enjoyed the ones that I did do. Thanks for the fun, FF.
From the Friday Five maintainer
May 06, 2004This is the end of the Friday Five. I know most of you have seen this coming and I appreciate you humoring me. I haven't enjoyed it for some time now and because of that I can no longer justify the bandwidth. I'm not going to give it away or sell it or bring anyone on to help; Two-and-a-half years is a good run. Let's let it go.
Thank you to everyone who has participated over the past 2+ years, for taking this silly little idea and running with it. Thanks again to the donators for their generosity and thoughtfulness, and those of you who have emailed me notes of support and encouragement over the last few months.
The notify list will remain as-is, just in case. The archives will remain down since that's where most of the bandwidth suck has been. Globe of Blogs is not going anywhere, so get your blog listed if you haven't already.
This script might come in handy some day. There are always posts on the MT support forum about how someone's lost their database, hadn't made a backup and only have the archive HTML files generated by MT to restore from. And I'm always forgetting what search terms I used to find the original post.
It won't restore everything. You still need to rebuild your templates and modules. Not sure about the comments, but at least you can recover your entries. Still, it's no substitute for having a good database backup or SQL dump of your MT database.
Don't thank me, thank Jason. He wrote it.
#!/usr/bin/perl
use Date::Manip;
# mtfix.pl - parse HTML files to import into Movable Type
# usage: mtfix.pl *html > import.mt
# Note: you _will_ need to adjust the regex
while (<>) { # for each file on the command line
# read in entire file to $content, line feeds and all
# using slurp mode
{ local $/; $content = <>;}
# locate the fields we need using regex
# some matches may include newlines
($author) =($content =~ m|<div class="posted">\s+(.+?)\s+/|s);
($title) = ($content =~ m|<span class="title">(.+)</span>|);
($text) = ($content =~ m|<p>(.+)<a name="more">|s);
($more) = ($content =~ m|<a name="more">(.+)<span class="posted">|s);
($date) = ($content =~ m|<div class="date">(.+)</div>|);
($time) = ($content =~ m|Posted\sat\s(.+)<br />|);
# Read in all the comments as one big block of text
($comments) = ($content =~ m|</a>Comments</div>\n(.+)<div class="comments-head">|s);
# Break up each comment into it's own element in an array
@comm = split (/<\/div>\n/, $comments);
# convert the date to MM/DD/YYYY hh:mm:ss
$datetime = "$date $time";
$parsed = ParseDate($datetime);
$datetime = UnixDate($parsed,"%m/%d/%Y %H:%M:%S");
# Strip out the paragraph tags, MT will add them later anyways.
$text =~ s|\<p\>||g;
$text =~ s|\</p\>||g;
$more =~ s|\<p\>||g;
$more =~ s|\</p\>||g;
# printout the fields in the proper format
print "AUTHOR: $author\n";
print "TITLE: $title\n";
print "DATE: $datetime\n";
print "-----\n";
print "BODY:\n$text\n";
print "-----\n";
print "EXTENDED BODY:\n$more\n";
foreach (@comm) { # For every comment in our aray, printout the necessary formating.
if (length $_ > 7) { # this is here to ignore the last comment record.
($CText) = ($_ =~ m|<div class="comments-body">\n(.+)\n\<span|s);
($CDate) = ($_ =~ m|</a>\son\s(.+)</span>|);
($Ctemp) = ($_ =~ m|Posted\sby:\s(.+)\/a\>|);
($CAuthor) = ($Ctemp =~ m|\>(.+)\<|);
($CURL) = ($Ctemp =~ m|href=\"(.+)\"|);
$CText =~ s|\<p\>||g;
$CText =~ s|\</p\>||g;
$parsed = ParseDate($CDate);
$CDate = UnixDate($parsed,"%m/%d/%Y %H:%M:%S");
print "-----\n";
print "COMMENT:\n";
print "AUTHOR: $CAuthor\n";
print "URL: $CURL\n";
print "DATE: $CDate\n";
print "$CText\n\n";
}
}
print "--------\n";
}A news article titled "Patients, physicians unaware of CT radiation exposure" in Radiology 2004;231:393-398 and posted at Aunt Minnie talks about just how much patients and physicians don't know about radiation exposures from CT.
The article raises a some interesting points about the need to educate health professionals about radiation. About the only radiology education most physicians receive is a 3 or 4 month rotation through radiology where they learn what it is they're looking at when looking at an x-ray. Even some radiologists don't know as much about radiation as you might think. The trouble is, squeezing more education into the curriculum is difficult at best.
Yes, radiation exposures from CT are significantly higher than regular radiographic exposures. Yes, there might be an increase in the risk of getting cancer. It's a small risk but one that is dwarfed by risks from other activities such as smoking or environmental exposure to chemical carcinogens. Radiation can be bad for you, but saves lives when used properly.
Ultimately, when it comes to any diagnostic imaging involving radiation, it comes down to a risk versus benefit thing. This is one of the things I try to emphasize to residents when I'm teaching them. Does the benefit of diagnosing an immediate problem in the patient outweigh the small increased long term cancer risk? Will the exam provide significantly more information useful for treatment than another exam that uses less or now radiation?
For the past 7 years I've been involved in teaching radiology residents all about the physics of medical imaging. I teach them (try to anyway) about radiation, how it interacts with matter, the different imaging modalities and how they work and generate images, radiation safety and biology. It's part of the board exams they need to pass. But I don't teach them because they have to pass the board exam. I teach them because down the road, they will be the "radiation experts" in whatever community they end up working in. They're the ones that people expect to know about the risks and benefits of getting radiation. They're the ones that people will go to for answers.
And my education efforts go beyond the classroom as well. Dose/exposure charts for all the equipment I survey are generated and distributed for posting so that people can see (if they care to look) what kinds of exposures the machine produces. I probably need to advertise this a little more though.
It's one of the activities I enjoy about my job.
Abstract:
PURPOSE: To determine the awareness level concerning radiation dose and possible risks associated with computed tomographic (CT) scans among patients, emergency department (ED) physicians, and radiologists.MATERIALS AND METHODS: Adult patients seen in the ED of a U.S. academic medical center during a 2-week period with mild to moderate abdominopelvic or flank pain and who underwent CT were surveyed after acquisition of the CT scan. Patients were asked whether or not they were informed about the risks, benefits, and radiation dose of the CT scan and if they believed that the scan increased their lifetime cancer risk. Patients were also asked to estimate the radiation dose for the CT scan compared with that for one chest radiograph. ED physicians who requested CT scans and radiologists who reviewed the CT scans were surveyed with similar questions and an additional question regarding the number of years in practice. The 2 test of independence was used to compare the three respondent groups regarding perceived increased cancer risk from one abdominopelvic CT scan.
RESULTS: Seven percent (five of 76) of patients reported that they were told about risks and benefits of their CT scan, while 22% (10 of 45) of ED physicians reported that they had provided such information. Forty-seven percent (18 of 38) of radiologists believed that there was increased cancer risk, whereas only 9% (four of 45) of ED physicians and 3% (two of 76) of patients believed that there was increased risk (22 = 41.45, P < .001). All patients and most ED physicians and radiologists were unable to accurately estimate the dose for one CT scan compared with that for one chest radiograph.
CONCLUSION: Patients are not given information about the risks, benefits, and radiation dose for a CT scan. Patients, ED physicians, and radiologists alike are unable to provide accurate estimates of CT doses regardless of their experience level.
© RSNA, 2004
Oh goody, the problem I was having building PHP 5.0 RC2 seems to have been fixed. I can go back to experimenting again.
FIX: Solaris compile failure.Daniel Fahlgren reported that following Wez Furlong's latest changes to proc_open(), PHP will no longer build on Solaris. Daniel had a quick fix for this, but Wez foresaw implications for other platforms in his workaround, and suggested areas where the Solaris build problem might be genuinely resolved. Daniel took this on board and came up with a patch that was acceptable to all, which now happily lives in the PHP source tree. This will be included in PHP 5.0.0.
I get to be a beta tester for MT3! I won't be converting over right away though. I thought I'd set up a duplicate database and test the beta using that so that I can iron out what changes I'll need to make to my templates. So for a little while, I'll be running parallel weblogs.
Upgrading the MT database was pretty simple. Had everything up and running in a matter of a few minutes, although I haven't rebuilt an of my weblogs yet. I've recently run into few issues with plugins that I'm trying to sort out. After I get those resolved, I'll start messing around with MT3.
Looking forward to this.
We now have one of these, a Sony TJ37. The wife decided she just couldn't wait any longer and decided she needed to have one of these. And since she wanted to listen to MP3s, we needed to get a Memory Stick. Of course that also meant we needed to get a Memory Stick reader for the computer. I decided on one of those multiformat memory card readers that reads CF I/II, SM, SD, MS, Microdrive and several others. I was trying to avoid this Flash media bloat, but now it's unavoidable. My digital camera uses SM, my PDA uses SD, and now her PDA uses MS. All small little bits ot try and keep track of.
So now, several hundred dollars later my wife has a PDA again, and she can go back to organizing her life again.
It's actually a pretty nice little unit, although I think Sony could have made it more attractive going with a Virtual Grafitti area (DIA). MP3s are stored and played off the MS card, and pictures can be stored either to RAM or MS card. It even comes with a little strap that you can use to hang onto it with. Put your hand through the strap, and no worries about accidentally dropping the thing. Stylus leaves a lot to be desired though. It's pretty thin, and I can't imagine using it to write for any length of time.
Navigating with the jog roller is pretty easy, although the buttons can be a little tough to press. They're small and nearly flush with the surface, so if you have big fat thumbs or fingers, pressing them might be a bit of a challenge.
The pictures it takes are fairly decent quality. Not great, but acceptable for quick snapshots. Max picture size is 640x480. If I can get it away from her for long enough, I'll play with it a bit and maybe post a few pictures.
I think this is what we need to replace our finicky StorageTek LT700 tape library with.
Found via Jeremy Wright
Switched the weblog over to a duplicate copy of my weblog database. After some modifications to the templates, the weblog is now running under MT 3.0B4. Not much has changed as far as the look of the weblog. There are some significant UI changes on the back end though. Looking pretty good MT. Not sure if commenting works though. Registered for Typekey and pasted the Typekey token into the proper section of Weblog Config. When I try to sign in and comment though, I get told that
The site you're trying to comment on has not signed up for this feature. Please inform the site owner.
I'll need to mess around some more to figure it out. In the meantime, commenting seems to work. They'll go into an approval queue and won't show up until I get around to checking the queue and approving or dumping any comments as I see fit.
Ok, thanks to this bug report, entering the URL to mt.cgi rather than the weblog URL seems to allow Typekey signins.
However, now I get a complaint that a user name and email need to be provided when a comment is submitted by a Typekey user. I may have some template and/or cookie issues left to resolve. Time to go digging into the default MT3 templates and have a look.
Ok, so the MT 3.0 Developer's Edition has just been announced.
Quite frankly, I'm not sure whether to be happy or disappointed about the new release and pricing.
From what I've seen playing with the beta, MT3 is pretty cool. Significantly faster than 2.6 especially when it comes to rebuilding. Good backward compatibility with older plugins, although I don't use too many of them. Better comment and trackback editing and handling.
There are the license changes. I haven't read through them yet, but from what I see it looks like it'll be more friendly for web developers and ISPs who want to offer MT to their clients.
Then there's the money aspect. MT's a great product, but honestly, I'm not at all sure it's worth $100 for a personal license that only gives you 5 weblogs and 3 authors. $40 or $50 I wouldn't object about. But I think $100 is a little steep. MT would do well to reconsider their pricing model so that it's a little more friendly to the power user needing a personal license.
Mena Trott writes
Additionally, as promised, donors who have ever contributed $20 or more to Movable Type will be able to apply their full donation to this version. For many who donated, the difference after applying their donation will be a nominal fee.Ok, I have to take issue with that statement. Yes, I made a $20 donation shortly after I started using MT 2.6. But I'd hardly call $50 (discount price minus donation) a nominal fee. It's anything but that. And you still end up paying the same price in the end.
Sure, there's the stripped down free version, but you only get one author and up to 3 weblogs with it. And a long list of No's and features taken away from the 2.x versions:
Notable license items with the free edition
"Author" means one individual with a unique login name generated by the Software via the "Add/Edit Weblog Authors" function of the Software. The sharing of an individual login name for more than one person is prohibited.
Making Copies You may install the Software on only one (1) computer or server having a single CPU. You may make one (1) copy of the Software in any machine readable form solely for back-up purposes, provided you reproduce the Software in its original form and with all proprietary notices on the back-up copy.
So I guess what I'm saying in short is
Wow, a lot of bitterness, griping and bashing going on with the release of MT 3.0D.
There are a lot of angry people out there ranting about SixApart's (SA) new licensing scheme and pricing for MT3.0. Some of it I think goes a little over the line, but the majority of it seems to question the wisdom of SA's actions.
Personally, I think if they made the pricing scheme a little more reasonable (ok, a lot more reasonable) and simpler, it would go a long way to making people feel better. However, I think it's going to make a lot of people abandon MT as a weblogging platform.
In the meantime, I downloaded and set up the free version of MT and pointed it at my existing database. It unpacks itself as MT-3.0D-full-personal-en_us and as far as I can tell so far, any user/weblog restrictions seem to be on the honour system. In fact I made this entry using the free version using a database with 5 authors and 6 weblogs. No complaints either when I created a 7th test weblog.
So, SA people, if you are listening (if anybody is listening), I think MT3.0 is great. I have no problem with paying for a Personal license for MT. I just think your pricing scheme needs to be changed to make it more affordable. Drop the cost of the Personal Edition license by half and you'll have another paying customer.
At long last, almost 3 years after the initial purchase, our final gamma camera has been delivered and installed. Joining our department is a new Philips/Adac Argus Epic single head gamma camera which will do a good portion of our routine and planar imaging, particularly for patients coming down in hospital beds.
Tomorrow I should be able to get in and do the acceptance testing on the unit. Looking forward to it. It's been a while since I've done anything on an Argus. Should be pretty easy this time. Only two sets of collimators and one head to do.
Ok, looks like bug report 1065 and 888 cover my problem with Typekey authenticated commenting. Now to read through them and see if I can figure out what's going on.
It's the second day since the release of MT3.0D, and the griping, whining and bitterness continues. Over 350 trackbacks to Mena Trott's announcement. So far, not a peep out of 6A since the announcement. I hope they've got good shields to deflect some of the hostility being directed at them.
To the 6A folks:
Wait a little bit for some of the hubbub to die down, but don't wait too long. Plenty of users are already frustrated with 6A about the lack of communication over MT. Give your users a well thought out response and any plans on addressing some of your users' concerns. Drop the prices on your PE licenses. Show us you're listening and want us to keep using your excellent product. I don't mind paying. Lots of MT users don't mind paying. You're just asking us to pay too much.
3 days ago, I was invited to join the beta testing program for MT3.0. Downloaded and installed 3.0b4 the next day. The day after, I learned that MT3.0D was released. Now, I'm not a developer, but if I were, I wouldn't be inviting more beta testers to test a product 2 days before it's released.
I've spent many more hours than I probably should have reading posts, weblog entries and comments about people's feelings on the matter. One item in particular from Mena's post caught my eye.
We would recommend that, if you're not the type of person who likes to tinker with Movable Type or would require a installation, you hold off until the general release.
So, does that mean that MT3.0D is intended primarily for MT plugin developers? Is there going to be another release, perhaps with different license conditions for regular users, or a different feature set?
Since there doesn't appear to be any hardcoded enforcement of user/weblog limits with the free edition (I've not dug into the source code to confirm this though), 6A is trusting the MT community to follow the license restrictions on their own.
We're big on honor at Six Apart. We haven't built in any nagware for license violations or phone home mechanisms. We trust our users' good judgment and intentions. We intend to use our good judgment in being flexible about enforcing these limits.
In that, I think the free edition has become something of a shareware product, which is not necessarily a bad thing. Use it, if you like it, then pay for it. Problem is, I think they're just asking us to pay too much for it.
Update: The hubbub has even reached Slashdot.org now!
Although not in any way an official statement from SixApart, Jay Allen offers some thoughts and insights on the release of MT3.0D. And some very good thoughts too. Good words, Jay.
Plenty already logged to the blogoverse about 6A's clarifications to the MT 3.0D release. There still continues to be some vitriol expressed by people who insist on remaining offended by 6A's release and license changes though. Even a troll has emerged to muddy things up and do all the nasty things trolls do.
6A's clarifications on the licensing terms and definitions as well as changes to the number of allowed users/weblogs does make things easier, and I think goes a long way to placating the majority of people. Now what I'd like to see is some statement about where 3.0D fits in with what 6A has in store.
3.0D is clearly a developer's release intended primarily for plugin developers to create new plugins and rework existing plugins to fit into the new framework.
It will be available to everyone, not just developers; we're calling it a Developer Release to emphasize the fact that 3.0 itself is not a feature release in the traditional sense. With this release we hope that the developer community will implement some great extensions for 3.0.Since many of Six Apart's employees are Apple fanboys/girls, we make the analogy to the first releases of OS X: the first releases did not offer that many new features themselves, only a more stable and robust platform for developers to build upon.
This clearly implies that unless you want to be active in developing and testing plugins, there's no need to jump in and upgrade. I think a lot of people missed this part and focused primarily on the licensing issues (which I think still could use some reworking).
In any case, I'm starting to feel comfortable enough with using the beta I've been testing to move over to the free version of 3.0D (at least start testing it). I think I still have Typekey issues to work out, but no blocking issues. And once my CSS book arrives, I'll be looking forward to having some fun messing with the look of my weblog.
And with that I think I have blogged enough about 6A and MT 3.0D and the release. Back to our regularly scheduled programming.
We're into the last half of May now, and that means Hurrican Season is coming soon and the National Hurricane Center's hurricane predictions are in.
This year's storm names:
Alex, Bonnie Charley, Danielle, Earl, Frances, Gaston, Hermine, Ivan, Jeanne, Karl, Lisa, Matthew, Nicole, Otto, Paula, Richard, Shary, Tomas, Virginie, Walter.
Some highlights from the NHC's predictions:
The outlook calls for 12-15 tropical storms, with 6-8 becoming hurricanes, and 2-4 of these becoming major hurricanes. These numbers reflect a predicted ACE index in the range of 100%-160% of the median, and indicate a likely continuation of above-normal activity that began in 1995.
Many of the tropical storms and hurricanes in 2004 are likely to form during August-October over the tropical Atlantic and Caribbean Sea between 9°N-21.5°N (green box). These systems generally track westward toward the United States and Caribbean Sea as they strengthen.
Another factor known to significantly impact seasonal Atlantic hurricane activity is ENSO (Gray 1984, Monthly Weather Review), with El Niño favoring reduced activity and La Niña favoring increased activity. Based on the most recent ENSO outlook issued by NOAA's Climate Prediction Center, ENSO-neutral conditions are expected to continue in the tropical Pacific through July, and most likely through August-October as well. However, there is considerable uncertainty in the statistical and coupled model ENSO forecasts after July, and the comparatively wide range in the predicted ACE values reflects this uncertainty.
There are two competing uncertainties in this outlook. The first is the possibility of an extremely active season similar to 2003, which resulted partly from near-record warmth across the deep tropical Atlantic, and partly from an amplified upper-level ridge across the western subtropical Atlantic and Gulf of Mexico in association with a persistent East Atlantic teleconnection pattern (Bell et al. 2004, Bull. Amer. Meteor. Soc., In press). In the event that the warmer tropical Atlantic SSTs and the subtropical ridge over the western Atlantic again become significantly enhanced, the ACE values could be at or even above the high end of the predicted range.The second uncertainty involves the ENSO forecasts, which have exhibited low skill historically when issued at this time of the year and represent an ongoing source of uncertainty in the pre-season hurricane outlooks. There is currently considerably diversity in the statistical and coupled model forecasts of ENSO after July, which leads to a wider predicted ACE range in this outlook.
In the latest entry to SixLog, the question is asked: "How are you using the tool?"
If free isn't an issue for you and you're willing to pay for a version of Movable Type (say the $69 version) and the blog/author limits won't work for your current use, write a non-emotional post explaining how you're using Movable Type and TrackBack this entry.
I work in the Radiology department of a university hospital. When I first decided to install MovableType on my server, it was in response to one of our radiologists who wanted some software that our residents could use to log the procedures they perform. A place where they could leave notes, pictures, descriptions, details, whatever. Our program typically has anywhere from 4-8 residents per year, so there would potentially be as many as 40 weblogs and authors. A weblog would be perfect for this kind of application.
Unfortunately, they decided to go with a different system, so now this installation of MT hosts 1 active author and 4 weblogs.
In the near future I plan on introducing MT to our Radiology Informatics group to see if they might find it useful as a group communication tool. This would involve adding 5 additional authors and at least that many more weblogs. I also plan on introducing MT to the rest of our faculty to see if our radiologists and residents might find it of any use. Thats maybe another 30 or 40 authors. Of course I don't expect all of them to use it. If 10 of them decide it's useful enough to use regularly, then I would be impressed.
Lately my wife has been trying to convince me to get a cell phone. She knows I don't want one, but she keeps insisting I need one. I keep insisting that I don't need one. Heck, I don't even like carrying a pager.
Now she's telling me to pick out a cell phone that I'd want, or she'll pick one out for me. Considering my pickiness for technology, it'll probably be one that I'll end up hating (if I can hate cell phones much more).
So, since I have to pick out a cell phone that I don't want, let's see what what kind of cell phone I would use.
Let's see, I suppose that for starters, since i have a T3 with Bluetooth, I might as well get a BT cellphone so I can make use of it. bluetooth.com lists a bunch of BT phones, made by Motorola, Nokia and Sony Ericsson.
Motorola has the V600. Nokia offers several BT models, but I like the Nokia 6820 best. Sony Ericsson also has several models, with the T637 looking the most appealing.
Now to see if any of the local providers carry them.
One Friday night up at RATT, R and M have disappeared from the table. Later they are spotted a couple tables over schmoozing on two members of the female persuasion. Stealthily, we observe (well, as stealthily as any table of drunk people can observe) the evil seductresses sinking their claws deeper and deeper into our inebriated friends. Finally, B decides to act. We must save our friends from the clutches of the evil temptresses. Our friends have been bewitched. They think they want to stay with the females, and keep schmoozing them.
B and I stumble over to the table to see if R and M can be saved. We're almost too late. We need to resort to stronger tactics.
B says to M: M, your wife just called. You have to go home because Stephanie's sick.
The sudden breaking of the spell sends a reverberating shock through everyone at the table.
Evil temptress 2 turns to R and says: So, are you married too?
We return to our table with R and M, still in shock, but rescued.
Another successful mission by the Paladins of the Penis.
It all begain in 1994. I was tired of living on my own in a dingy little basement apartment. Geezus was looking to move out of his parents' house and so was Oreo. So it was just natural for the three of us to get an apartment together. So we began the hunt for a reasonably priced 3 bedroom apartment near the campus area...two mutually exclusive criteria.
After much looking and checking out many apartments, we finally found one, a good sized 3 bedroom 2nd floor apartment for about $650/month. It was a fantastic location. A nice 15 minute walk to campus, and staggering distance to Whyte Ave and the Purple Onion. Close to the Farmer's Market, and we had the Fringe Festival practically in our back yard.
The MERK Chapter House, as our apartment later became known, quickly turned into the launching point and crash pad for many nights of carousing. It was a gathering place for Hooligans all over.
The collection of empty Coke cans in the corner became legendary, and proceeds from the returns funded purchases of even more cases of Coke, plus the occasional bottle of Crown (to mix with the Coke).
Eventually, the Chapter House became decorated with the spoils of our drunken wanderings. A life sized cardboard cutout of Darth Vader (obtained as a surprise after purchasing the Star Wars VHS boxed set) sat in one corner along with my bike and indoor trainer. Nobody remembers (or is willing to admit) where the street sign hanging on the wall came from. Empty bottles of Crown Royal lining the tops of the kitchen cabinets. The sandwich board sign from the Black Dog mysteriously appeared in our living room one day.
Life at the Chapter House was good, life was fun and care free and became the source of many memories. Walking into the living room to discover a naked girl prancing about. Coming home from school to discover a happening party and no signs of the roomies around. Staggering home from nights spent at the Purple Onion. Pizzas at the Funky Pickle. Drunken Hooligans scattered about the living room from the previous night. Black Creature spewing all over Oreo's futon. Geezus making a ritual sacrifice to Hoo over the porcelain altar. And who could forget the massive clumps of hair from Geezus' brush scattered about the bathroom looking like dead rodents.
Sadly, after about two years, the Chapter House was forced to close. I got a job in Detroit, and Oreo moved to North Carolina to work.
Those were fun days living in that apartment.
In Your MT-Blacklist Wish List, Jay asks what should go into the next version of MT-Blacklist.
Here is what I'd like to see:
Although not plugin related, another thing I'd like to see is the format of the Latest 100 changes changed to something that could just be copy/pasted into the blacklist. Then I wouldn't have to grab the master blacklist file all the time and have it tell me that most of the entries are already in the blacklist.
That's all I can think of at the moment. If I come up with more, I'll add them in.
I was just watching Kitchen of the Future on the Food Network.
Connected refrigerators that know what's in your fridge with RFID-tagged foods. The stove that you can control with your cell phone. The steam iron that tells you if it's on, or that it's still hot.
So now our e-fridge can tell us if we have any e-cookie dough to e-bake in our e-oven and then later e-eat. And we can do this all with our e-cellphone (mostly).
So that you can bring morning rush hour traffic to a complete standstill for 15 minutes while the drawbridge is raised and lowered so you can get one with your boating day.
Headed off to Orlando tomorrow for a little mini-vacation. We're going to drive down there, so it should be an interesting road trip. We're going to hit SeaWorld, Kennedy Space Center, Cirque du Soleil Nouba, and hang out at and Universal Studios Orlando.
Should be fun.
While I'm gone, I probably won't be blogging, and I'll be turning commenting off. Since upgrading to 3.0D, spam's been a bit of a problem lately without MTBlacklist to filter things out. So rather than come back and have to delete several hundred spam comments, I'm just going to turn it off. I'll turn it back on when I come back.
Back from my trip to Orlando. Much fun was had, much baking in the sun was done. I'll put some pictures up in my gallery shortly, once I've gone through and organized them a bit.