Pastebins are incredibly useful. But most of the public pastebins are not suitable for sharing within a company (think code fragments, log messages etc.) and most private pastebins are either ugly (except hastebin!), hard to setup/maintain and usually forced to be behind the firewall (for security).

So I decided to scratch my itch and whipped up a pastebin that fit my needs. Features:

• Usability: it’s a pastebin — you create a paste, you view a paste. That’s it. No need to specify the language — we guess it, thanks to highlight.js. It also looks good (I think), thanks to Solarized.
• Easy of deployment: no installation, no maintenance. Just deploy to Google App Engine.
• Security: you need a Google account to create a paste. No login required to view a paste though. Bonus: if you use Google Apps at your company, you can have a private pastebin for you company by restricting the app to your domain.
• Open source: Fork it, baby!

The Good Great

• Google integration: this is a no brainer. If you spend a lot of time on Google properties (like I do), the integration is superb! Nexus 7 is meant to be a device for content consumption so it’s no surprise that Google Play is almost “pushed” in front of the user. It even synced the known wifi networks (and passwords) from my Galaxy Nexus!
• Form factor: I’ve only used the iPad 2 and the new iPad briefly. Though the Nexus 7 is visibly smaller, it’s a lot more comfortable to hold with one hand without building muscle. (On the other hand, one could argue that it’s only slightly larger than Galaxy Nexus…)
• Performance: this baby is fast! Those quad-core Tegra processors sure do their job — I haven’t played any intense games yet, but everything else (switching between apps, Angry Birds, Google Earth, browsing through music and photos, playing videos etc etc) is super snappy.
• Bang for buck: at $200, the price point couldn’t get better. This price advantage alone will put the Nexus 7 within reach of many could-have-been iPad owners.

The Bad Good

• Build quality: this is no iPad, but the tablet feels solid. I like the textured back panel. But the screen gets smudged quite easily (similar to the iPad) and is a tad too glossy for me. I miss the smart cover!
• PDF reader: the built-in default PDF reader sucks. I can’t swipe to go to next page, for instance. The Kindle PDF reader is much better in comparison.
• Book reader: Again, this is no Kindle (but the Kindle Fire is toast) but the Play book reader is pretty good. All caveats w.r.t e-ink vs. back-lit screens apply. There is one problem though: if while reading you accidentally end up touching anywhere near the bottom of the screen (which is fairly easy to do, if you consider how you normally hold a book or an e-reader), you’ll end up either going to the home screen or opening up the task switcher. Either way, its extremely distracting. I wish they added a “locked” mode while reading books that can only be changed by using the physical power button.

The Ugly Bad

• Camera: there’s no (easy) way to take pictures on this device. Yes, there is a (crappy) front-facing camera but it is only meant for hangouts. I seriously don’t understand why Google doesn’t want to put a good camera on their devices. I’ve previously complained about how crappy the Galaxy Nexus camer is compared to the iPhone 4S‘s, and the Nexus 7 doesn’t change anything.
• Packaging: given that unboxing is the first experience with the device users have, I’m bitterly disappointed by the Nexus 7 packaging. The sleeve is too snug; the black packaging just too cardboardy; and there should be an award for opening the inner box without struggling. Overall, it was just plain frustrating getting the device out of the box (and I’m not alone in this). Yes, first world problems but whatever.

More later.

Facts:

1. The Internet dominates our lives.
2. The Internet thrives on advertising (think Google, Facebook, Twitter, Hulu)

It therefore follows that our lives are dominated by Internet advertising.

The traditional model for advertising has been that publishers put out ads to catch the attention of consumers via some like of delivery network. In the past these delivery networks were in print, on radio, on television and now, on the Internet. It seems like a win-win for everyone: the delivery network gets paid by the publishers; the publishers make money because they get more customers; the consumers find out about publishers that they may not have otherwise known.

But a new trend is emerging now: consumers directly pay the delivery networks to NOT see ads from publishers.

Think Spotify. Netflix. Pandora. NYTimes. Dozens (hundreds) of mobile apps and games that have paid versions without ads.

Think about it. There seems to be near universal consensus that ads are a negative thing. There seem to be some (many?) success stories that individual consumers are willing to pay extra to avoid exposure to ads.

It seems like a fundamental shift in advertising to me. A world where the delivery networks become content providers and instead of charging publishers, they make money directly from the consumers.

