The Great Change: Turning Cathy into a Lawyer

Welcome to my blog. Thanks to Joe Nekrasz for helping me set it up.

I'm still testing everything, so too soon to start with the "serious" writing.

Come back soon!

I decided that I should formally articulate an editing policy for my blog. I wasn't worried about this at the beginning because I wanted to see how things would develop (and I reserve the right to modify and/or abandon any policy set forth today - my blog, my rules!) but since part of the reason I'm blogging is to set a historical record documenting the Great Change (and you know how I feel about documenting...), I don't want to corrupt that record with retroactive modifications.

There are some reasonable exceptions though:

• Typos are always fair game for fixing.


• After making a post, I may come back later to rephrase parts of it. It's important for me to articulate myself clearly, and sometimes I find myself lacking the correct words to do it at the time I post. Sometimes it's only on re-reading posts that I finally find the phrasing I was searching for. Depending on the time that has passed since the original post and the scale of the changes I may leave a notation describing the edits. I won't generally do this if I make changes on the same day, but I will be more likely to do this if it's possible that readers might get confused ("Didn't it say something different the last time I was here???").


• Inline URLs can be adjusted at any point, but I will try to leave an editing notation to indicate if there has been a significant change.


• If I really change my mind on something, I will try to follow the protocol of not mutilating or destroying the original post. Rather, I will follow it up with another subsequent post and/or a comment. An example where I did (something similar to) this was for the June 13 and June 15 posts.


• Comments, part I: I'm really enthused that there's been some interesting discussions in the comments already. I would like to leave the comments section alone and not edit them at all, but I'll have to see how things shape up. I reserve the right to delete comments that I am not comfortable with hosting on my site for any reason, but I would prefer not to interfere. I've been debating the merits of deleting off-topic comments, but the volume on the site isn't such where I think that's necessary at this point.


• Comments, part II: I have on occasion gone back and removed typos from my own posts, but I am looking to resist editing them for content because the other people leaving comments do not have the same ability.

In continuing with yesterday's post, I've also decided that writing with emoticons should be verboten here. Prior to their advent writers managed to write with precision without resorting to their use, and if I hope the exercise of keeping a blog to improve my mastery of the craft, then I should also eschew them.

Besides, in keeping with the "becoming a lawyer theme," I doubt that most lawyers employ them in their legal documents:

"The plaintiffs in this case assert that the defendents did willfully and knowingly defraud the plaintiffs of $1 million :-("

Somehow I don't think so.

Even outside the blog I'm trying to avoid using emoticons. It seems that they've become a large crutch making me lazy as a writer. On the other hand, in emails and online chats it may still make sense to use them. It's not worth risking the breakdown of a friendship if the gratuitous use of an emoticon could have avoided the problem entirely.

It was also interesting when I administered the survey for my undergraduate thesis (where I researched usage behavior of the Internet). One respondent, who was clearly an early adopter with regards to the Internet, included a handwritten comment to clarify a multiple choice response, and in the margin, after the comment, wrote a smiley face. Sideways.

A follow-up post.

I should have done this a long time ago but I didn't have the mental bandwidth to look into this and figure it out. I have now released the blog under a Creative Commons license.

It's worth checking out the Creative Commons site for more information about these licenses and how they work. Since I began my blog they seem to have added some helpful illustrative cartoons to help explain the licenses and what rights they do or do not reserve for authors. For my part I chose to allow the contents of my blog to be reused in a non-commercial context as long as attribution remains and any derivative works are released under the same license. A benefit to using a Creative Commons license is that people who want to use my work under those conditions can do so without needing to contact me to discuss it first. At the same time, none of my other rights that copyright law protects are compromised beyond what my license chooses to concede. Given that my purpose in blogging is to communicate with as wide an audience as possible to contribute to public discourse, I decided it was worth my while to not be heavy-handed in restraining all of the increasingly myriad rights U.S. copyright law affords.

It has crossed my mind from time to time that people might mistakenly perceive that I'm speaking for other people or organizations I'm connected to, either on this blog or in other contexts. Being in DC has magnified this concern. It's a surprisingly small community of people who deal with each other so frequently that it's fairly easy to learn and remember who knows whom, who said what to whom, who did what to whom, etc. Enemies are surprisingly easy to make, and it's also surprisingly easy to inadvertantly drag other people you may somehow be connected to into your battles just by association.

But that's a pity, if for no other reason than it affects people's autonomy and compromises their honesty. It makes everything political, so you can't do what you think best at the moment because you have to be worried about payback. I suppose that's true in any context, but in Washington where so many people are here to try to affect the world, and so many battles necessarily are fought in the process, a sense of political pragmatism is particularly important.

I really like being in Washington. I really like being somewhere where important things happen. But I absolutely, positively do not want to get sucked in and corrupted by it. While discretion is valuable in any context, and I'm mindful of how I refer to other people on my blog particularly in any identifying way, I do not want to have to compromise my candor, my honesty. To the extent that this blog tracks my intellectual journey, it needs to be a true record of it. If I were to compromise that, I think the journey would be over and there'd be nothing left to tell. The destruction of my idealism would be complete. I want to believe that principle and independent thinking can triumph over all. I will hang on as tightly as I can to keep it from ever turning into a wishful fiction.

That said, there is still the pragmatic problem of inadvertantly sucking in people and organizations I care about into my own little drama. So I want to state clearly and explicitly for the record that I speak for myself. Only myself. People I know may agree with some, much, or even all of what I have to say. The same is true in reverse. But I am an independent thinker and so are my acquaintances. The following statement is therefore unequivocably true: what I communicate, including here on this blog, unless otherwise stated and authorized by another party, REPRESENTS ONLY MY OPINIONS, BELIEFS, ATTITUDES, PHILOSOPHIES, KNOWLEDGE, AND/OR UNDERSTANDING. Regardless of any affiliation, what appears here is only what I as Cathy Gellis, Individual, have to say.

Lately I've been slowly, and reluctantly, turning off the commenting feature on my blog. It distresses me to do this but the comment spammers have been getting out of hand. There have been days when I've had to spend an hour deleting all their crap. Part of the problem is that my blog software doesn't allow for easy deletion. But the other problem is that in their quest to improve their google rankings, they try to get their URLs linked to as many sites as possible. With easy access to mine they've been merrily posting away.

Since I've been turning off the commenting though it's been more under control. The older posts with known URLs to the spammers are now off-limits to them. It's too bad, because I'd really like for people to continue commenting on them, but I had to draw the line somewhere. I'm trying to keep the more recent posts open though. I really like having the comments because I like to see how people react to my writing, and I think the conversations my posts sometimes spawn can be really interesting.

Really posted 11/17.

