Office Move – still ongoing

Well, Twunty Manager™ made such a cunt-up of the office move that IT-wise it’s still happening.

Last week we ordered two completely new servers to replace the Exchange (non-geeky: email) server, and a new server to hold all the other services that were also running on the old Exchange server, and are thus fucked in parallel with the email problems. Small items such as Active Directory, DNS, DHCP, and a couple of other odds and sods. (geeky readers are now shaking their heads and going “oh, shit”)

This week I’m installing everything on the new servers. Windows 2003 server, and all the gubbins. Exchange, AD, whole bundles of stuff. Then over the weekend when I’m not here, three others (including Twunty Manager™, so I’m not overly optimistic) will be sorting out moving the users onto a new network domain, moving over the remaining/surviving servers onto the same new domain, and then moving it all about so that we can do some maintenance gubbins too. Like moving the development server onto a bigger (and safer) environment.

In short – I’m not going to be writing much here today.


Frustration – Finalé

Well, according to my nedstat page of referrers the script I put in place yesterday to block google’s image search is working nicely, and the count of referrals from that page is coming down slowly. It should be completely off the list by tomorrow, with luck.

I’m still debating whether I do a nice page saying “you’re looking at this from Google, which I’ve blocked. Now fuck off” or just to leave it as a 404 “Page not found”. The 404 error takes up a whole load less bandwidth, that’s for sure. So hmm, not certain yet.

As it is, I’m almost certainly going to get caned a bit on bandwidth again this month, as I’m already at 2Gb of my allocated 3Gb, so the odds are that I’ll go over. After all, there’s still three weeks of the month to go yet. I’m going to keep an eye on what else is referring to d4d™ and see if there’s anything else that needs blocking still. Now I’m happy with how the script is working (oh, and the reason it wasn’t working was because PHP spells referrer differently to how it should be spelt, and I tend to hand-write my code rather than using a muppets guide… Arsenuggets.) I can block out some other things if they’re pissing me off with how much bandwidth they’re hogging. But I think that removing Google’s image search is going to be the biggest saver going.

UPDATED : Yay, it’s now all gone from the referrers. To coin a phrase, “I love it when a plan comes together”.


Frustration – Fixed

Ha! Got it sorted.

Now, I could just send anything from Google Images to a simple “Page not found” error, or I could do a nice explanatory page. What do you think I should go for?

Oh, and if anyone else is interested in blocking Google Images totally, let me know. So long as you’re comfortable adding in a bit of PHP code to your page (I’m not sure how well it would work in (for example) blogger pages yet) then email me and I’ll see what I can do.


Frustration

Every so often, I get annoyed with PHP because somewhere along the line it’s not doing what I want.

Currently I’m working on barring a certain google image search which is screwing me over bandwidth-wise, and I’m getting about 30-40 hits per day from it. It’s all coming via google itself, rather than being a link out – the page first displays the “image” (which was never actually on the site, I just linked to it) and then in a frameset shows “where the image is on the original page”. At which point it downloads my full archive page. Which is – needless to say – bloody big.

So I’m trying to find a way to stop it from doing so, and at the moment I’m really not succeeding. In theory it should be working, but it’s not doing so.

So I’m pissed off.


25th Title

I’ve just completed my 25th book this year – and I’ve also already got three on the go, including the new Christopher Brookmyre novel, “All fun and games ’til someone loses an eye” (sorry, no link at the mo, as Amazon appears to be epically tits-up) which is one I’ve been looking forward to for a while now.

I think that perhaps I need to get out more. However, the problem is that I do get out – it’s just that I also read a lot…


CSS – minor bits

For a while now (OK, since the redesign) the comments box has been playing silly fuckers for people using IE. Basically, the comments box was too wide, and slipped under the column on the right, which meant people couldn’t see what they were typing in that section. Kind of unhelpful.

I think I’ve now fixed the problem. But I’d appreciate any feedback from anyone who still uses the piece of crap known as IE to let me know if the problem still exists.

Well, really to know on anything significant if there’s problems in their particular browser.


Mobile Web

Bit of a geeky post, this, while I get my thoughts in order on other stuff.

Anyway, while I was away, I used my new(ish) mobile for reading a few sites, and also to keep an eye on d4d™, make sure it was all running smoothly. Oh, and read comments etc. I didn’t bother sorting out the admin side of things, but well, no-one’s perfect.

So – what it did make me realise was how few sites cater at all for mobile users. D4D™ itself does, because I knew I’d be doing this sort of thing with it. That’s why it’s got the “content first” idea being used, rather than having to get through all the navigation and gubbins first.

I know Gordon’s site is similarly useable, but I was surprised by how few others were. Looks at Pix in particular – well, that’s not fair, it’s useable, it’s just got a bloody huge image first of all, which kind of chuffs Sony Ericsson’s web-browser variant.

It’ll be interesting to see how many more sites convert to this way of working over the next few months.