In particular, I wonder how the Internet giants will evolve to take this trend into account. Would you be interested in a paid Google account that has no ads and offers full privacy (because they don’t need to make money off of your information anymore)?

Also interesting is that Apple is probably one of the few companies that are isolated from this changing nature of ads.

For instance, on my iPhone I read pretty  much everything via Flipboard. On Android, I’m still struggling to find a good Flipboard replacement and shuttle between Pulse, Google Currents and recently, Feedly. In either case, I rarely ever go to the actual website.

I still get some of my content fix from Google Reader (xkcd, Abstruse Goose etc).

Most of the “news” — that is, when I’m in “skim mode” — comes from social media, mostly G+ and a tiny bit from Twitter.

I remember the days (several years ago) when Techcrunch changing it’s site layout used to be a news in itself. Now I can’t remember the last time I visited Techcrunch (well, that could be partially attributed to the content quality…)

My point is, in all of the above cases, the app or service presents the content in an origin-agnostic manner. When you read something on Flipboard, it’s presented to be consumable via the Flipboard interface (in most cases), and not meant to preserve the look and feel of the origin website.

And such apps and services are just becoming more and more prevalent: Evernote Clearly; Readability; content-provider specific apps such as those from Time, CNN, NYT etc.

So, is website design becoming irrelevant? Especially for content-heavy sites?

(The Oatmeal is an exception — Matthew forces you to visit the website, and it’s always worth it)

The Awesome

• Google Integration: Galaxy Nexus is a great phone, no doubt. But make no mistakes — you won’t get the full experience if you’re not using Google’s services (gmail, calendar etc). If you already entrenched in the Google ecosystem (as I am), you’ll love it! As soon as I turned the phone on, it asked me for my Google credentials and within a few minutes I had my email, calendar, contacts, photos, bookmarks and music available on the phone. It was like magic! The support for multiple Google accounts is also fantastic; so if you’re using Google Apps at your workplace (as we are), rejoice!
• Hardware: This phone is FAST. The display looks great (I’m not quite sure how to compare it with the Retina displays on iPhone 4S, but I won’t be surprised if the Retina display comes off as better). The phone is also surprisingly thin and light.

The Good

• Android: The Google apps on Android are so much better than their iOS counterparts, especially Gmail, Maps, Google+ and Google Talk. Some services (like Google Music) don’t have apps on iOS (yet).
• Power Users: Geeks and data nerds will LOVE this phone. Signal strength graphs? Check. Breakdown of data and battery usage by apps? Check. Fine-grained control over how much cellular data apps can use? Check. Aggressively reap processes as soon as user exits an app? Check.
• No Cables: Unlike iOS devices, the Galaxy Nexus doesn’t depend on any iTunes like software running on a computer to get app updates or synchronize music. Everything synchronizes over the air (you can restrict syncs to wi-fi only). iOS5 has a similar feature but still needs iTunes running and accessible within your network AND requires the devices to be connected to a power source (which typically is also the computer, so …)
• Google Voice: Unlike on iOS, Google Voice can truly take over the phone on Galaxy Nexus. You can finally use Google Voice how it was meant to be used — let it control all incoming/outgoing calls, voicemail and text messages.

The Bad

• Lacks Polish: For all the great improvements made in Android 4.0 (Ice Cream Sandwich), the Galaxy Nexus is still not nearly as polished as the latest iPhones. iOS reigns king when it comes to attention to detail and making sure all aspects of the system fit well together. Here are a few examples. When I first turned on the phone, the home screen was part empty, part full of ugly “widgets” (I still don’t have a good  understanding of widgets on Android). There is a separate area for apps, so when you install something, it won’t appear on any of your home screens. The notification bar is nice, but I find the notification badges on iOS a lot more intuitive. Some of Google’s own apps (notably Google Listen for podcasts and Google Currents for news) are just half-baked and buggy products.
• Confusing: A common converse for a product that power users like is that it can easily overwhelm average consumers. There are just too many knobs and controls, some system-wide, some app-specific. It’s a phone for which I sometimes wish I had a user manual. Here are a few examples. Do you know how to take a screenshot on the Galaxy Nexus? Or how to quickly put the phone in silent mode? Or exactly what does “background data restriction” mean — and if it does mean what I think it does, why does the phone have a persistent warning in the notification area as if this is a real problem?
• Size: Size does matter and this phone is BIG to hold. The larger display is sure nice, but I can’t operate this phone with one hand. At all. This is particularly problematic if you need to go to the next song while you are riding your bike, or even just answer a call. Want to write a text with one hand (maybe you have a drink in the other)? Forget it. It doesn’t help that the phone is hard to hold and slips easily — I highly recommend getting some kind of a case/cover that provides a better grip.
• Verizon only: Galaxy Nexus is only available on Verizon as of today. I’m sure somewhere down the road it will be available via AT&T and other providers but I won’t hold my breath (it took iPhone several years to be available on Verizon). In the meantime, if you want a Galaxy Nexus for a GSM network, just buy an unlocked version from Amazon.