I decided that my "Law School – The Process" category was getting too disproportionately big. (And it would only get bigger, since most of my posts talk about it, what with it being the ostensible focus of the blog.) So I split it up by year. I figure a year will run from July to July. The dates of my posts suggested that split, and I think it also makes sense. In July you start anticipating the upcoming year. In June you are still getting over the previous one.

I also finally (I think) figured out how to syndicate my site. I'd meant to do it before, when someone commented somewhere here that she'd really like me to do it. I'd like to write her back and tell her I have, but I can't figure out where her comment is to find her email address. (Edit: found it.) What I'd really like is for someone to tell me if I did it right. There's a link on the front page for the syndication, which links to here: http://www.cathygellis.com/mt/html/index.rdf. This is just my best guess though since I don't really know how RSS works. Poking around the MoveableType manual has not so far been helpful on this front.

Edit 11/26: Today I played with my first RSS newsreader. I'm using Thunderbird. It didn't like the URL above, but it did like this one so I've added it to the side navigation: http://www.cathygellis.com/mt/html/index.xml.

Beware with syndicated readings, though, that I frequently edit new posts. I almost wish there was a way I could keep things from going out on the RSS feed until 2 days after the post or something. I think the way it works the headline will go out, but when you click on the article you'll get the latest and greatest version that's posted. Which is fine, as long as you are aware that there may be a later version and don't just delete the article and move on. But I guess that could happen on the real site. Why would you reread an article you've already read? Maybe I'll just have to get better at editing up front...

(The other hazard of the syndication is that those horrible comment spams will go out if I haven't had a chance to delete them. Sorry. I don't mean to be the authority on penile implants and texas poker...)

Speaking of editing, my Musicians for Kerry posts have had some work done to them since first posted. I may still make some tweaks, but they're better than they were before 11/19.

Edit 12/2: It's interesting to note that even if a blog does not have a syndication link on it, it probably still syndicates. The blogging software seems to set up the xml pages automatically, whether the author explicitly advertises the links or not. For instance, apparently my blog was syndicated well before I got around to syndicating it...

Edit 12/8: The dark side of RSS: bandwidth consumption. The BoingBoing post referred to talked about only allowing one RSS download per day/update/other iteration. But I'm not sure how it was achieved. This isn't a huge problem for me though as a publisher - yet. I'm just not that popular... (darnit).

For my latest trick I turned on the trackback feature on my blog. I'm not entirely sure what it is and how it works (MoveableType had rather cryptic documentation on the subject) or that I've got it all set up right, but I think it's a(n automatic) way of listing on my blog any other blogs that link back to mine. So I can now very easily and conveniently see ... just how little influence I have in the blogging world. But in case fame occurs, I'll be ready.

I've added a new category to the blog, called "Blog meta." More and more I feel inclined to comment on issues involving blogging generally - as have many other people on their blogs - and this seemed like a good way to catch those posts. I just set it up and pulled in a few old posts to start populating it.

back·date   (bkdt)

tr.v. back·dat·ed, back·dat·ing, back·dates

To go out with an old flame

