There may be a problem extending the voting because the poll was set to automatically close. Ursa is working on it, though, and in a little while we will know if he succeeded in keeping the poll open for another day.
Don't count on the software cooperating, though, so if you are still contemplating which story to vote for, you may have only nineteen minutes left.
The poll will now close 24 hours later than scheduled, just in case someone tried to vote earlier and couldn't (and isn't around until after midnight tonight).
At the moment, the closing time is slightly earlier than that -- I had to change the time before it closed for good today -- but I will change it to the correct time (23:59 on the 29th of March) in about 12 or so minutes.
Well, the Chrons died again as he was making the changes. And now he's undoubtedly gone to bed. Stay tuned to find out what the final closing time is. (Or better yet, vote while the site is up and you can!)
@Parson Nowadays software is built on OOP (object oriented programming) paradigm. Because of that, a page request like this one, is going to be piece together from tens to thousands small pieces of code. The actual code is separated in files on the disk and reading each one of them for every page request, consume a lot of server CPU time. Multiply that with thousands of visitors and you are going to clog the machine to the point no request can be served. There are many other factors, but they can be tweaked a lot easier.