Nginx

Must play with this HTTP server/load-balancer/mail proxy/bundle of awe­some some­time soon. Looks like a pretty awe­some option for VPS envi­ron­ments and other places where there isn’t heaps of spare resources going around! My cupboard-bound SSH oasis and occa­sional web­server is, of course, a likely can­di­date… but I’m a tad con­cerned I’ll screw myself over with PHP. Not because it par­tic­u­larly gets used for that (there’s like… a few wikis and a hand­ful of lines of PHP code eas­ily replaced by some­thing else that get semi-regular atten­tion) but mostly for the “just in case” I wanna test run some­thing. And yeah, I know, that’s what vir­tu­alised stuff should be for… but I still haven’t quite caught up to that. I’ve got an Ubuntu thing run­ning in a vir­tual PC instance on the com­puter I use most of the time, but it just doesn’t cut it for actu­ally try­ing to test some­thing out with, you know, other users and real Inter­net con­nec­tiv­ity. In other news, can-we-have-IPv6-moar-plx? Just because it’s absurd to have to pay more to run real SSL on ded­i­cated IPs when there is SO MUCH SPACE just wait­ing for us to broaden our hori­zons and start to fill it. I’m not heaps fussed if pre-Windows XP users can’t use it, actu­ally, because they’ve likely got big­ger secu­rity prob­lems on their hands from their network-connected 10-year-old OS than any reg­u­lar web inter­ac­tion is likely to give them, prop­erly secured or not — that is, even if their web traf­fic is secured, their desk­top is prob­a­bly a bot­net zom­bie with key­log­gers and tro­jans abounding.

Rage. Uni. Anger. Blood. Tears. Web applications.

I am about to start cry­ing because of a web appli­ca­tion for the sec­ond time in (I think) as many days. No, it’s not MySpace (it was suf­fi­ciently van­quished after some tum­bling about with pointed sticks).

I sup­pose I should have known bet­ter. Just because there’s no warn­ing, doesn’t mean it’s not about to do some­thing stu­pid. Par­tic­u­larly given the Uni­ver­sity of Sydney’s web team’s fetish for ses­sion time­outs like they’re run­ning some high-grade-cipher-required (they use 256bit SSL certs for every­thing) nuclear launch sys­tem. Only not, because Kim isn’t a stu­dent. But, then again, even if he were the usabil­ity issues would prob­a­bly be man­i­festly more suc­cess­ful than the UN/non-proliferation treaties.

What­ever. So I spent too long ago­nis­ing (and I do mean ago­nis­ing) over sub­ject selec­tion for pre-enrolment (I know, I don’t need to worry, I can change it later — what­ever. I’m hav­ing a stress­ful day and for what­ever rea­son am choos­ing to get this out of the way now so that I don’t expe­ri­ence this later. That’s the the­ory.) and then the mon­ster ate it all. What really [exple­tive] me is that when I finally made my last choice, I went and entered it then its bloody popup-confirmation sys­tem (which, inci­den­tally, is quite usable but I despise it on prin­ci­ple) still worked. Sub­mit it? Sorry, you’re not logged in. Log in? Their [another exple­tive] auth proxy doesn’t even pass the right GET vars (strips ? and pos­si­bly amper­sands, too, it seems, so I got a lovely 404 page), let alone every­thing I just POST’d. Talk about stab­bing users in the back.

Words can­not express how irate I am right now.

To top it off, I’m increas­ingly con­vinced I some­how man­aged to screw up my whole degree pro­gramme whilst still in first year Arts. No, I didn’t think that were pos­si­ble, either. I am ade­quately pissed off with the world to leave this post here.