powdarrmonkey

There's coffee on my monitor now

Thanks Well I was waiting for a slot in the banner calendar, but as there are moustaches on it today I guess I've missed it again... On a rock by the sea, in the sunset. Bliss A little under a year, I think (though she knows better than me - maybe a fortnight short of?)

That was all really

There were similar problems in the West Midlands on Thursday morning.

Ack. .

It's O2 exclusive, and they want up to £159 for contract or £380 for Pay and Go.

Inexperience, inappropriate tools and a framework that tries to know best. Disastrous combination.

Nobody can speak for them, you must ask them what their stance will be.

For your convenience:

No, he's written an installer that relies on a mouse.

WTF? you're installing GUI stuff on a headless machine? Whyyyyyyy? Anyway, your question can't be answered without more detail.

Ordinary visitors don't capitalise buzzwords (well, except when they're emphasising them...).

You're too late (screenshots).

Try 10300506.

From the PHP manual: There is a very good reason that the original name is not kept: it's an attack vector to overwrite arbitrary files on the server. You should be using

It's a side issue, but it reflects less-than-optimum programming practice. You're inspecting binary data, which you can't add slashes to (funnily enough, it tends to corrupt it) and you should have checked for safety long before you reach this stage - like running it through your friendly neighbourhood virus scanner first It inflates the database unnecessarily, which makes recovery difficult It inflates the indexes in a really ugly way It inflates the binary log file in a really ugly way It's impossible to monitor space use by individual files It's impossible to share files across a cluster or replication partner without massive overhead It's expensive to add large blobs to indexes, and if they're not indexed it's expensive to find them A hit on an image costs you two lookups and two runs of the PHP parser, which is expensive - sending a file to the agent is the web server's job and it does it very, very fast It's impossible to take backups that are not the entire dataset (because your database is a filesystem blob) Your file system can do deduplication far more easily that you can Your virus scanner can't inspect the stored files You should be caching file requests on the server to protect against page refreshes, so you're going to end up storing them twice File systems have strengths and weaknesses. You can't store your files on a different and more suitable file system to your database So don't move them. Not really, you can no longer do incremental or differential or partial backups.

An almost verbatim lift from my own blog (just as well I wrote it...)

Yes, your plan. Do NOT do this, it's a monstrosity. Save the file somewhere (after sanity checking until your hair turns grey, and following the usual rules about not storing a billion files in one directory - you know about that one, right?) with a unique name (try sha1 on the current microtime, that's pretty unique) and store the path. edit: and why the hell are you calling addslashes on binary data? You should have checked what it is and discarded it way before then if it's dangerous...

Osmos (Hemisphere Games Osmos –) It's beautiful, mind-bendingly frustrating, and comes packaged in .deb and .rpm.

In all seriousness, designing your site to be friendly to screen-readers, customised user-agents and so on is very important for accessibility.

Let me get this straight... you ask the amassed holiday experts where to stay at 19:15, and by 19:38 you haven't had any responses so you go ahead and book somewhere anyway? Weird.

.

It looks like it's been generated (badly, it violates several standards) by something rudimentary.

I can't believe anyone would be so naive to think they wouldn't get an overwhelming response for a heavily marketed giveaway, and worse to be so naive as to not even have finished designing them before taking orders. Still, the thing that annoys me most is the total lack of any information from them; instead, marketing emails that they promised I wouldn't get in the first place. Unhappy.