No, not really. (Or at least that's not the way I mean it here.)

I've been wrestling with the dating of my posts, and I think it may be time to rethink my policies. I've been trying to keep them spread out, partly because I think it makes the blog look better maintained (and not undeservedly so), and partly because I like to fully populate the calendar on the side (that may be a silly reason, but my blog, my silly reasons). All that may be well and good, but I'm wondering if it's getting out of hand. For one, since I tend to post several things all at once, most of my posts are getting date changed notations on the bottom. It's possible that those notations should be the exception but I think they are becoming a rule. And then there's the problem of the accuracy of the record I'm trying to keep.

On the BlogEthics site I almost posted an answer to another of the questions, "When making decisions about your blog, do any of the following values or duties cross your mind?" And then he listed several values including transparency and factual accuracy. I started writing this as a response (although I didn't post it):

I find myself very caught up in the transparency aspect, although it manifests itself in logistical details. Since I hope my blog will be a record of the time in which it was written, I find myself wanting to ensure that it be as reliable a record as possible. The catch is that I'm trying to create a fixed record in a malleable medium. I can always go back and make changes. I often want to, particularly if I hadn't quite been able to make the point I wanted with sufficient clarity at the time I wrote it. But if I make changes retroactively, I run the risk of undermining its legitimacy as a record. So I find myself pursuing all sorts of conventions to try to reach a happy medium. I have posts outlining my editorial policies on edits, and I leave tons of markers at the bottoms of my posts noting any changes. I don't think I've achieved nirvana on this point, but I'm trying...

Of course, what is it really doing for historical accuracy if I keep changing the dates on my posts?

So I think I'm going to tweak my policy. There are many times when the idea has struck me earlier and I've mentally drafted (or actually drafted) the bulk of the post on an earlier date than when I post. In those instances, I think I will still backdate because it is ultimately more accurate to represent the dates when the mood struck. But for posts that have only been vaguely brewing in my head until the one day when the muse lets several out, I think I will let them all be posted for the same day. It won't break anything. Lots of bloggers have lots of posts on the same day. And in telling the story about my law school process, it does tell it accurately to show which were the days that I felt more prolific.

Of course, we'll see how this goes. Old habits die hard.

Apparently for the last few days comments have been blocked. I only just found out about it now (thanks, Mark) although perhaps I should have gotten the hint from the lack of comment spam needing deleting...

Anyway, it appears a null entry got into the list of IP addresses to block, which effectively blocked everyone from everywhere. No comments, no trackbacks... I hadn't meant to be this unsocial, so my apologies to anyone inconvenienced (unless you are a spammer, in which case, screw you - it's your fault I even need to mess with the IP blocking tool at all). Please come back and link and comment to your heart's content, especially on this entry where I specifically asked you to.

So add this to the list of aggravations... Have I mentioned how much I hate technology?

Edit: Wow, the comment spammers were really chomping at the bit. I've had comments enabled for about an hour and already I've had to delete two spams.

Also, lest anyone think I am making too much out of my technological misery, let me also add to the list my mom's scanner and printer, which both also broke in recent weeks. Luckily I had another scanner I could give her, though it took a few weeks to get them to send the software so we could get it properly installed. (Getting it up and running was important for our ability to send faxes, e.g., transcripts, which comes up from time to time.) But the printer finally bit it this morning, just to make sure everyone in the household could be as inconvenienced as possible.

It's a conspiracy, I tell you...

The blog is now upgraded... mostly. As far as I can tell everything works, at least from your end. On my end, the admin screens are a complete mess -- in Mozilla. They are gorgeous in IE. There's something so wrong with that... In fact, I wonder if anyone else has this problem because I imagine MT users everywhere would be up in arms over it. There must be a quick fix I can get my hands on somewhere... Suggestions?

Edit: It turns out it's only somewhat gorgeous in IE. I've poked around the MT support forum and gotten a few ideas, but none seem to really solve the problem. There must be something obvious that I'm missing, but I can't think of what it is.

In the meantime, I wonder if trackback was broken on my old installation, because as soon as I upgraded I got all sorts of trackback spam. Oh, joy... The good news is that the new MT makes it SO MUCH EASIER to delete them. Yay.

Edit 2/7: Other observed problems include punctuation that has turned into "?" (mostly where you would expect to see quotes, dashes, or the occasional ellipse) and the stylesheet for the search results seems missing. Eventually, I presume, these things will be sorted out... But the important thing is that I can write and you can read, so essentially all is well.

Edit 2/11: The admin screens all work now. Just thought you'd like to know... Some of my external templates are still a bit mushed (eg, page archives, search results) but it's all nearly back to 100% operability.

Apologies to anyone who couldn't connect to my website within the last day. Even *I* couldn't connect to it, not even to post anything. I'm not sure what happened to it, but I suspect that the webserver needed restarting in some form. The problem is that my ISP isn't really a commercial one that provides 24/7 support. It's run by a bunch of people whom I completely trust technically, but it's not their day job and so when things go wrong it sometimes takes them a while to respond. For me it's a trade-off: I like not being with a commercial service and I trust the technical skills of the staff to solve any problems. Unfortunately sometimes the problems can escape unnoticed (and therefore go unfixed) for more time than would be good.

But I've paid for my service for 2005, and I really, really, really don't want to have to try to move everything. So let's hope for the best and lots of uptime...

When I set up my blog originally I anticipated posts falling into certain categories. The structure held up fairly well for a long time. But I'm now nearly two years into blogging, and maybe because of the Great Change itself, the structure has started to get a little frayed.

So today I added a few categories, renamed a few, and moved some posts around. The major changes are the addition of "Law school - Life at BU," which is a category about things that have to do with the law school experience at BU (or even to some extent in general) but not so much my own personal development, and "Politics," which is essentially an off-shoot of the "World Events" category.

I also renamed the "Learning the Law" category to "Reflecting on the Law" and moved a bunch of posts. Posts that had more to do with my progress through the academic curriculum went more to the "Law School - the Process" categories. Remaining are posts that reflect on legal issues that cross my mind either through my classes or other extra-curricular channels.

I'm toying with making a few other changes, but I may wait and see how well this breakdown scales for a while first.

This was an itch I needed to scratch: on the front page, I added a link to the category each post belongs to. I also removed the "author" information, since I'm the only author on the site. All posts are by "Cathy" so there didn't seem to be much point in bashing people over the head with that information repeatedly when I could save all that space by leaving it out.

These are the blogs I read:

Syndicated blogs, as listed in my RSS reader -

Non-syndicated sites (or sites I don't read through RSS) -

BoingBoing - A group blog, like Slashdot, but better. Better stuff, better writing, and Cory Doctorow is there. RSS'd but I read it onsite.
Equal Process? Due Protection? - Written by a 2L at the University of Miami, I think.
Expressio Unius - I think this person may be recent Berkeley law grad, who has me in his blog roll.
Volokh Conspiracy - a group of law professors. It may be RSS'd, but I go to it regularly instead.

Edited 5/5/07.

In trying to figure out why trackbacks weren't showing up on the pages of the posts they belonged to, I discovered that my upgrade didn't go quite as well as I'd thought it had. On the upside, I now know why my search results pages look so ugly, and I was able to get the trackbacks to show up. But now my blog is hovering somewhere between version 2.x and 3.x, and I'm not sure what to do about it.

I liked things the way they looked when it was 2.x. Or at least I got used to it. I pretty much used the default templates and stylesheets, with just a few modifications. Version 3.x seems to require using different templates and stylesheets, and I have to decide if I want to make that leap. Right now though I'm using what went with 2.x, with a minimum of 3.x bandaids to get back functionality that disappeared, like the trackbacks. I'll need to decide if (a) I want to leave everything the way it is, despite the ugliness resulting form the templates and stylesheets not matching, (b) continue to apply bandaids to fix the ugliness, or (c) bring everything over to 3.x so the look-and-feel and functionality match the way they are intended.

Anyway, I mention this so if on subsequent visits the site seems to be a different color than you last remember, you needn't worry you're hallucinating...

I played around with my categories again. I added one, "Sports," where I put most of the cycling, baseball, football, and swimming posts, unless I was focusing more on my participation in them. I also changed - again - my "law school, the process" categories. They are now "The Great Change (1L year)" (et al). I think it's better that way, and the names probably how better reflect how I always envisioned the categories being used.

It might be easier to explain what they contain by explaining what they don't contain. Posts were I describe aspects to the BU experience or the law school process from a structural perspective tend to go in the "Law School, life at BU category." Posts that give insight into who I am as a person but with little reference to (or impact by) law school go in the "About Me" category. What's left goes into the Great Change categories. These are the posts that describe the process of the change or leave breadcrumbs about how who I am as a person has changed as a result of that process. (As I may have mentioned before, the years run from July 1-June 30.)

Clear? I thought so...

I also took the opportunity to update my blogroll.

Web services on my ISP were down since Friday. It made me very sad, not being able to write on my blog. And very distressed, since it also meant no one could read my blog!

I sent a series of increasingly plaintive emails to the sys admins, which went unanswered. But today, when I logged on to check my email, I discovered a pile of comment spam (I get email notifications on every comment and trackback). I've never been so happy to see it - it meant my site was back. Yay!

Of course, during the weekend when there were no comment spams, I had the occasion to admire the regular spams that normally are drowned out by the email notifications. In addition to the flurry of mortgage offers and male physique enhancers, I got a spam from an anti-spam organization, and another offering me a year's supply of pringles.

It got me thinking about the spam I got sometime in early 2003, the one that let me know it was a new world order. It was one of those Nigerian 419 scam emails, except that it wasn't sent under the auspices of a Nigerian diplomat. Instead it read, "Dear Sir or Madam... I am the Minister of Culture for Iraq..."

Just a quick "change log" note to say that I added a new category for "pop culture" and moved some other posts around.

My blog is under a full-scale attack by spammers, at unprecedented levels. As a result I've had to turn off allowing unregistered comments, at least for a little while. I'm hoping that if it's off, the spamming will stop. Or at any rate, I can't let them accumulate faster than I can delete them and block their IPs. Given that turning it on for barely 5 minutes resulted in 27 new comments, I shudder to think how many would accumulate if I were offline for more than an hour (which sometimes happens, like when I sleep and stuff).

I'm hoping it will soon blow over, but in the meantime I've done this and I'm turning off comments on more old posts. Except for closed posts, though, you can still comment -- as long as you register. The problem: I'm not quite sure how you register. I think there's a way you can register on my site if you want to comment, but I haven't quite figured out how. You can also use a TypeKey login, but I think I need to tweak my settings to make that work and I'm not quite sure how to do that either.

One way or another, though, I'll do something (as soon as I get the chance). I like having people comment. But it may be a little hit or miss for a bit until I get this worked out. $#*%$ spammers...

Edit 8/4/05: A compromise on comments... You can post annonymously and unregistered-ly, but they won't show up right away. I'll have to approve them and then they'll show up. I plan to approve everything that's not a spam, though, as a matter of course, and HOPEFULLY this will be temporary and I'll be able to turn them back on completely. But in the meantime this seems like a reasonable middleground.

The last attack at least seems to have abated, and perhaps this change is why.

I temporarily turned off comments again in preparation for upgrading Moveable Type (the blog software) again. Plus it will be a hectic couple of days and spending hours on deletion of the spams is not what I want to be doing.

But expect the look and feel to change a bit in the forseeable future as I get this all squared away.

I hate not being able to blog. It makes me very cranky when I don't get to write, and the last bunch of days with all the travel and moving in left me with little opportunity to sit down and still my thoughts enough to get them down. Then once I could, I was further stymied by not being able to get online. But at least I got a few posts queued up, and I've now added them and backdated then to when they were created. (You should read them in chronological order for the best sense of my character development...)

It does bug me that there were things I wanted to say that I never got a chance to sit down and write. Things that I think were important to write down as part of the documentation of my Great Change, but are now impossible to write about because even just a few days later I've moved on too far past where I would be emotionally able to accurately capture and chronicle how I originally felt when the urge to write had hit.

(Meanwhile I have obviously not gotten around to updating the blog software, and it will be further hampered by the lack of Internet at home, so I think I will leave the comments off for a while longer. Please email me though if you would like to have one manually added – I'd be glad to do that and get good discussions going.)

I'm going to wait until MoveableType figures out how to properly document the upgrading before I attempt it. So in the meantime I've cautiously turned back on the comments, because I hate not getting real ones. (Although it's been a lovely break from the spam ones...) Comments still require approval, though, just to keep it from getting out of hand. I'll try to get on them as soon as I can though.

(I also reserve the right to give up and turn them off again if I need to. Hopefully this upgrade will forstall some of this nonsense though...)

Edited 9/12

A quick housecleaning note: I modified the category name "Life at BU" to "Life at my school," since I've been talking about Bucerius in the same way that I talk about BU in posts of that category.

Edit 10/8: I changed it again to "School life." I think it sounds less stupid.

I went away this weekend and just got back yesterday. I blogged regularly during that time, however. Except not online, but in a notebook. I came back with about 30 handwritten pages that I just typed up for posting. I have adjusted the dates for when they were written.

For the best effect, start reading here and work forward.

The previous post was written in response to a recent site outage. It's back up, sort of. Already published pages are viewable, but the backend that lets me post isn't too healthy right now, which may affect further posting and maintenance. Although I hope not...

(Also, I've - hopefully temporarily - turned off trackback. Kind of. New posts won't accept them, although the old ones are still vulnerable to spamming because I can't easily turn them off. Hopefully once I get MoveableType upgraded I'll be able to manage them better and turn them back on, but for now I'm trying to scale back to try to lessen the load on my apparently fragile infrastructure.)

(However comments are still on. So have at me! Join the crowd...)

(Although if the backend isn't working it's gonna take me a while to get them posted. Sorry.)

I updated my blog roll. Nothing too major - a few sites on, a few sites off. It's kind of sad to take sites off for having gone dormant, particularly if they were really good when they were maintained. I did leave one on that may have gone dormant because I'd actually corresponded with the author and perhaps he'll want to come back to it, but I can't chase after all the other sites of people whom I only "knew" through their posts.

Anyway, now that this itch has been scratched, back to studying for exams...

I finally got around to upgrading the blog software. After much gnashing of teeth and swearing at my ISP that is not too healthy these days, it finally seems upgraded. I hope. I suspect there may still be more things to correct (like, um, what happened to all my comments???), and the look and feel may change drastically if I decide to play around with the stylesheets. Hopefully I'll be able to get this all taken care of soon.

Edit 1/4: This would all go much better if MoveableType actually had something resembling comprehensible documentation to help this process along. Sadly, it doesn't.

The biggest problem that I still have is that I can't administer pre-upgrade comments. The old ones do seem to still be attached to the site, but they don't show up in the admin screens. It's not the most enormous problem as long as I can administer new ones, but I would be much more comfortable if I could get them all to show up. Unfortunately I have no idea how that can be achieved and can't find any intelligible documentation anywhere on the Six Apart website that can shed some light on the problem. If anyone reading has some thoughts on how to fix this, I'd appreciate them.

In the meantime, however, I've allowed comments to be posted again without moderation. We'll see how this works out...

Edit 1/5: Ugh... The upgrade seems to have converted (all? most? some? many?) of my hyphens to question marks! That's going to be a pain in the ass to fix...

With the upgrade to Moveable Type 3.2 I decided to upgrade the templates to the ones they recommended. It seemed just as well since the last time I upgraded things started to break, template-wise, and with the 3.2 version they offered a handy tool to get them all set up right.

Unfortunately that meant that my entire blog interface broke as soon as the templates were updated. This wasn't unexpected, but it was a hassle.

One of the advantages to having the new templates, though, is that there are a lot of stylesheets offered to create varying appearances for one's blog. (A stylesheet is a file that the web browser looks at to determine how to display a page. Thus it's possible to radically change a page's display just by changing the stylesheet file - and not having to reprogram the entire site's HTML.) I tried out a few, and hated them all.

And I liked what I had. I wasn't ready for a change. Changing the look and feel dramatically would seem to also suggest a dramatic change in the blog's content, and that's not happening (at least not today). Plus I found most of the suggested styles to be poor choices given my blog's content. I tend to write long, dense posts, and it's important to make them as easy to read as possible. I'm not sure the way I used to have it was ideal, but the old interface produced posts that were much more legible than any of the new stylesheets I tried.

So instead I settled on using a stylesheet that I could fairly easily hack to make it look like the old one. I used the "green grass" one, and changed it from this to what you see here. It took some doing, but thankfully I have some web development skills... In a way it was fun to dust them off and engage in the unique problem-solving exercise of web development. But in another way it was completely irritating...

There are still some things I need to tweak or fix, as I get around to it. One particular problem that I can't figure out - but I'm sure I didn't cause - is the random closing tag at the top of the monthly archive pages. And I might squish some things closer together, or rearrange little bits of things. But mostly I'm satisfied, and it's mostly the same as it was.

(One thing that is different, however, is that there's no longer a calendar. I could ressurrect it if I wanted - with some effort - but Six Apart recommends against it since it slows down site rebuild times. I have enough problems trying to keep my ISP from crashing while I rebuild things, so the time-savings is much more appealing than the calendar was. Plus maybe now I'll be less inclined to backdate things...)

Edited 1/6. Actually, maybe "edited" isn't the word as much as "completely-rewritten" would be... I'd written the first version of this post at one o'clock in the morning, which didn't do much for fluidity, but I wrote it as a test post as much as anything so it seemed reasonable to go back and fix it in the light of day, particularly after having made more fixes.

Edit again: I figured out how to fix that extra closing tag problem. Have I got skillz or what...

Speaking of web development... I've decided to try having a "recent comments" feature on the side of the blog like many others do.

I'll have to see if I like it. One benefit is that it could help keep some discussions going that are otherwise buried in the site. On the other hand, it could end up being taken over by spam.

I currently have it set to five comments in order not push the categories too far down, but that may or may not be enough to make it worth having.

Instructions for how to do it gleaned and adapted from here and here.

I've done two things:

1) I made it so "visited links" show up in a different color than unvisited links. Unvisited links still show up in current a tealish blue, but now visited links are sort of purplish. What do you think? Choices include going back to the way it was, where links were always the same color, or keeping the change but tweaking the colors, or keeping it just how it is. My thinking is that it's a good idea to have differently-colored visited links since I make so many self-referential links and people might like to keep track of what they've already read. But perhaps the colors could be improved?

2) I changed the font. I'm thinking this font is more readable. What do you think? I'm wishy-washy on keeping it though. For one, it changes the look and feel of the site at an odd junction, and for another, it kind of looks odd with the other serif fonts. I suppose I could change them too, but then the look and feel changes really dramatically.

I guess my thinking is that unless the site is vastly more readable, I may roll it back to the old font just because I'm not quite ready for a drastic change. But feedback on it would be good for when I am.

Edit 3/11: Font rolled back. Someday when I overhaul the look and feel more thoroughly I'll change it to something sans-serif, but for now I think this font may actually work better as it sets the main content off from the sidebar in a way the sans-serif font didn't.

I've been having some problems again with my web host again. The maintenance scripts haven't been running on it properly (preventing me from making updates and edits, and interfering with the submission of comments), and sometimes the site hasn't been available at all. At the moment it all *seems* better, but in case you encounter further strangeness, this is why.

I didn't want anyone to think I was giving up on my blog by being quiet for a while... Some posts I've been working on haven't quite come out the way I'd like so those haven't gone up yet, and they may be further delayed since I *may* have spotty Internet access over the next week. More details about that later... </mysterious>

But stay tuned, because I suspect at some point in the near future I'll have a whole wad of catch-up stuff to post.

FYI - I turned off trackbacks. Much as I liked the idea that I could see who was linking to me, either no one ever was or it just wasn't working. All that happened is that I deleted spam, so forget that. Someday maybe I'll replace the feature with Technorati, if I can figure out how it works, but for now I'll just have to remain ignorant of the extent of my reach...

If you read this blog through Mozilla Firefox you may notice a green "C" in the URL line. I finally started investigating how to make a "favicon.ico" file to give my site a custom icon. However, it may change and/or disappear, as my investigation has not yet gotten me to the point where I know how to make them right. I screwed up the transparency, and the current format doesn't work in IE at all. Plus I'm not sure I'm crazy about the green "C" either. So someday I may fix this, but you'll hopefully all excuse me if I don't rush out to make it my highest priority...

If you've emailed me lately to either my Berkeley account or through this blog, I may not have gotten it (or not gotten it yet). The system I use has been quite ill lately and is not yet recovered. I've managed to get some things forwarded elsewhere, at least for the time being, but your best bet right now if you don't know my BU address is to email me through the blog address. It should turn up somewhere where I can see it...

Meanwhile, for people who've come to know and love me at my Berkeley address, it should someday (soon) work again, but I may use this occasion to transition to a forwarding alias so that in the event this does happen again, you can still find me. Drop me a line if you are someone I know and love and want the alias. People who know and love me through my BU address may also want it, since I suspect the BU one will soon go away too. (But we can cross this bridge later.)

Unbeknownst to me, the script handling comments got turned off. While it offered a wonderful reprieve from comment spam, it also prevented legitimate comments from being posted. I have now turned the script back on, unbeknownst to my ISP system adminstrators, who I think may have turned it off the last time... (I did tell them they could turn off the trackback script, but I guess they got carried away.)

Anyway, it's back on although running slowly. If the page seems to churn without posting, don't worry. More likely than not the comment has been submitted to the database, and the next time the site rebuilds itself the comment will show up. (Try refreshing the front page and hopefully it should show up, but even if it doesn't, it's probably still in the system somewhere.)

This mess is all the comment-spammers' fault. Assholes. I know there are some serious civil liberties concerns with pressing the trespass-to-chattels doctrine to Internet traffic, but in situations like these it sort of seems like a nuanced application of it might be appropriate.

I added a plugin that should help cut down on comment spams. However, I can't yet tell if it works properly. What seems to be happening at the moment is that comments do get submitted successfully, but the page turns blank after their submission. It will take some time to troubleshoot why that is, but if it happens to you, don't panic - I likely got the comment. Just back up your browser to where you were and keep reading. Thanks.

I made a new post category, "The Great Change (post grad)," since little of what I have to post now belongs in the 3L category.

Graduating law school forces a lot of law student bloggers to think about what to do with their blogs since they are no longer chronicling the school experience anymore. But because I decided to write about the change into a lawyer, it means that law school is not so much the delineating point. After all, I'm not technically a lawyer yet. So I think I'll let things run as they are, with the new category, for maybe another year, give or take, and then see if and how I want to refocus my blogging. But right now I'm still working on telling my story, and it's not yet reached its end.

My comments script got turned off AGAIN! And without my knowing about it! This isn't good. I installed a new plugin that helped with the spam problem, so I don't know what's going on.

Apologies for those who wanted to comment and couldn't. In case this happens again, please feel free to email me and I'll post the comment myself. (I'd also appreciate being tipped off if there are problems since I don't always find out right away.)

I realized I have a bunch of posts discussing language, so I made a new category for them.

Just in time for links from Wil Wheaton, the law school round-up, and now Ann Althouse (thanks!) my web host is becoming decrepit again. Sorry about that, and sorry about the agonizingly slow process for submitting comments (if you were so inclined). Never fear, they likely were submitted on your first try, and I'll manually refresh things frequently so they'll show up soon.

I'm getting tired of this happening, so if anyone has any thoughts about a good ISP I could migrate to, I'd be interested in the recommendations. I'd say just leave them in the comments, but perhaps that's not the best plan...

The Great Migration has begun. Posting may be minimal to non-existent while I work on it so I don't end up with out-of-sync content. (Note: I'm not attempting to set up Blog 2.0 right now. I just want to get v.1.0 moved over to somewhere more stable.)

The status as of now is that I've opened an account on a new ISP (thanks to the reader who sent me the recommendation for it!) and uploaded Movable Type to the new home. (I'm simultaneously upgrading to MT 3.32, so theoretically that could add some complications, but I hope not.) I'll then try to get everything set up over there like it is here, copy the content over, and if everything looks ok, then transfer the domain.

