by publius
We're currently working to get rid of the comment pagination (Typepad suddenly decided to limit the number of visible comments at any one time to 50). I put in a request, and then noticed Hilzoy had already done so. In short, we're working on it, and we'll get it fixed.
The Wrath of Hilzoy vs. the Complacence of Six Apart...
Im a just universe, Hilzoy would win. This is not a just universe. Sorry, I think the only way this is going to get fixed is to port the blog to working software.
Posted by: Jesurgislac | October 19, 2008 at 04:54 PM
Which, BTW, I've offered to do multiple times for free.
Posted by: david kilmer | October 19, 2008 at 05:08 PM
"(Typepad suddenly decided to limit the number of visible comments at any one time to 50)"
Sorry, you're saying that Eric was wrong when he announced that they were limited to 25, and then after I pointed out that it was reported that the limit could be 50, and Hilzoy announced that she was switching it to 50, she was wrong? That none of that happened?
It seems that either Hilzoy and I are lying, or your account is false.
In fact, Typepad announced a year ago, as documented by Eric, that they were move to 25 comments per page, and paginating, and then they implemented it here, and then subsequently we had the previously linked discussions, and Hilzoy upped the comments limit to 50. In reality.
When you give versions that are made up, and apparently are vague guesses, which contradict that which we know, it kinda undermines your credibility as a reporter of things that happen.
Posted by: Gary Farber | October 19, 2008 at 11:18 PM
Quelle outrage?
Posted by: Gary Farber | October 19, 2008 at 11:41 PM
gary - that was uncalled for. i don't know what exactly about me pisses you off so much, but it gets tiring. i happened to miss this in the earlier thread -- i'm sorry. jesus christ.
Posted by: publius | October 20, 2008 at 12:15 AM
plus, what you're saying is inaccurate. typepad may have announced it a year ago, but they just recently implemented it that here.
And when I say "suddenly," I wasn't staking my journalistic credibility on the fact that it had in fact happened in the last 10 seconds, as opposed to two days ago.
your response was completely -- completely -- disproportionate to what i said.
I mean, i expected to get some comments on this, but not "you have no credibility and make stuff up". on a site update post.
Posted by: publius | October 20, 2008 at 12:38 AM
seconded - Gary needs to get over himself.
Posted by: sydneyos | October 20, 2008 at 12:40 AM
Can I second moving the blog? Everywhere else I hang out can at least prevent italics
Posted by: Mike Schilling | October 20, 2008 at 12:57 AM
from leaking into the next comment
Posted by: Mike Schilling | October 20, 2008 at 12:57 AM
Enough said
Posted by: Mike Schilling | October 20, 2008 at 12:57 AM
Drat This is harder than I thought.
Posted by: Mike Schilling | October 20, 2008 at 12:58 AM
Good?
Posted by: Mike Schilling | October 20, 2008 at 12:58 AM
OK, if this doesn't workI give up.
Posted by: Mike Schilling | October 20, 2008 at 12:59 AM
Posted by: david kilmer | October 20, 2008 at 02:05 AM
Ka-ching. Damn, I'm good.
Posted by: david kilmer | October 20, 2008 at 02:06 AM
What is the magic incantation? The usual terminator (LeftAngleBracket-slash-rightAngleBracket) didn't work.
Posted by: Mike Schilling | October 20, 2008 at 06:01 AM
I looked at the page source and saw that it wasn't keeping your close italics tag. So I closed both span and div, then closed italics.
Typepad apparently does some parsing/scrubbing when you post.
Posted by: david kilmer | October 20, 2008 at 08:53 AM
Of course, if you figure out what Typepad is doing and manage to fix it, will you please please please tell Fred Clark at Slacktivist?
Thanks!
Posted by: Cowboy Diva | October 20, 2008 at 09:22 AM
I looked at the page source and saw that it wasn't keeping your close italics tag. So I closed both span and div, then closed italics.
Thanks for the advice, David. I'll bear that in mind for future reference.
FWIW, before the new "we page your comment threads" software, a multi-repetition of the close italics tag would generally work just fine. *sigh*
Posted by: Jesurgislac | October 20, 2008 at 09:45 AM
Which makes it all the more annoying that in the parsing it doesn't notice the unclosed tags and close them. What's the point of "upgrading" the HTML handling without doing that?
Posted by: KCinDC | October 20, 2008 at 09:55 AM
Correction after a bit of experimentation: close div, then span, then italics (twice for good measure).
What a mess that makes of the page's validity, though. It's a shame.
Posted by: david kilmer | October 20, 2008 at 10:43 AM
IME it's rarely necessary to do more than (repeatedly) close the italics tag. The span and div closures are probably redundant.
Posted by: Anarch | October 20, 2008 at 04:29 PM
Anarch - it appears that the close italics tags aren't making it through to the page. That's why I threw in the close div and span tags.
Posted by: david kilmer | October 20, 2008 at 08:59 PM
david - just in case we haven't, i want to thank you for the kind offer. it's obviously a big big step -- but it's something we'll definitely think about.
but thanks for the offer.
Posted by: publius | October 20, 2008 at 09:58 PM
in fact -- if you'll email me offlist (at the obsidianinfo address), we can discuss what would be involved, etc.
i don't think people are opposed to doing it -- just worried about bugs, pain-in-the-arseness, etc.
Posted by: publius | October 20, 2008 at 10:18 PM