My raw thoughts on Google’s acquisition of Motorola Mobility

Overall, I am positive on the acquisition, with my main concern being that Google is clear and decisive about how they plan to proceed with the integration and operational side, and that they don’t unintentionally create confusion and concern in the consumer market.

ARMING UP FOR THE PATENT WAR
Obviously this acquisition is related to the ongoing patent wars between Apple and Google (with their hardware partners HTC and Samsung as the primary proxies for litigation). Motorola has a deep, broad collection of intellectual property. Not only did they invent the cellular telephone and have years of creating popular consumer mobile hardware (StarTAC!), but they also have created their own Linux+Java mobile OSes in the past, which could provide support for Google in the case vs. Oracle.

GOOD FOR DEVELOPERS FOR NOW
I don’t think this will change much for developers in the next few years, as Android has great momentum that won’t end anytime soon. It may be a boon ultimately, as Google must work harder to maintain the image of Android being open now. The more transparency and code they release, the better for all.  I would also hope Google uses this to support and/or indemnify its app developers from worrying about being sued by patent trolls like LodSys.

PUTTING THE NAIL IN THE RIM COFFIN
Motorola has a “Pro” category of devices, with enhanced security in the OS to meet enterprise and gov requirements, as well as Blackberry style keyboards. This device could be a “Nexus Pro” sold bundled with Google Enterprise services to take on RIM directly as complete business tack. Google is having a lot more success in this space than people realize, taking on IBM, Microsoft and RIM all in one swoop. This is an area that Apple cannot compete in.

COMPETING WITH YOUR PARTNERS
It will be a tricky task to manage Android and Motorola business units of Google. While not entirely comparable, there are some good lessons to learn from Palm and Apple’s own failed attempts at licensing an OS while producing their own competitive hardware. I was at Palm when we had the PalmOne (Hardware) and PalmSource (OS) divisions, when there were still Palm licensees such as Handspring and Sony, and it was a really difficult mess. PalmSource had to treat us like a separate company, in order to appease partners, but at the same time, we didn’t have the freedom those partners would have to implement their solutions because we had to maintain unity with the Palm vision. Eventually, all the licensing ended, Palm bought Handspring, and the whole company unified again, and then ultimately failed, and was acquired by HP.

Redesigning the Camera Phone to Protect Privacy

Have you ever wanted to post a photo to Facebook from your mobile phone, but weren’t sure if someone in that photo would mind their face going online? Did you take a great picture of your kid at the playground that you want to tweet out to the world, but caught some other kid in the shot, and are worried about their parent freaking out about online predators? Maybe you are worried about all the data that is being logged in your photos, like the exact GPS coordinates of where you took the picture, and don’t know how to disable that feature. If any of these thoughts have ever crossed your mind, and you have an Android phone, then you should try out a new app my team at the Guardian Project just launched called ObscuraCam.

In short, the app integrates with your camera and gallery, to allow you to remove, pixelize or disguise faces of people in your photos, before you upload them to Facebook, Twitter or elsewhere. It also cleans out all the secret, hidden extra data that gets stored in your photos, like your GPS location, the make and model of the camera phone and sometimes even a unique serial number identifying your phone. While our original goal was to build an app that supported human rights activists in places like Iran and China, we really do think this app has broader relevance to everyday people (like YOU!) who want to have a bit more power of controlling what gets revealed, analyzed and indexed when they share their photos online.

Read the post on the Guardian Project blog, to get a more in-depth idea about what we’ve done, and where we are going with this project. This “v1” release is just for still photos, but we are quickly moving on to support video, as well as additional obscura filters too!

ObscuraCam is pretty powerful, in that it can automatically detect multiple faces in a photo, and then allow you to selectively choose how to filter those faces. You can also filter out t-shirts, signs, sensitive documents on a desk or just about anything you don’t want a human or machine to be able to see.

You can even have some fun putting on a silly disguise, which may still allow a human to recognize the person in the photo, but would most likely stop Facebook or Google’s current recognition software from figuring out who you are.

So, please – try it out, have some fun, and post some pictures.

Just search for “Obscura” in the Android Market or install it directly from the web.

My Quick Guide to a Less Risky Dropbox

While there are definitely many security-related holes and privacy concerns to be had about the free (but not open-source) Dropbox file sharing service, it has taken the world by storm, including many activist and human rights groups, mostly due to the simplicity and effectiveness of its user experience. As we have seen many times before, software and services that “just work”, will always win out over more secure options with the majority of the population. This post is a quick attempt to share some simple steps you can take to ensure your use of Dropbox, or any similar cloud-based file storage and sharing system, is more properly protected, obscured or otherwise mitigated as a direct threat to the security of your information.

1. Use Dropbox over Tor to stop local network monitors from knowing you are using Dropbox to begin with. This also is a good configuration to use with people who live in places where Dropbox might be blocked, but Tor is not.

Install Tor and use Vidalia (the GUI controller) to connect to the Tor network.

Set Dropbox->Preferences->Network->Proxy Settings to use Tor’s secure SOCKS proxy on localhost, port 9050

2. Set Bandwidth Usage to a low value to avoid creating large spikes in network traffic. This will reduce the likelihood your particular use will be singled out if you are syncing large media files or other transfers.

Set Dropbox->Preferences->Network->Bandwidth Usage to a low value such as 50KB/s for upload and download

3. Use Truecrypt to create encrypted disk volume files inside of Dropbox, and then store your files inside of that. This can still be shared by multiple users, if you use a password based volume.

Download, install and configure the free, open-source TrueCrypt software: http://www.truecrypt.org/

Create a new TrueCrypt volume, stored within a Dropbox folder

All in all, there are more secure ways to share sensitive information, such as using GPG file encryption or another OpenPGP solution, but if you absolutely must use Dropbox, and you are under any sort of threat at all to having the information you store on it used against you, then please follow this advice I have shared.

If you have additional tips, warnings or configurations along these lines, please add them to the comments below.

    Another small step for a Tibetan keyboard on Android

    There has been a lot of excitement this week about the robust support for the Tibetan written language in Apple’s iOS 4.2 for iPhone and iPad. This is a fantastic achievement that many contributed to, and that Apple should be loudly applauded for.

    Unfortunately, the state of Tibetan on Android is still poor, but not hopeless. While Tom Meyer has provided a great starting point for rendering text properly, I still am not aware of any means for inputing Tibetan characters. With that in mind, I set out to investigate the ability to create a new Tibetan “Input Method” (as Google calls it) for Android, and quickly realized that one could just write a Language Pack add-on for the open-source AnySoftKeyboard project. This solution still requires you to root your phone and install the Dzongkha”རྫོང་ཁ font, but is still a step in the right direction!

    You can find the open-source code for my new project, the Tibetan AnySoftKeyboard Language Pack on Github. If you would like to try it out, you must have a rooted device with the Dzongkha”རྫོང་ཁ font installed, then install the “AnySoftKeyboard” from the Android Market, then you can install the first test Add-on APK file, and the Tibetan option should come up in keyboard settings.

    Below you can see a screenshot of the initial keyboard writing text into the OI Notepad app. It appears to be properly stacking characters as well, but I may be wrong. Also the current implementation does not yet support the SHIFT key or other modifiers. I would love to have some help setting up the rest of the QWERTY mappings in this XML file. Otherwise, any other comments, feedback, advice or pointers to other Android Tibetan keyboard work would be much appreciated!