Archive for June, 2010


E3 2010 is over, and now we have a better idea of the motion control systems that the two big companies (Nintendo already has it) have been telling us about for over a year. Microsoft have finally unveiled the name for Project Natal – Kinect. Sony also unveiled some more games, a price point and a release date.

Microsoft had a huge marketing spending splurge, which kinda made me sick just looking at it all. As a gamer, I don’t care what some actor says about a peripheral (cheque please). But then, Microsoft isn’t aiming Kinect at me, they want that whole casual market to cash in on.

Controller free gaming isn’t new, Sony did it during the PS2 days with the EyeToy. It was fun, but you got over it quickly, and came about the same time the SingStar franchise was starting up – the party was always up for more SingStar than EyeToy. But, it never took off, and never got any compelling gaming experiences. As Richard Marks (the guy at Sony behind the EyeToy and Move) has said about it, sometimes you just want a button.

Now Microsoft is trying it on for size, and whilst they’ve got better technology, with infrared and 3D cameras and stuff, they’re still to convince me that it is a better system. There are signs that it is, but they’re going to have to capture me on more than the first round of shovelware. Which I think is the problem, Microsoft is focusing too much on the casual gamer, rather than its core audience. As IGN have pointed out,

Microsoft needs the core audience to tell the casual gamer what is cool. And if Microsoft doesn’t get that long-time Xbox 360 gamer behind Kinect, it will fail. We need some games that show what Kinect will do for someone who loves games like Halo or Castlevania or Gears of War. I’m not saying it has to be a first-person shooter where you are the gun, but we need to see more gamers that have depth to them.

Sony on the otherhand have a system built around the PlayStation Eye. They’ve been trialling ball-on-stick tracking for years now, since about 2000 (here is Richard Marks’ demo from about 2003/2004), but only now got a commercial product. PlayStation Move doesn’t just use the wand though, but it can do head and body tracking, facial recognition, all that fun stuff that’s ripe for exploitation.

There is definitely a broader range of games on Sony’s system, games that cater to the casual and the “core” gamer, and they’re also showing how it can be flexible by enabling support in other games as well, such as Heavy Rain and Little Big Planet. They must be taking their lessons about the EyeToy seriously – no compelling games? No sale.

Whilst this is the “first wave” that any platform has to suffer through, this first wave of games is coming right in the middle of an already mature game console cycle. We are getting bigger and better games all the time, and that was especially evident at the Sony press conference where they just kept whacking you with new, big, better games. It’s all up to Microsoft and Sony to show us the direction they want to head in with their motion controllers.

Meanwhile, Nintendo is laughing to the bank with all the core games they just announced for the Wii.

HTML5-ing it up

June 13, 2010 at 4:29 pm
View Comments

Woohoo!

OK, not really. All I did was use the <!DOCTYPE html> doctype. This site doesn’t use any HTML5 features, but it does use some CSS3.

The reason? One web browser treats unknown tags differently to the rest. That browser, Internet Explorer.

Until I found Dive into HTML5. It’s a free “book,” detailing HTML5 changes and even explains how you can HTML5-ify your site. And, it even describes a quirk in IE’s JavaScript that can be used to enable HTML5 components (of course, it means that your site is dependent on JS being turned on).

HTML5 was designed so that older browsers can still parse the document, unfortunately, it depended on functionality that 60% (or so) of the web browsing population don’t have.

You may be wondering why I used the HTML5 doctype then. Well, the answer is simple – it’s easy to remember. One annoyance I had with HTML4 was that if I wanted standards, I had to find a website that listed all the correct doctypes, figure out what I wanted, and pasted that in (yeah, I can’t remember them). HTML5 only has one, and it’s forwards compatible. (Who knows what they’ll do with HTML6, although I guess we won’t find out for another 20 years.)

We have a long way to go yet.

