Thunderbird Workaround for RSS

I was hitting a bug with T-bird’s RSS reader, which I think I have now finally worked around. I have not been able to add new feeds for some time; and previously I had hit a bug where my feeds stopped updating. I fixed that by (wrongly) deleting the feeditems.rdf file from my T-bird profile. That seemed to cause other problems that I don’t officially claim to understand.

Today, I exported my feeds, created a new RSS account, imported my feeds to that, and then deleted my old RSS account. This works brilliantly and I was able to add new feeds immediately to the new account. (Including a feed that required HTTP Basic Authentication, which I hadn’t been able to use at all previously)

It’s worth mentioning that I had tried out ThunderBrowse as a way to work around the HTTP Auth problem I was having, but it seems not to handle HTTP Auth requests at all. Too bad; ThunderBrowse could be really neat with a little bit of massaging; I hope it gets it.

checking my work

So I have been using this little tool for a while to look at the output of “cvs diff -up8″ as HTML before submitting patches to bugzilla. It seems to be working pretty well for me, so I thought I’d go ahead and make it more widely available. I would love to get feedback and/or patches for it. I worked up some fixes today to make its output validate as XHTML 1.0 Strict. Since I can’t upload anything but images, I’ve hosted it elsewhere. And yes, I realize it’s relatively ugly perl-code.

alas!

I really liked the Penn Jillette radio show. Too bad it’s been canceled.

Manipur, eh?

Apropos of nothing, this article from the Economist is a fascinating read.

why this crazy thing works

It’s addictive.

The high comes (or at least, the best hits are) when two conditions are met: 1) something you do benefits someone else, and 2) you know about it.  Today, for me, it happened to hit me when a random comment I made in a random bug more than a year old helped someone else fix the bug.  Yeah, that’s right:  I didn’t even actually fix the bug.  But I helped someone else do it.  And yeah, it’s not a bug the fixing of which will protect anyone’s credit-card numbers or identity, but somehow it’s still a pretty good high.

in other news

Y’all probably already saw this; it’s so 24-hours ago.

Kozilla

Reading Gen Kanai’s blog-post here makes me think we have a real opportunity in a market we haven’t cracked yet.  What do we need to do to make the Korean SEED Active-X control work in our browser without introducing all the other mayhem which comes with Active-X?  I looked at the source for the Active-X control in our tree and it looks as though some thought has been made for restricting (whitelisting/blacklisting) controls, but in my cursory examination I didn’t find the actual code that uses the preferences documented for this.  I’m not very familiar with this code.  Who is?  How good is our Korean localization, in general?  Am I wrong in thinking this is a very big, very obvious opportunity?