The amount of things that could go wrong with this is staggering... but stay tuned, and thanks for your patience as I inevitably toy with becoming an off-the-grid hermit once again.

Edit 10/16: It's coming along but s...l...o...w...l...y.... (MT now installed on new ISP, but not configured yet. Delay in doing it not my fault, I swear...)

I'm declaring a content freeze on the blog in order to continue the migration to the new server. This means no new posts from me, and I've turned off comments as well.

With any luck this period should pass quickly. I've now got MT installed and mostly configured. It's time (or nearly time) to import the content and see what happens. Assuming all goes well, then it will be time to transfer the domain name. Then I'll have to tweak a few more settings but by then it should be good to go.

Ideally the total time for all this will be just a few days, or at worst a week. Although if all hell breaks loose and it starts taking longer I'll post a status update on wherever cathygellis.com happens to point to.

Meanwhile, important note for RSS readers: if you are reading through the RSS 1.0 link I think it will disappear on the new host as a result of the MT 3.3 upgrade. Atom and RSS 2.0 will remain available, though. When the switch is complete hyperlinks to the feeds will be on the upgraded version in the same place where they are on this one now (although I assume the Atom and RSS 2.0 links will be the same as they are on this site, if you want to get a jump on that adjustment now).

Edit: Never mind. See subsequent post.

