Today I resolved a bug lurking deep within the workings of my Chlorine Boards framework and I have twitter to thank. When I made a blogpost about how drug use is not abuse a person following me on twitter immediatelly picked up on the post, gave it a read, retweeted and wanted to leave a comment. But couldn’t. Immediately @OneLuvGurl tweeted to me about how she can’t comment.

We tweeted back and forth for about an hour about the issue when I finally just asked her to send me the comment and I’ll see what I can do. It turned out that it was indeed, as I feared, the comment’s fault. So I started poking around until I found what was wrong. The comment was too long … but how can this be? The darn thing isn’t very long at all.

Two hours later I finally found out what the issue was and was able to resolve it. It would appear that three, or was it four, years ago I’ve made a terrible design flaw – I decided to use GET requests for ajax instead of POST requests. Since GET requests have a limited length this was naturally a disaster waiting to happen and I’m surprised the issue could go so long without being noticed, but I’m glad it’s resolved and I’ve already updated all the websites running on Chlorine Boards with the surprisingly simple fix.

This event just goes to show how much more than just status updates Twitter has become and just how awful bugs can be.

---
Need a freelance developer? Email me!

You should follow me on twitter
Follow @Swizec  Subscribe to RSS