The Ugly

• Ecosystem: One of the biggest problems with Galaxy Nexus (as I imagine with other Android devices) is the ecosystem. Several key apps are not available in the Android Market yet (Flipboard, Instagram to name two). The app-ecosystem itself is quite fragment with Amazon and others wanting to get their share of the pie. The accessories ecosystem is even worse. Just try searching for a case for Galaxy Nexus. In comparison, the iPhone/iPad ecosystem is significantly richer.

I got my invite for the Bitcasa beta last week but only got around to installing it yesterday. I’ve only used it sparingly thus far. If you are in a hurry, here’s the TL;DR version:

• Users might find the “cloudify” model confusing
• Built using osxfuse (not to be confused with MacFUSE) and Qt
• Infinite storage sounds too good to be true. What’s the catch?
• Building trust with users will take time

Cloudification and Confusion

Here’s Bitcasa on what cloudify does:

When a folder is Cloudified, a corresponding virtual folder is created on the Bitcasa server and the contents of your local folder are copied up to the server. When Connected to the Bitcasa server, any changes or additions to the folder will live on the server. When not Connected to the Bitcasa server, any changes or addition to the folder will live locally.

Just think about that for a second. The “cloudify” model sounds great in principle, but it does add a lot of complexity in terms of how users interact with the system. For instance, when I’m offline and make changes to one of my cloudified folders, that change happens presumably locally. I would assume that when I come back online, these changes are synced back to Bitcasa ala Dropbox. But what if I accidentally disconnect a folder, make some changes and then reconnect — per the FAQ, the changes made locally won’t be synced.

The consumer cloud storage is fairly mature right now and one can learn a lot by looking at how people respond to other systems. This thread on Quora is particularly insightful: again and again, simplicity comes up as one of the key reasons behind Dropbox’s success.

My prediction is that Bitcasa’s cloudify feature will be leveraged primarily by power users and the rest would end up using the default Bitcasa folder, Dropbox style.

Nuts and Bolts

Bitcasa seems to be built primarily using Qt. This isn’t a surprise: Qt is a mature, open source and cross-platform library.

$ otool -L Bitcasa
Bitcasa:
 /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)
 /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
 /usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 44.0.0)
 @executable_path/../Frameworks/libmacfuse_i64.2.dylib (compatibility version 10.0.0, current version 2.0.0)
 /usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 44.0.0)
 /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 53.0.0)
 @executable_path/../Frameworks/QtWebKit.framework/Versions/4/QtWebKit (compatibility version 4.7.0, current version 4.7.4)
 @executable_path/../Frameworks/QtXml.framework/Versions/4/QtXml (compatibility version 4.7.0, current version 4.7.4)
 @executable_path/../Frameworks/QtGui.framework/Versions/4/QtGui (compatibility version 4.7.0, current version 4.7.4)
 @executable_path/../Frameworks/QtNetwork.framework/Versions/4/QtNetwork (compatibility version 4.7.0, current version 4.7.4)
 @executable_path/../Frameworks/QtCore.framework/Versions/4/QtCore (compatibility version 4.7.0, current version 4.7.4)
 /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 52.0.0)
 /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1105.0.0)

$ mount
Sample Videos on /Users/diwaker/Bitcasa/Sample Videos (osxfusefs, nodev, nosuid, synchronous, mounted by diwaker)
TryBitcasa on /Users/diwaker/TryBitcasa (osxfusefs, nodev, nosuid, synchronous, mounted by diwaker)
TryBitcasaDedup on /Users/diwaker/TryBitcasaDedup (osxfusefs, nodev, nosuid, synchronous, mounted by diwaker)

