Radio, YACCS blah via my own stuuuupidity

My double decoding fix stopped working, if it ever worked. I changed it to not call xml.entityDecode at all, since I don't think it needs to (why would it need to call that on something it just xml.getValued?), but unsubscribing and resubscribing to my feed didn't show it worked. I'll have to dig around more to find it.

At least, if this doesn't work: <p />

Meanwhile I started working on a WYSIWYG HTML editor widget for Mozilla. But don't tell anyone--it's just between you and me, OK?

Also, I discovered a few days ago that YACCS' post ID numbers have a maximum length, namely ten digits, which is inconvenient since I recoded stuff to use raw dates for them. Like, if I posted this item when the weblog post page loaded at 8:28:37, my item template would build the comment link with a post ID of 20020709082837, which is 14 rather than ten characters. YACCS reads the post ID as 2002070908 instead.

Anyway, all that means all the posts I post in a single hour that have YACCS comment links are sharing the same YACCS thread. It wouldn't be so bad except all Kit users who followed my #itemTemplate directions for making safe permalinks and comment links (and use YACCS, at least) are in the same boat.

Luckily afaik the number of Kit users who made the template changes for Radio to the Past number roughly zero. I'm not sure whether I'd like to be disabused of that notion or not.