The >> posting regex being used right now matches every comma in an anchor, even if it's at the end and doesn't mean anything. This screws up some sentences a little:
"What this all really means, though, is that you, >>1, should just stick with today's special."

I can't get one to work; it seems to need at least extended regexp syntax, and I don't know enough of that to do something useful.

Well, that's ugly, but at least it doesn't break things entirely, since the link to 1, does work... But let's look at the regexp. I'm using this right now:

/(?:[0-9\-,lrq]|,)+/

One quick but slightly clumsy solution would be something like this:

/(?:[0-9\-,lrq]|,)*[0-9\-lrq]/

That would require the last character to not be a ,.

Shamelessly bumping this to promote further improvement of navigation/linking & sucking up to 0ch! n, next100/previous100, etc. （n´✪ω✪n）

See also: http://wakaba.c3.cx/sup/kareha.pl/1099328662/21-22