updates

so, where to begin - it's been way too long since I wrote anything down; my apologies to anyone out there reading but I haven't had nearly as much internet access as usual lately, and I can't seem to find any decent blogging software for OS X so I may end up having to write my own.

in other news.... Steph has decided not to move out here. shocking, I know. it's actually kind of sad, because she's really cool, and I was kinda looking forward to her moving out here. on the other hand, it's rather freeing, and I realized the other day that I'm officially more free right now, at this very moment, than I've ever been before in my life. I have no responsibilities to anyone, really - I have no obligations to maintain, no relationships holding me down or keeping me from doing what I want, and it's sort of a scary place to be. hopefully things will firm up a bit soon; it's an interesting place to be at, though.

have been going to interviews and submitting the resume at tons of places up here. no solid results yet, unfortunately.


qotd

today's quote (from Tia):
"hell if i would have known that you were moving i would have handcuffed you to a bed and stuck you in a basement somewhere so you couldn't leave"

good to know that I have friends who would abduct me and keep me in a basement. definitely good to know.


interviews

I went to Boston on Wednesday last week for an interview that I had at a community health center in the city. I got a call the same day from Red Hat asking if I wanted to come in for an interview the next day, so I told them "Of course!"

the interview went great! I had the most fun I've ever had interviewing. I got to meet a bunch of cool guys and I had a blast chatting with them, about all sorts of stuff. they had me show up at 10AM and I was supposed to be done by 3, but they kept me until a little after 4. which hopefully is a good sign, but I don't want to get my hopes _too_ far up.

the hospital was basically a dead end, though. they don't have any positions for the IS department, but they swore that they would call me as soon as they do. they did seem to be pretty impressed though, so I think it went well even if nothing comes of it. it's experience, anyway. which is always good.


in new york

I'm finally in New York, and I've actually been here for a couple of weeks now. been a while since I updated the blog so I figured "what the hell" and decided to go ahead and post a bit of info.

the job search hasn't been too promising so far, but Syracuse is gorgeous. I really love the area, and the fact that snow is all over the place probably has something to do with it. everyone here thinks I'm insane because I love the cold; maybe I am actually crazy, but I still get a kick out of it.

haven't had much time to hack on KDE lately, what with trying to find viable employment. my aunt has this great idea that I should be the Easter Bunny or one of his assistants; I'm really not too into the idea personally, but I do have to admit that it'd probably be pretty funny if I had to resort to that. I mean, it'd suck terribly for me of course. but it'd still be hilarious, and maybe in a few years I'd be able to laugh about it. maybe.


disappointment

So, I have had a lot of respect for the GNOME hackers for a long time. I have been incredibly happy that the core hackers in each camp have got along with cheerfulness, decorum and mutual respect - even while some overzealous members of our user communities have flamed and bickered, generating this idea of "The Desktop War".

But this week, a bunch of actual GNOME developers - not random gimps being idiots - have acted like children and made everyone working on the Linux desktop look like a bunch of juveniles. I'm very disappointed.

How do they expect corporations to take Linux desktop efforts seriously with a release name like "That and a pair of testicles"? Some people have mentioned that this won't reflect badly on KDE since GNOME and KDE are only related by virtue of being alternatives to eachother; they might have a point, but in reality, nobody in the Windows world knows the difference between KDE and GNOME and this sort of crap makes Linux desktop acceptance that much more difficult for everyone involved.

Very disappointed.


oh how I hate gssapi

so now that I have a local kerberos server, and it hands out tickets like a champ, and life is good, the next (logical) step is to want to have single-sign-on for things like (say) my email.

KDE has a custom ground-up SASL implementation that supports LOGIN, PLAIN, CRAM-MD5 and DIGEST-MD5, but not GSSAPI (which is a layer on top of Kerberos). I took a look at it and decided that I could implement a GSSAPI function for the KDE SASL implementation. I had no idea that it'd be so damned frustrating. why is GSSAPI so complicated, and poorly-designed to boot?

if you think I'm joking, or complaining about nothing - the main function, gss_init_sec_context, takes THIRTEEN parameters. that's a lot of margin-for-error. one would think they might use custom data structures, ones more complicated than the standard struct with a void pointer and an int to indicate the length of the data, but no. of course not.

oh well. when I'm done, KDE will have a GSSAPI implementation, meaning that it should Just Work (TM) with any Kerberized service that uses SASL. Namely, this means IMAP servers and probably a few SMTP servers - having single-sign-on for these services will be great.


mmm. kerberos.

so I finished setting up a working LDAP server here at home. with Kerberos, for that single-sign-on goodness. I can see why people dig this. I can also see why people fucking hate it. awesome features, complete and total pain in the ass to set up. honestly, I think I probably would rather have installed openBSD, and that's saying a lot.

but now that it's working, and I have it set up, I am a golden god.


orkut

everybody else is blogging about it, so I guess I'll join in too. orkut is nifty. I don't have five thousand friends, but I think that maybe instead of being obsessed with collecting as many as possible I'm going to just use it to keep in touch with the ones that I do have. well, the ones that are on the service anyway.

other than that, not much news. been listening to Massive Attack's 100th Window lately. good stuff. really starting to dig Thirteenth Step, as well, for some reason. I didn't like it that much when I first heard it, but it's grown on me quite a bit.


resolutions

it's been almost a week since my last blog! damn. I resolved to make sure to update this more often. not even four weeks and I'm already falling behind.

yesterday was fun. Caitie, Nuge, Brandi, Josh, and I all went to Red Sea. Kevin was over there (surprise surprise!) and Cliff showed up eventually, as did Steph, It was like a party or something, almost. everybody's decided that they're going to throw me a huge going-away party, although the little details (like "when" and "where") have yet to be decided. sounds like good fun though.

Steph took advantage of Brandi being there, and apologized to her. Or so she says. haven't heard Brandi's side of the story yet. still, it's nice to hear that Steph's trying to be less caustic. she got me a gift yesterday, too, completely unexpectedly. the Onion calendar. hooray! new Onion every day for the rest of the year.

that's about all. the last week hasn't been that interesting. tonight should be, though. Caitie and Nuge and I have finally agreed to do our intervention with Jessica. no idea how that's going to go, but ... it needs to be done. Jessica is a really great friend, and an amazing woman, and she deserves far better than what she's currently getting. anyway.


jessica and intervention

the intervention didn't happen. Caitie got cold feet, chickened out, and didn't even show up until twenty minutes before Jessica left. I feel like shit.

Jessica really is too good for her boyfriend. that's really all there is too it. I wish I could have convinced Caitie to go through with it, but my persuasive skills aren't what they used to be, I guess. oh well... I tried, and I failed. it really does make me sad though.