Skip to main content

who needs another social network?

That was my first reaction to Google+. In a matter of 2 days 40 connections were added to my circles. That is when I realized that it could be a serious competitor to facebook. Here's why:
  1. Rebuilding social graph is quick and simple. Everyone I have interacted over email can be found in my gmail which makes it easy to add connections. That's viral.
  2. "Hey, look what my dog did last week!" - yes, one can now have side conversations with a relevant group of people instead of broadcasting to all. That's less noise.
  3. I can call in sick at work and still talk about my day off with my friends without worrying about getting fired from work. That's better privacy.
  4. Sure, I will accept invite from my mom. On facebook, it is awkward to let friends, family and co-workers see everything. It's not a problem on Google+ since not everyone can see all my posts. That's more freedom.
  5. It is all about sharing nearly real-time information. Older conversations are irrelevant. That will make it easy to switchover to Google+ once the social graph gets built.
Lastly, Google has a track record of challenging well established players. Just when people thought "who needs another search engine" or "who needs another email", Google surprised everyone. Can they do it again?
Labels:

Comments

Post a Comment

Popular posts from this blog

Creating no-reply@domain.com account in Postfix

If you wanted to send emails to users but did not want to receive any replies to the email, you would need to setup a no-reply@domain.com email account. These kind of email ids are useful when sending emails containing forgotten passwords or activation code. Below are the steps for creating such account in Postfix. 1. Identify the file containing alias for Postfix First, make sure the following line in the ALIAS DATABASE section of the /etc/postfix/main.cf is NOT commented out: alias_maps = hash:/etc/aliases 2. Create an alias that redirects messages to /dev/null Edit /etc/aliases and add following entry devnull: /dev/null 3. Create a virtual email id Edit /etc/postfix/virtual and add following entry no-reply@domain.com devnull 4. refresh postfix alias and postfix cache Execute following commands. (You may require root privileges) > newaliases > postfix reload
4 comments
Read more

jupyter notebook execution error: "http://localhost:8889/tree?token=xxx" doesn’t understand the “open location” message

I got this error when I tried to launch jupyter notebook on a mac. It is not a fatal error. I could still go to browser directly and copy/paste the url manually. The error indicates that when the command automatically tried to launch a browser, it couldn't find the default browser in jupyter configuration file. The easy fix is to specify the browser. Here are the steps to do so; 1.   Open ~/.jupyter/jupyter_notebook_config.py in an editor.       If the file does not exist then you can create a default config file by typing the following command;       jupyter notebook --generate-config 2. Search for a word "browser" to locate a following line.     #c.NotebookApp.browser = ''     By default it is commented. You can uncomment it and use one of the following values depending on your browser preference.     # set default browser to chrome     c.NotebookApp.browser = 'chrome'     ...
Post a Comment
Read more

.ssh/config: “Bad configuration option: UseKeychain” on Mac OS

After upgrading Mac OS to Mojave I started seeing this error when doing "git pull". I was able to follow the steps below as described here ; 1. open ssh config vi ~/.ssh/config 2. Add the following lines to ssh config to keep your configuration compatible with both new and old versions of openssh. IgnoreUnknown UseKeychain UseKeychain yes That fixed the issue for me. Try running git pull again.    More details about the issue are available here . 
Post a Comment
Read more