AusCERT 2012: What’s changed since 2011?

I’m currently on the train down from the Blue Mountains to Sydney, en route to the AusCERT 2012 information security conference on the Gold Coast, and I’m thinking about what stories might emerge.

Here’s what I wrote last year when, just like this year, I was on the ZDNet Australia team:

The feeling I get from scanning those headlines is that there’s always a lot of scaremongering but the threats often don’t materialise. Are the threats over-stated? Does pointing out the threats trigger an effort to counter them, thus defeating them? Is it all just a bit too screechy?

And over the last year there’s been so much talk of imminent cyberwar. Is that just this year’s fashionable scary thing on a stick? I intend to ask a few questions. And I’ll plug it again: Thomas Rid says we shouldn’t believe the hype.

I haven’t yet looked in detail at the conference program but will do so over the next few hours. What do you reckon I should be investigating?

[Update 16 May 2012, 0625 AEST: Changed second paragraph to emphasise that I am covering the event for ZDNet Australia this year as well as last.]

Crikey: Google+ is a goddam Trojan horse

So, there’s a reason Google is being so stubborn over this “real names” policy. Google+ isn’t a social network at all, despite the fact that it looks like one. It’s actually the core of an identity service.

I wrote about this for Crikey today, a piece that includes Google chair Eric Schmidt’s confirmation of that plan and some observations that suggest Google+ is failing to reach critical mass.

The continuing bad press over what’s been dubbed #nymwars won’t help. Yet I suspect that Google’s need and desire to prevent Facebook Connect becoming the planet’s default identity service will override most concerns.

It’ll be interesting to see how this plays out.

Schmidt has always been the go-for-profits guy. Google co-founder and CEO Larry Page is reportedly aware of the problem, although an informative post by Stephen R van den Berg says it’s unclear whether he’s being properly informed about the criticism. That post was written a week ago, however, so I daresay Page has seen at least some of the news reports since. And the other co-founder, Sergey Brin, has been notably silent.

It feels like things have come a long way since my original expletive-filled rant.

Oh, and thank you to everyone who said they liked the Patch Monday podcast on this topic. That’s especially pleasant given my fears over the rushed recording.

Stilgherrian versus Google, Round 2

There’s been a few developments this week in my battle with Google over my name. More communication. And more media coverage.

On 18 August I responded to Google’s boilerplate email thusly:

Hi folks,

My full, legal name is a mononym, “Stilgherrian”. It has been so for 30 years. This name has been used consistently throughout that time on every official document, in every credit line in print, on radio and on television, in everyday use… everywhere.

Dare I say it, a Google Search will soon reveal that.

My only photo ID is my passport, and I am unwilling to send a copy because I have security concerns.

I can’t edit my name in Google Profiles to match my “real” name, because it won’t let me leave the surname field blank.

How do we fix this?

Cheers,

Stilgherrian

Google’s reply arrived on 20 August.

Continue reading “Stilgherrian versus Google, Round 2”

My Google names-policy rant goes global

My expletive-ridden blog post about Google’s fucked-up “real names” policy and their brain-dead implementation has gone global.

While my editor at Crikey commissioned an article, To Google, we are data fodder, and I am an unperson, the story was picked up by an American political blog and linked to by The Wall Street Journal.

The post has been viewed at least 6000 times, probably many more. So far.

I’ve just written a lengthy response to the 127 comments so far. I do think that people who say “It’s only a beta” and “It’s just a bug” and “Well it is a free service” and “What do you expect with a weird name?” have entirely missed the point.

That, too, will probably offend people.

And now my work here is done.

Please add your comments on the original post.

[Photo: Logo from Google Developer Day 2007 by meneame comunicacions, sl, used under a Creative Commons BY-SA license.]

Right, Google, you stupid cunts, this is simply not on!

[Stilgherrian writes: Oh dear. This post has generated a lot of interest. Thank you for that interest. But if you’re visiting for the first time, I strongly suggest you also read my lengthy response to commenters and the fair warning before posting your own comment.]

I knew this would happen sooner or later. Google, a data mining company in the United States, has the ignorant arrogance to tell me, a citizen of Australia, that my name — my legal name — doesn’t fit their scheme for how names “should” work. Well fuck you, arseholes!

What’s worse, this is how they tell you.

They suspend your profile, tell you your name is wrong, and tell you to change it.

Your profile has been suspended.

It appears that the name you entered doesn’t comply with our Names Policy.

The Names Policy requires that you use the name that you are commonly referred to in real life in your profile. Nicknames, maiden names, and so on, should be entered in the Other Names section of the profile. Profiles are currently limited to individuals; we will be launching a profile for businesses and other entities later this year.

Your profile will be suspended until you do edit your name to comply with the Names Policy: you will not be able to make full use Google services that require an active profile, such as Google+, Buzz, Reader and Picasa. This will not prevent you from using other Google services, like Gmail.

We understand that Google+ and it’s [sic] Names Policy may not be for everyone at this time. We would hate to see you go, but if you choose to leave, make a copy of your Google+ data first. Then, click here to leave Google+.

Listen, Googlecunts. This name precisely fits your Names Policy.

Continue reading “Right, Google, you stupid cunts, this is simply not on!”