AAARRRGGGHHH.....

My entire upgrade/migration has been called off indefinitely. First I was stymied because the export file of my entries was apparently too big for the new MT installation to handle importing. Hmmm... not that MT provides any sort of indication that might happen, or provide any sort of mechanism to work around the problem (splitting the export file, perhaps?) I'm surprised there's not a plugin out there that could take care of the splitting - surely others have encountered this problem? - but I couldn't find one. Meanwhile SixApart (the maker of MT) has managed to break their community board so I'm not sure I can even ask for advice on how to deal with this.

But that's the least of my problems. The more severe one, the one that prompted me to unfreeze the content over here, is that if I move my blog, I will break every single static link. Every internal cross-reference will break, every link from any other blogger back to me will break, every reference in google will break, etc. The issue is that every entry has an ID number, and when the system archives each entry on its own page it uses that ID number as the file name. Unfortunately, what will happen when I migrate the export file (a big text file with all the entries squished together on it) is that the new MT installation will renumber each entry. The effect of this renumbering is that the archive version of each post will have a different file name. So it's not that the links will break, per se; it's that each link will now point to the wrong entry because the numbering has switched.

This is not cool. What's also not cool is SixApart's attitude. "Yeah, we know this will happen," they said. "That's why we've changed the default archiving system away from entry IDs to long form names." Yes, that's great. But I've been blogging since MT v.2, when that new scheme wasn't available. The fact that they glibly ignored backwards compatibility to the system they themselves enforced upon hapless bloggers by default is reprehensible. Yes, right now MT is free to me. But it's starting to feel a lot less "free" in terms of the time and money I have to spend cleaning up their mess and makes me seriously question the wisdom of ever using a commercial version.