Note further that Bitcasa represents “connected” folders as mount points over the existing folders. This is why when you disconnect a folder and make changes, they won’t propagate to Bitcasa’s copy of that folder. They are using osxfuse which implies that Bitcasa is intercepting file system calls; this is in contrast to Dropbox-like systems that detect changes to the local filesystem asynchronously. I haven’t compared fine-grained read/write performance just yet.

Here’s a snapshot of the Bitcasa Folders UI:

Bitcasa also does some deduplication. Uploading 100MB of mostly random data took around 4 minutes on a pretty fat pipe which isnt’ bad at all. Copying that data back out took just as long, if not longer. A copy of the same folder took less than 10 seconds to cloudify!

Security

Much has been said about Bitcasa’s security. However, most of the articles are concerned with a specific dimension of security: encryption.

A detailed discussion of Bitcasa’s security in general and encryption, in particular, deserves a post of its own. For now, suffice to say that even after several years of user experience, Dropbox still hit some pretty nasty security snafus in 2011. Like a lot of you, I’m very concerned about security, especially with a service that is offering me infinite storage for free! It takes time to build trust with your users — there’s no short cut.

Overall, Bitcasa is definitely interesting. Dropbox was almost beginning to monopolize the consumer cloud storage market, so some good competition will hopefully benefit the end users in the long run.

OK, that probably sounds contrived. But the truth is that I did have the need to extract the wifi password from my wife’s laptop earlier today and thought I’d share the (pretty simple) process.

Step one: open keychain access

Step two: search for the network name (SSID)

Step three: check ‘Show password’ (you may need to enter your password first since this required Administrator privileges).

Voila!

Summary: the NDTV app is probably one of the best free apps. I didn’t consider paid apps.

First, the usual suspects:

Times of India: The ToI app’s UI is functional, but otherwise not remarkable at a first glance. In true ToI tradition, the “Entertainment” section is feature prominently on the home page, just under top news. Of course, readers of ToI know that “Entertainment” and “Photos” are just euphemisms for soft porn — ToI happily parlays all kinds of NSFW material under the guise of “news”. I’m really curious to know how much of their app traffic (indeed, their website traffic) goes to the entertainment section.

Thankfully, buried under the “Settings”, the app allows reordering the various sections. You can also optionally specify a home city. I haven’t really used the Video section of the app, so can’t comment on it.

Overall, the app is not bad, but it can’t compensate for ToI’s reporting.

NDTV: The NDTV app feels only slightly more polished than the ToI app; structurally they’re quite similar and most differences are cosmetic. Unlike ToI though, NDTV’s Photos section is closer to what I’d expect on a news app (there’s still a heavy entertainment bias, of course).

But perhaps the most killer aspect of the NDTV app is that you can watch various channels of the NDTV group live!!

The only downside of the NDTV app is that it shows a lot more ads than the other apps I looked at.

Hindustan Times: the HT app is probably not being actively developed — it still has a CWG section!! Other differentiators are a dedicated “Blogs” section. Compared to ToI and NDTV, this app offers basically no customization, no videos. The content is not as rich or fresh as the other apps.

There were a lot of other news apps but none of them felt credible. The IBN Live app looked interesting but it seems to focus mostly on live TV and not news articles. For now, I’m sticking with the NDTV app.

What apps do you use to get your does of Indian news?

As we all know by now (read: probably 1% of the world’s population), at WWDC earlier this week, Apple spilled the beans on the upcoming iCloud, among other things. In this post, I wanted to share some of my thoughts on the much hyped iCloud (not that there is any dearth of opinions and articles on the subject, thanks to the echo-chamber that is Twitterverse and Blogosphere)

First off, some quick bullets summarizing what it is:

• iCloud aims to make cloud storage painless, the idea being that your data should be available to you from all your devices, all the time.
• It’s automatic and transparent. Apple is baking iCloud support deep into 9 different applications: iTunes, Photo Stream, Apps, Books, Documents, Backup, Contacts, Calendar and Mail. And that’s just the beginning.
• It’s free. Upto 5GB — excluding purchased music, books, apps and photo stream.
• Sync over the air: iCloud can sync across devices over wireless. As a concrete example, you’ll no longer need a cable to sync and backup your iPhone with your laptop.

Here are some cool things about iCloud:

