Since when does the "next >" button = "<" ?

I'd have to say it's "a" - but not on the first page - that works fine, It's when you're on subsequent comment pages.

Okay - you're looking at an item on Gizmodo - let's call it "Item B" - and you scroll down the page's comments. At the bottom there are page numbers when the number of comments surpass one page (2, 3, 4... etc)

Then you click on page 2 or page 3 or whatever, anything but page 1 (under Item B) THAT is where the next > nav button doesn't work right.

It's like it's working backwards - it takes you to the previous item instead of the next one.

(In other words, it takes you back to Item A instead of to Item C)

I hope that makes sense!

I'm using this post as an example because it has over 600 comments
http://gawker.com/5051193/sarah-palin...

I'm currently on page 13 of that post and if I click the next, it works just fine for me.

Is it possible you're confused about the results? The numbers inside the brackets, ie, [321..340 of 404] should tell you where you are.

Or am I still confused?

Yes, you are still confused.
(I'll assume part of the blame for that, since I'm the one trying to explain)

The "next >" button at the bottom takes you to the next page of comments and works just fine.

(Just as you've indicated)

It's the next button at the TOP that doesn't work correctly when you're on subsequent comment pages.

When you're on page 13 (per your example) and you scroll back up to the top of the page and click on "next >" it takes you back to the previous item - it should take you to the next article.

(I think we're confusing article pages/comment pages, and top/bottom "next >" buttons)

Step by step:
1. Open any article with more than one page of comments
2. Scroll down to the bottom
3. Click on (comment page) 2
4. When the page loads, click on "next >" at the TOP of the page
(To go to the next article, not the next page of comments)
5. You'll end up on the previous article instead of the next one
(Click on "next >" again and you'll be back to the same article)

Now I know! This is indeed a bug. We're working on it.

Good luck and thanks for your patience with my difficulties explaining the issue.

We fixed that bug :)

Yes, I noticed this morning! Nice work!