Anyway, I think I have two choices if I ever wish to change ISPs:

- Keep the blog here until I declare v. 1.0 "done," at which point I will zip it up, archives and all, and just relocate it to the new ISP. The problem is that it will no longer be a blog. No one will be able to comment on any post, I won't be able to edit any post (at least not without digging into the HTML directly), etc. It will simply be frozen in time from whenever I zip it up. Or,

- Perhaps it's possible to go through my MT entries and figure out which IDs are missing, and then manually insert null entries into my export file to fill in the gaps in the sequence. Because the MT installation here has choked so often as I was publishing, I often ended up with duplicate entries. I naturally deleted the duplicates. But that's why I now have a sequencing problem. This installation understands that I have entries 1-7 and 9-10, but the new installation will think that I'm simply importing entries 1-9 unless I can sneak an entry into the 8th spot to pad it out.

This fix is probably the way to go, if I can. Unfortunately there's nothing in the MT administration that will help me do this, my current system is still prone to sluggishness, and my export file is still enormous and needs slicing. There's probably a couple of nice UNIX command that can do what I need, but sadly I don't know what they are...

So everything's back on for the moment while I ponder what to do. If I (figure out how to) pursue the second option I'll freeze it again, but until I stop with the swearing and primal screams of frustration, I'll leave it on...

Edit: No wait, it's back off. I'm going to try to figure this out...

Edit again: Fishbane, I saw your comment (it's in my system, just not appearing right now because of the freeze). I'm probably going to forge ahead as stated, or at least I'm gonna try it. But, uh, help would be appreciated.... Feel free to drop me a line if you'd like ;-)

It looks like my migration may work after all, although I haven't worked out the nits yet.

As I recently mused, what I've done is export all the entries into the one large file the system produces. Then I went into Homesite and split it up into 100-post pieces. Then I FTP'd each piece one at a time to the /import directory on the new system, running the import function each time, and then when they were all there I rebuilt the site (rebuilds on the new ISP are MUCH quicker than on the old). In theory I could have used the MT admin interface to upload the files, but there's apparently a bug in it because despite saying that the import was successful, it obviously hadn't worked.

Meanwhile I'd manually scrolled through the pages of each individual entry to figure out which IDs were missing. This wasn't as tedious as you might expect... Then before I uploaded the export files I inserted dummy posts in the gaps. This, too, wasn't quite as tedious as you might expect, and it did give me a chance to fix some of the bizarre punctuation that had gotten into my posts during the last upgrade. I don't know if I caught all of it, but I caught a lot.

