Log this one in the “Totally out there” bin. Also in the “doesn’t really work, but shows off a cool notion that could probably be done if we were smarter and weren’t using an underpowered web plugin” bin. And the “Big Brother / 1984″ bin.

Inspired by the love our Augmented Reality Twitter Shirt recieved and our recent foray into face detection, we decided to put the two together. At the moment, the script doesn’t detect a specific person — that’s where the (kind of) comes into play. But imagine associating specific faces with twitter (or “face”book… …. sorry) usernames and you’ve suddenly combined the power social networking with video monitoring that would make the Brit’s CCTV system cry like it just got relegated to League Two.

This actually came about as a happy little accident while trying to bend FLARToolkit to our will (tracking multiple instances of multiple symbols – a total pain in the ass. But that’s a story for another time). It just so happened that we were rocking out to Kiss’ “God Gave Rock & Roll To You” and it suddenly occurred to us that “Hey, it wouldn’t be so hard to make these things make sounds when they disappear.” So we did. And it was awesome.

We’ve (for once) posted a usable demo, so you too can rock out at your desk. Below is a quick video demo of all four sounds and after the break, you can see the demo of using multiple instances of the same drum.

So we here at squidder have been playing around with the FLARToolKit a lot recently. Pretty amazing stuff really. And while fooling around with it, something (perhaps obvious) occurred to us: We love flash. And we also love t-shirts. And Papervision. And Twitter.

And, suddenly, we had a way to combine them all together.

Below is an early technical demo, in which a barcode, containing a twitter username, is embedded within our FLAR pattern. This is important because you don’t need to create a new pattern for each username. Instead, the flash reads the person’s username (up to 8 characters, encoded in 6 bit chunks) and then pulls that person’s latest post from twitter. 

The source code is a mess, but we’ll be posting some more how-to details soon. In the meantime, enjoy the video demo below!

Update: YouTube drools, Vimeo rules.

It really remains to be seen how this new development from The Company Google will affect us flash developers. In some ways, it could be bad — imagine an instance where only some of the text is embedded but not necessary representational. Yeah, yeah, it’ll index data calls as well, but still, you should probably stick to some good ol’ SEO best practices for now… On the other hand, it probably spells relief for clients, which can only mean more work for flash devs everywhere… and disaster for Earth.

We at squidder often talk about the best way to bring SEO and accessibility to our flash work. And in many ways, the work is simple when you add in fancy tools like SWFObject — just spit out the content you want to appear to a search engine in the div that gets overwritten!

But what if you’ve got an extremely complex site, with many sections, pages and drill downs that you want to make accessible? One option is to simply spit out all the content, no matter how long, into that same div. Yes, that will get indexed by search engines, but not only does it make the page you’re loading very large, it also doesn’t link users directly to the content they searched for.

That’s where SWFAddress and mod_rewrite come in. Full deets after the jump.

Let’s look at our tools:

SWFAddress, as you may know, is an OUTRAGEOUSLY awesome javascript tool that works in tandem with SWFObject to allow for deep linking and use of the back/forward buttons in the browser.

mod_rewrite is an apache module that basically lets you parse out elements of a url as variables instead of the folder structure that they appear to be.

So let’s put them together.

Let’s say you’ve got a flash application set up for selling music. There is conceivably a huge amount of information that you would want to make available to search engines, but there’s no way you could output all the information on one page.

Instead, you set up a “fake” directory structure using mod_rewrite that might look like this:

yourmusicapp.com/alternative/wolf_parade/apologies_to_the_queen_mary/

So everything after the first “/” is parsed and used to return an html page with the track listing and album info for Wolf Parade’s album “Apologies To The Queen Mary”.

Similarly, if you went to “/alternative/work_parade/”, you would get html of links to all of Wolf Parade’s albums and a description for the band. Go futher down to just “/alternative/” and you’d get links to all the alternative artists and if you just went to “/” you’d get a links to all the genres.

So now we’ve set up a structure that can easily be indexed. But now how does that allow us to get into the flash?

If we call the above links “hard urls”, then “soft urls” would be urls that you pass into SWFAddress for deep linking — basically anything that occurs after the “#”. So the soft url of the example above would be:

yourmusicapp.com/#/alternative/wolf_parade/apologies_to_the_queen_mary/

The flash is then set up as such that when it receives the value above from SWFAddress that it automatically goes to the album view for “Apologies To The Queen Mary”.

Now the final step: using javascript, you can automatically forward users with flash who are led to the “hard urls” to the the “soft urls”. So someone who searches for “Wolf Parade” in google would get back:

yourmusicapp.com/aternative/wolf_parade/

If the viewer is a search engine, they’ll be stopped here and just index the information about wolf parade. But if its a viewer with flash installed, they’ll be seamlessly redirected to the flash application:

yourmusicapp.com/#/alternative/wolf_parade/

Conclusion

Our next step is to get a public example of this for people to take a gander through. SEO solutions of this caliber for flash are great for both developers and agencies as it lets us alleviate some fears that clients may put up to going with flash. It’s not for every project — you’ll probably need control of the back end development as well as the front end — but when you find the right one, you’ll know it.

Also, keep in mind that you don’t actually need mod_rewrite to pursue a solution like this – you could generate the hard urls as actual html files instead of generating them on the fly, which, if your music store was getting a ton of traffic, might be a better plan anyway. The important thing is coming up with a url structure that is mirrored in the both the hard urls and the soft urls.

Finally: if you haven’t heard “Apologies To The Queen Mary”, do yourself a favor and get it. I’m not going to say that if you listen to it backwards while reading this post, you’ll find a super secret message… but you never know.

We’re late to the game as usual on this one, but if you’ve ever had a client who wanted MAXIMUM standards complacency and compatibility, its time you checked out Faust flash augmenting standard, evangelized by the future-loving folks over at space150.

If there’s one thing that could be a ton cooler in AS3, its the audio capabilities. Yeah, we’ve all had fun making spectrum analyzers, but that was back in the hazy, drug riddled days of 2007. This is 2008 and 2008 demands better audio stability and features.