My problem with pagination

I recently got into a discussion about a comment I made on a blog post two years ago. Granted; my comment might have come out a bit harsh (for which I apologize) but there was a point to be made. In this blog post I'll try to explain what I was (and am) talking about and what my issues were (and are) with the proposed solution to the problem at hand: pagination of large chunks of data / resultsets.

Ah, another CAPTCHA for me to answer!

"A CAPTCHA is a program that can tell whether its user is a human or a computer. You've probably seen them — colorful images with distorted text at the bottom of Web registration forms. CAPTCHAs are used by many websites to prevent abuse from "bots," or automated programs usually written to generate spam. No computer program can read distorted text as well as humans can, so bots cannot navigate sites protected by CAPTCHAs."

_{Source: http://www.google.com/recaptcha/learnmore}

Are you using DNSStuff.com? You shouldn't!

I have been using LastPass for a while now and I was very happy to find out they now also offer two-factor authentication. This has, as far as I know, been available since ages but you had to use a Yubikey. I don't know when they added support for Google Authenticator but they did. And since I have been using this for a while for my GMail and Google Apps accounts I was glad to find out Lastpass supports it too.

WebSphere MQ Reason codes

IBM has worked hard to obfuscate exceptions by not providing any specific info in XMSExceptions and using the unconventional "LinkedException" in their WebSphere MQ classes. Why they didn't use the InnerException is beyond me.

This page can be used to look up "ReasonCodes" (which is all the LinkedException provides in XMS.NET). The links in this page all lead to the specific help-page.