• Scan and skip upload (iTunes only): when dealing with large data sets (such as your movies and music collection), one of the main impediments to using cloud storage is the overhead of doing the initial import. With a 1Mbps uplink, a 10GB music collection will take a full day to upload. Of course, if the file you are trying to upload already exists somewhere in the cloud, you don’t need to upload it and this is exactly what iCloud does. Because of the iTunes store, Apple already has a library of 18 million songs (and counting) and detecting if two files are for the same song is a lot easier than for many other media types (say images or movies).
• Storage APIs for developers: APIs are all the rage these days. By exposing the right set of APIs, Apple could attract developers to build iCloud functionality on other platforms (Android, for example). Unfortunately, the API is fairly limited at this point (key-value store or documents).
• HP, Teradata, maybe EMC are rumored to have supplied bulk of the hardware in the spanking new datacenter that will be the backbone for iCloud.
• Despite all the hoopla around “cloud” recently, it was still grounded firmly within the tech circles. Apple has the ability, experience and motivation to take cloud computing truly mainstream with iCloud.

What is NOT so cool:

• Apple has a habit of exaggerating the novelty and efficacy of their features (remember Spaces?) Scan and skip upload is nothing new: it is just deduplication under the wraps — a well known technique in storage systems. Videos and photos will still have to be uploaded though — there’s no real shortcut for those. Of course, there are techniques to dedup arbitrary data and I hope Apple is leveraging them.
• In the same vein, syncing of Mail, Calendar and Contacts is just catch up. Ever used Google? Likewise for Docs and Books. The delivery model is different — Apple apps work with the local data and sync when there’s connectivity. They haven’t touched upon conflict resolution, disconnected clients etc.
• Implications for Dropbox: transparent, automatic sync across multiple devices is a phenomenally hard problem. Apple makes it sound like they’ve nailed it. It took Dropbox several years to address all the performance and security concerns. I’d wager Apple will run into its share of snags along the way.
• Apples all the way: despite their claims, iCloud is designed to lock you in. Sure you may be able to leverage some of the features by installing additional software on a PC. But unless you are using an Apple device, you won’t get the full experience or service. Want your “reading list” available on Android (or Chome, for that matter)? Tough luck. Want your music available to other music players (open source players like Banshee and Amarok, god forbid)? How about your photo stream in Picasa?

Finally, there’s no doubt that iCloud will drastically alter the cloud landscape. However, Apple is focused mainly on the personal cloud — which is a good thing, they are playing to their strengths. It is also a great opportunity because the enterprise cloud market is still wide open. The requirements, challenges and “killer apps” in that market are very very different than the personal/consumer cloud market. Should be fun!

For years, free/libre/open source software (henceforth referred to as FLOSS) have proclaimed, year after year, how that year is the year of Linux, or the year that open source will become mainstream, or the year that open source will finally take off etc. But it never has, at least traditionally speaking. Linux based desktops haven’t penetrated either the enterprise or consumer markets; with a few notable exceptions (Apache httpd, for instance), most FLOSS products — be it office software like OpenOffice, multimedia software such as Gimp or Inkscape — remain popular with economically insignificant niches. And yet, this year, more than ever before, open source forges ahead with its silent victories.

Consider the following shifts:

• all the top brands of the day — Apple, Google, Facebook, Twitter, Amazon — they ALLstand tall on the shoulders of FLOSS giants.
• Contributing software back to the open source community is becoming increasingly common, even expected. Take a look at the GitHub repositories of Twitter and Facebook, or the various Google projects. In fact, when screening engineering candidates, I often look for and encourage people to talk about their open source contributions.
• Most of the activity around “big data” and “cloud computing” is being driven in large part by FLOSS, whether it is the Hadoop-powered ecosystem or the Xen/Linux powered Amazon Web Services.
• Given the current smartphone landscape, it is highly likely that Android will become ubiquitous on tablet devices and a variety of consumer smart phones. Already, Android has more search mindshare than Linux, despite the fact that Linux is part of the Android stack.
• If you start a software company today, I would bet that you will find yourself bootstrapping almost entirely using open source software. The entire development process — from the GCC compiler toolchain, to the build systems, to the scripting languages, to the version control systems, to the code review systems, to the continuous integration systems — everything is dominated by FLOSS products. Good bug trackers and enterprise Wikis are the last bastions but it is just a matter of time.

I’ve had a chance to see the enterprise software market up close and increasingly find more and more open source everywhere I look. FLOSS has not arrived, it has taken over.