But I'm not out of the woods yet. For one, I still may have gotten out of sequence. All it takes is one extra or too few dummy posts and the whole thing will need to be redone. And to redo it I think I'll have to reinstall MT all over again. Plus I noticed that there are problems with the site templates over on the new system, so that will take some troubleshooting (e.g., the front page didn't rebuild to display any content).

So I think I will semi-lift my content freeze while I work this out. Comments will remain off because I can't limit them to recent entries (in theory there's a way to, but that's not what I want to devote my energies to figuring out right now) but I may keep posting. I'll just export and import the new entries when I've got this all ready to go.

All but the last 50 or so posts have now been imported into the new system. All the archives have been rebuilt, and all the URLs seem correct. Yay!

I'd had to redo it - it turned out I was missing two dummy posts the first time - but I was able to figure out which ones, and redoing it did not require a full install as I'd feared. I was simply able to delete the MySQL database and recreate it. Annoyingly this meant I also had to redo some settings and replace my custom templates, but I guess that wasn't really too bad. I now know what I'm doing, which makes this whole enterprise much less scary. Of course it still takes time to do.

One of the complicating factors was that I never understood what was going on with the database under the previous set-up. Between cryptic MT 2 documentation and really difficult database administration on the old system (itself hobbled by the fact that certain databases were apparently not available on the machine my account was on...) it was a miracle my blog worked at all. I never understood why it did, but I decided not to worry about it... But the new ISP has a nice web interface for setting up the MySQL database and some instructions for how to do it for MT, so from here on out the upgrades and such should be much easier. And, as a bonus, I now can administer my old comments, which I'd lost control of on my last upgrade due to the database weirdness.

I think the only thing now left to do is throw the DNS switch, although I may let that sit for a bit while I pull myself together... What will happen when I do it (I think) is that eventually when you go to cathygellis.com you will no longer end up here (on the old site). You will end up on the new site and not see the blog. When this happens, because the DNS will have rolled over successfully, I'll have to change some settings in my config files to make it show up (my new installation is currently all pointing to a temporary domain name). I don't think I can do that beforehand though; weird things were happening when I had the new set-up point to cathygellis.com before it actually was on cathygellis.com so I think I'll need to be patient.

Gosh I hope this works...

Having now pulled myself together, it's time to switch ISPs. I think it's just a matter of changing the name servers with my registrar and waiting. At least I hope that's all that's involved... If all goes well, the next posts will be in the new home.

The blog appears to be working on the new site. But not the comments, and I have no idea why. Also, the index page at cathygellis.com seems a bit off. Again, not sure why.

Ah, the mysteries of web maintence...

Edit: Fixed the comments. Except for reasons I don't understand but don't want to worry about Fishbane's comment didn't seem to make it in the export. Oh well.

Otherwise as far as I can tell everything is working. (And working much faster than before!) But please go ahead and try to break it. And if someone wants to send me a trackback, I turned them back on so it would be nice to see if it works...

It looks like I will finally become a lawyer in January. So it looks like I may need my new blog around then too.

In anticipation of this change, I wanted to solicit readers' feedback for what should change - or stay the same - in the next incarnation. I'm currently toying with using the "extended entry" area to keep my long posts from swallowing up the front page, and new categories with separate RSS feeds so that people can subscribe just to the bits they find interesting. (While I think that means people would miss some good stuff, I think I'd rather have them miss a little bit of good stuff than not read any of it at all.)

Anything else? Look and feel-wise? Content-wise? Speak up now, or you don't get to complain later ;-)

Even though my "great change" is done, who are we kidding - it's still continuing. And, anyway, I'm not ready to roll out a new blog yet, so we'll just have to put up with this one for a while longer.

For those of you who like to read my blog in the middle of the night, or from obscure timezones (hi people in Japan!), my site will be down overnight between Friday and SaturdaySaturday and Sunday due to electrical maintenance where my ISP houses its servers. So while it's bad to be down, it's great to a) know about it in advance, and b) not to have to fix it myself... Presumably everything should work properly once they turn all the systems back on.

Anyway, I mention this so no one panics if my site is unavailable for a while. I know it's like crack and you just can't wait to get your next hit, but consider it practice for the upcoming week when I'm locked away doing the bar and likely won't be blogging anyway.

The flurry of recent posts is due in part to the fact that I must send my computer in for repair today. It's not quite dead yet, but if it doesn't receive medical care soon I fear that might change. Do you remember those can-like toys from when you were growing up, which when you tipped them upside down it would sound like a cow mooing? Well, my laptop fan is making the exact same sound...

It's scheduled to be picked up shortly, and then I'll be in for a few days to a week of laptop withdrawal... I'll probably be able to get online here and there while it's gone, and I also have Internet access on my phone, so I won't be completely cut off. Feel free to send any emails you were otherwise inclined to send, but note that the Treo interface is kind of cludgy so if I don't respond right away it's probably because of that, and not (necessarily) because of something you said...

Edit 3/29: It's back! Props to IBM (or Lenovo, or whoever they are...), their turn-around time is really excellent. I thought I wouldn't have the machine back until Monday, but it's Thursday night and apparently it's been back since this morning. Considering that it only got sent out Tuesday late afternoon, this is pretty impressive.

Oh, and it seems to work as well...

It had been quite some time since I'd updated my blogroll, so I took care of that just now. In the process I also explored better ways to maintain it in order to avoid the staleness problem in the future.

I pursued two solutions, both of which were designed to integrate with Bloglines, which I currently use to read my RSS'd blog subscriptions. Not all blogs have RSS feeds, but there's few I read regularly that don't offer them. It's too big a pain, in my opinion, to have to separately remember and reload each separate blog. With RSS I can aggregate all the blogs I follow into one place and be notified when there's updated content to view - and often have that content brought to me in my reader as well. It's the only way that reading many blogs is manageable, and since I'm currently reading 70+ it's rare that I will take the trouble to read any that don't offer a feed.

The first solution was a blogroll plugin for MoveableType. I got it to work, but it wasn't as nice as I'd hoped. For one, it didn't import the descriptions of each blog I'd earlier laboriously typed into Bloglines for each blog link. For another, I didn't seem to be able to easily and efficiently sort the links as they displayed on my blogroll. Not that this was a show-stopper, but the links generally sit in Bloglines in alphabetical order, but once imported to my blog they displayed in reverse alphabetical order, for reasons I wasn't able to determine. More irksome, however, is that I don't think the link list can automatically refresh itself. I'm often adding and deleting blogs from my Bloglines reader, but I'd have to manually clear the links in my plugin and then re-import my Bloglines subscriptions to keep the blogroll updated, which isn't a huge improvement over the previous status quo that also was very manual. Furthermore, the plugin's import feature choked on a few subscriptions, so it ended up being fairly laborious on its own to delete the bothersome subscriptions from Bloglines, import everything, and then remember to reenter the offending subscription feed back into Bloglines.