Late last year Facebook undertook a massive Privacy Settings overhaul. It was deprecating the “Networks” in favour of pages, i.e. you didn’t belong to the New Zealand Network, but the New Zealand page. In doing so, Facebook popped up on log in a dialog saying “We changed how our privacy settings works, please review your settings below.” I looked at them, and while the dialog was flakey (I complained that it wasn’t clear what “My current settings” was), I looked through them and determined my current settings were what I wanted.

Social Graphs and Personalisation

Facebook announced the Social Graph system and instant personalisation about a month ago. The former seems a lot like Twitter, and the latter seems to be something that should ask for your permission. Facebook stipulated that the only data sent is stuff that is open the everyone, yet then the cries of privacy being breached came. What happened?

My settings are pretty strict, I only share things between Friends or Friends of Friends. Well, there is the basic directory info that I share with everyone, and that’s because I want people to find me (a social network is for finding people and making connections, and if I can’t find you, then you don’t know what social networking is). Only people who I say “I know this person” can see what I’m doing and what I’m up to (although, most of the time, it’s to the oh-so-public Twitter, so, you know what I’m doing anyway).

And here’s the kicker, everyone was saying that Instant Personalisation was opt-out. Problem was, I never opted out, or opted in, and I’m not in it. I read the complaints on Twitter, when I inquired I got a “You’re kidding right?” When I figured out what the hell was going on, I found the Instant Personalisation screen and that the box wasn’t checked, and never has been.

Everyone, it means Everyone

Facebook uses the term “Everyone.” I can see why, Everyone is all emcompassing, and pretty much summarises in a single word who you are sharing your data with. But alas, there is that vague-ness about it. “So, Everyone means just people I’m friends with, right?”

When Facebook said “OK, now we have these API’s that lets people access that data,” people just went “Wait a minute. So, my data is public now?”

Yes, your data is public now, and has been since you said “Everyone” could access it.

They should probably call it something else, maybe, “Everyone, including people and businesses you don’t know.”

But, it did yield good results

The best thing about the privacy furor, good things did happen.

Facebook finally simplified the privacy controls – still giving that granular control that everyone wants, but made it simple at the same time. They should have had that to start with.

They also finally clarified what Everyone means…

Information you’ve shared with everyone – as well as your name, profile picture, gender and networks – could be seen by anyone on the Internet. Please be aware that it will be visible to anyone viewing your profile and applications and websites you and your friends use will be able to access it.

(Emphasis, theirs.)

In fact, I love their Privacy guide. Go and read it. It tells you exactly what’s going on, without the legalese. I wish every web site did this, for all legal policies. Take a look at the Creative Commons license I’ve got on this blog. It gives you an easy to read version of a legal document that can be understood by anyone looking at it for five seconds. If you must, you can dig deeper and look at the legal license that sits behind it.

Facebook also had a bug appear during the middle of all this which let you pretty much log in as someone else just by using a simple tool that lets you look at your profile as someone else. I expect QA would be tighter now on privacy than ever before.

The problem wasn’t just Facebook here, it was everyone, including people and businesses we don’t know. Facebook have done some pretty dodgy stuff (the do-first-ask-later game is getting pretty tiring), but when I read their privacy policy all I saw was “if you said that this information is public, then fair game.” Facebook asked, people said yes, but then changed their minds when it got real.

Of course, the simpler thing is to not put stuff up there you don’t want strangers to know.

Comments

June 3, 2010 at 9:46 pm
View Comments

Google appear to have a website called Google Crisis Response which is available when disaster strikes. It’s currently active with the BP Oil Spill.

There are a compilation of Google Maps layers, with forecasts to where the oil is headed, and the latest satellite imagery. Then there are links to Google Earth/KML files with this, and more (such as animations of the spill). There is also this great overlay with all the worlds oil spills (and rapidly updating data on the current one).

The Daily Kos has an article on how to do “fucking proper fucking booming.” Quite interesting, and here’s a sum up in picture format!

Fucking Boom