March 26th: Blogging D-Day
However yesterday we received a less-than-welcome notification from Blogger that they will no longer support FTP publishing in Blogger after March 26th of this year. They blamed the decision on "too many engineering resources" required to support FTP sites and said "We realize that this will not necessarily be welcome news for some users."
No kidding!
Word has it that the reason Google are doing this is nothing to do with cost and more about censorship. As you all know, we host our own blog on our own server, but we use the freely-available Blogger code for the blog publishing part, which allows all you lovely folks to use your Blogger accounts to leave comments etc. So not only can we remain part of the thriving Blogger community, but by publishing the blog via FTP this means that all our precious photographs are kept on our own servers, not Google's. We can therefore design our own groovy blog graphics (instead of Blogger's grotty standard templates) plus of course, we don't have to have a "content warning" header slapped in front of our blog (like most of you do.)
Basically Google doesn't have any control over what we can publish or how we publish it. We really like it that way. And I quote our resident photographer: "Hell will freeze over before I host our blog on Google servers. They have enough control over us as it is...this is just to increase their control and censorship of the internet. No bloody way! I'd rather close our blog first!"
(And before I get tons of comments from happy photographic bloggers who tell me that they host their blogs on Google servers and they don't mind one little bit, I must warn you in advance that we have absolutely no intention of going down this route. We deal with internet security as part of our day job. Bearing in mind what we know, please trust me when I say that letting Google host all our intellectual property is NOT an option.)
So we have until 26th March to decide what to do.
Perhaps it's time to put our resident computer geek to work on designing our own blogging code?
(Poor lad! As if he doesn't have enough to do already!)