After I wrestled around with all that I then noticed that Bloglines itself offers some code that can be put in a website to populate a list of links, and that's what I'm currently using to generate my blogroll. It, too, isn't perfect, mostly because it also doesn't include those descriptions I'd so laboriously typed in... But at least the list stays fresher, as I believe it will always produce a current snapshot of my Bloglines subscriptions.

At some point perhaps I'll categorize them into folders, which might serve reasonably in lieu of the wayward descriptions. Still, I don't understand why Bloglines even bothers to tempt me to enter them in if ultimately they serve no purpose.

In any case, the new and improved blogroll can still be found where the old one was, although at some point I may pull it out into a separate file, which I'd started to make when I was working with the plugin. Either way, just follow the link from the front page and you'll find it whereever I've put it.

Edit 5/6: Well, we currently have categories. Enjoy them while they last (and before I change my mind about them...)

I'll need more time to whip up the next few posts, but in the meantime I thought I'd tide you over with some words I stumbled upon in a case I was reading yesterday:

...to mulct a necessitous borrower.

The rest of the sentence wasn't much better than this end part either, having dragged on and on for several lines before reaching this lexicological climax. I think the case was ultimately decided in favor of the borrower, although with writing like this it's kind of hard to keep score...

My blog is like a garden, which I carefully cultivate, water, weed, and otherwise attentively tend. But I think I may have to let it go to seed for the next few weeks while I head into the bar study homestretch because I need to take it off my list of things to worry about. I do worry when there's not fresh and/or substantive posts, but I need to give myself permission for that to be ok for a while. Of course, the way it's worked in the past, saying things like this has generally uncorked a slew of further posts, but in case it doesn't work that way this time I wanted to beg readers' forgiveness in advance for any subsequent lack of content.

The bar will happen July 24-26. Then when it's over I will jump on a plane to New Jersey for a week to take my CLE's. As of Aug. 5, however, I get my life back. Hopefully I will have managed some blog posts before then (particularly once the bar is over), but for non-RSS readers who wish to not reload the page obsessively between now and then to check for new posts, please do return after that.

Now that I'm starting up again with the regular blogging, I'm going to risk everything by trying to upgrade the software. We'll see how this goes... (The problem is that I do this so infrequently I forget everything I learned the last time.)

Edit: It would also help considerably if the documentation could make up its mind on what the upgrading instructions actually should be. The website says one thing, but the readme file says another.

Edit #2: OK, it's done, I think, three hours of frustration and bitterness later. Given that the license for Movable Type is free I guess I can't complain too much, but geez it's poorly documented. And what makes it extremely annoying is that one of the features Six Apart bragged about when pitching the upgrade was how well documented it was. I might not have cared so much if they hadn't gotten my hopes up...

I also think it might have a bug, because the wonderful comment-spam blocker I was using no longer seems to work. Which is distressing, because I'm not keen to have to delete spam again. So stand by, as I may have to turn comments off and on while I work this out (although at the moment they're still on).

I'm also so far not crazy about the upgrade because it affected the UI of the administration screens. I suppose I'll get used to them, and apparently they can be modified, but for now they just make me cranky...

Anyway, so far, except for the comment-spam thing, it all looks ok to me. Please let me know if you discover otherwise.

Edit #3: By the way, does anyone know how to make MT 4.01 automatically send out new posts as emails? I thought this version could, but I can't see how.

Edit #4: You know, I thought I had it figured out. I held off upgrading for a month to wait for all the bugs to be worked out. Unfortunately it seems like it would have been a much longer wait... Other parts of the system are also not working as intended. They won't really affect me, but it's really annoying since it means I'll probably have to do this again sometime soon. In any case, I do not recommend upgrading to anything higher than 3.3 for now (although the other, later 3.x versions are probably fine).

Edit #5 9/24: I know what I was thinking when I decided to upgrade. Six Apart promised all sorts of features I wanted to have for some other projects I'm working on. But it was so not worth it since it seems with the upgrade I've lost functionality I already had. It seems to all run slower, and the worst thing is that I'll have to turn off comments until I can get that anti-spam program working. Hopefully that will be soon, but I really have no idea, dammit.

Edit #6: In the further adventures of Cathy banging her head on the desk, I think user error may have contributed to the anti-spam plugin not working... On the other hand, if it weren't for the poor MT documentation that might not have happened. And I still think there is a significant bug in the comment part of the system, as its behavior is not what I'd expect it to be. For instance, I'm trying to turn comments back on, and yet that's not actually happened...

Edit #7: This was a good system: bitch and moan, then solve the problem... Seriously, it was actually constructive, as the venting helped relieve the pressure in my brain so that there would be space to reflect on screens that I'd previously seen such that I could derive clues to possible solutions from them. That's how I solved the plugin problem, by remembering something I'd seen on a screen that on further reflection I realized wasn't quite what I should have seen had things been working properly, and I used a similar mental mechanism to figure out how to finally turn the comments back on right now.

It now appears that everything is working (yes?), including the amazing spam filter and the comments themselves. I do, however, still have issues with the MT software. The documentation is too vague/inconsistent/obscured to be useful, it seems much slower than the previous version (3.3), and the general design of the administrative backend leaves something to be desired as well. I was able to figure out what was going on with the comments, and maybe the weirdness was due to the upgrade and will never be an issue again, but somehow I doubt it. There seems to be some poorly thought out behaviors stemming from these controls, where checking or unchecking certain boxes reverberates throughout the site in ways one wouldn't necessarily anticipate.

In any case, however, it looks like I can stop with the swearing for now and move onto writing more regular prose. Yay.

A few weeks ago I got a notice that my ISP would be doing some maintenance Friday night, which would make my site unavailable. I haven't heard anything more about it since, but if Friday night it's suddenly not here when you come visit, that'll be why.

I have a new blog! This shouldn't come as too much of a surprise, as I've been intimating for some time that it was in the works. For a while now I've felt a bit of a slave to my narrative, "The Great Change," but as long as there was more to tell, I was committed to telling it. But now that the story has been wrapped up it's a good time to move on and spread my writing wings in other ways. Don't worry, it'll still be me and my voice over there, but hopefully sounding like someone with the ethos of a trained and licensed legal professional and less like the bewildered law student I no longer am.

I will not be deleting this blog. In fact, for as long as I can (i.e., I fear the next upgrade...) I plan to keep it mounted on the blogging software, meaning that comments will remain open and functional. Conceivably I may also post to it if I decide to write any sort of "Great Change"-ish wrap up posts and whatnot. However if I do I will link back to here from the new blog, so it's only necessary to check the one site for new writing.

If you have me in your links or blog roll please note the changed URL. The new blog is at http://www.cathygellis.com/soi/, or, alternatively you can link to http://www.cathygellis.com/, which will (soon) be set to redirect to the new blog.