Google Plus Update On Privacy Issues Shimrit Ben-Yair Posted In he Blog Post About Public Feedback and Make New Improvements In Privacy In comming Few Days.
"Thanks for all the great feedback everyone! We're paying special attention to privacy-related issues, which is why we're rolling a new improvement to Google+ over the next few days.
Changing your public profile picture or scrapbook photos will no longer generate a public post to the stream, just to the people you have in your circles. So only people in your circles will engage in discussions about the photos you post.
Thanks again and keep the feedback coming!'
Wednesday, 20 July 2011
Tuesday, 19 July 2011
Finally Google+ App For Iphone Got Approved
| Tweet |
Description
Google+ for mobile makes sharing the right things with the right people a lot simpler. Huddle lets you send super-fast messages to the people you care about most. And no matter where you are, the stream lets you stay in the loop about what your friends are sharing and where they’re checking in.
Click Here FoR App
Google+ for mobile makes sharing the right things with the right people a lot simpler. Huddle lets you send super-fast messages to the people you care about most. And no matter where you are, the stream lets you stay in the loop about what your friends are sharing and where they’re checking in.
Google's New URL Shortner g.co Exclusively For Google Products Only.
| Tweet |
Google has unveiled g.co, a new URL shortener that will link only to Google products and websites.
The search giant already owns goo.gl, a URL shortener it launched in 2009. Unlike g.co, the goo.gl URL shortener can be used for any link on the web via the Google Toolbar.
“We’ll only use g.co to send you to webpages that are owned by Google, and only we can create g.co shortcuts,” Google VP of Consumer Marketing Gary Briggs stated on the company’s blog. “That means you can visit a g.co shortcut confident you will always end up at a page for a Google product or service.”
The tech titan, which has been using the goo.gl URL shortener for its products until now, clearly wants to limit the confusion about where its goo.gl links lead to. Separating Google products from goo.gl should go a long way to solving that problem.
Google isn’t the only company to use .co as its official URL shortener. Twitter obtained t.co last year to improve how links are shared and secured on its platform.
The search giant already owns goo.gl, a URL shortener it launched in 2009. Unlike g.co, the goo.gl URL shortener can be used for any link on the web via the Google Toolbar.
“We’ll only use g.co to send you to webpages that are owned by Google, and only we can create g.co shortcuts,” Google VP of Consumer Marketing Gary Briggs stated on the company’s blog. “That means you can visit a g.co shortcut confident you will always end up at a page for a Google product or service.”
The tech titan, which has been using the goo.gl URL shortener for its products until now, clearly wants to limit the confusion about where its goo.gl links lead to. Separating Google products from goo.gl should go a long way to solving that problem.
Google isn’t the only company to use .co as its official URL shortener. Twitter obtained t.co last year to improve how links are shared and secured on its platform.
Dell wants to use Google+ Hangouts for customer service
| Tweet |
Dell could soon use Google’s new group video chat platform Google+ Hangouts as an alternative to the traditional customer service call, according to the company’s chairman and CEO, Michael Dell.
Hangouts has been hailed as the next big killer app, and Michael Dell is obviously a fan as well. He’s used the video chat more than a dozen times since he joined Google+ in early July, and this Sunday, he posted the following question on Google+:
I am thinking about hangouts for business. Would you like to be able to connect with your Dell service and sale teams via video directly from Dell.com?
The reaction to his post was overwhelmingly positive, with hundreds of comments agreeing that this would be a good idea for Dell. And the idea is indeed intriguing: Some customer service needs are very similar, so having a service representative talk to a small group of customers at the same time could be more economical than the traditional one-on-one call. Using video could also humanize tech support, and group settings could even initiate self-help between customers.
One should note that Dell’s idea of launching a Hangouts session directly from Dell.com isn’t currently possible; Google+ is still invite-only, and Hangouts can only be started or joined from within the network. Google also hasn’t opened its social network for businesses yet, but the company is currently evaluating how to integrate brands and businesses into Google+.
Customer service has been one of the applications that has made Twitter attractive to companies like Comcast. Having the ability to directly talk to customers via group video chat could be the next step for many of these companies as they look for ways to take customer service beyond the traditional call-center script.
Hangouts has been hailed as the next big killer app, and Michael Dell is obviously a fan as well. He’s used the video chat more than a dozen times since he joined Google+ in early July, and this Sunday, he posted the following question on Google+:
I am thinking about hangouts for business. Would you like to be able to connect with your Dell service and sale teams via video directly from Dell.com?
The reaction to his post was overwhelmingly positive, with hundreds of comments agreeing that this would be a good idea for Dell. And the idea is indeed intriguing: Some customer service needs are very similar, so having a service representative talk to a small group of customers at the same time could be more economical than the traditional one-on-one call. Using video could also humanize tech support, and group settings could even initiate self-help between customers.
One should note that Dell’s idea of launching a Hangouts session directly from Dell.com isn’t currently possible; Google+ is still invite-only, and Hangouts can only be started or joined from within the network. Google also hasn’t opened its social network for businesses yet, but the company is currently evaluating how to integrate brands and businesses into Google+.
Customer service has been one of the applications that has made Twitter attractive to companies like Comcast. Having the ability to directly talk to customers via group video chat could be the next step for many of these companies as they look for ways to take customer service beyond the traditional call-center script.
Monday, 18 July 2011
Google+ Is Built Using Tools You Can Use Too Like Closure, Java Servlets, JavaScript, BigTable, Colossus, Quick Turnaround
| Tweet |
Joseph Smarr, former CTO of Plaxo in I'm a technical lead on the Google+ team. Ask me anything, reveals the stack used for building Google+.
Our stack is pretty standard fare for Google apps these days: we use Java servlets for our server code and JavaScript for the browser-side of the UI, largely built with the (open-source) Closure framework, including Closure's JavaScript compiler and template system. A couple nifty tricks we do: we use the HTML5 History API to maintain pretty-looking URLs even though it's an AJAX app (falling back on hash-fragments for older browsers); and we often render our Closure templates server-side so the page renders before any JavaScript is loaded, then the JavaScript finds the right DOM nodes and hooks up event handlers, etc. to make it responsive (as a result, if you're on a slow connection and you click on stuff really fast, you may notice a lag before it does anything, but luckily most people don't run into this in practice). Our backends are built mostly on top of BigTable and Colossus/GFS, and we use a lot of other common Google technologies such as MapReduce (again, like many other Google apps do).
t first I read Clojure, which would have been a real surprise, but it's Closure, a suite of JavaScript tools consisting of a library, compiler, and templates. The compiler is a true compiler for JavaScript for making JavaScript download and run faster. The library is modular and cross-browser JavaScript library. Templates is a server-side templating system that helps you dynamically build reusable HTML and UI elements. It's all open source so you can use it too.
While you don't have Google's stack available to you, you do have some open source options. HBase is replacement for BigTable. Then there's Hadoop MapReduce. Colossus is Google's next generation file system, a replacement for GFS. Since we don't know much about Colossus, it's hard to say what a suitable replacement would be. There's the Hadoop distributed file system HDFS. And if you are looking for some of the cloud like infrastructure glue there's OpenStack (which also has storage system).
Google probably uses a custom Java servlet container, but the choice here doesn't matter that much. Most of the work will be spawned in parallel and performed on other servers implemented in C++, Java, or Python.
Whereas most communication with Google is non-existent, the Google+ development team is noticeably more responsive, turning out visible improvements quickly and consistently. Joseph tells us why: We put extra emphasis on engineering speed/agility--we try to release code updates on a daily basis while still keeping quality/stability/latency as high as you'd expect from google. This helps us move fast and respond quickly to user feedback. We try to do a full push (almost) every day, and we sometimes sneak in patch releases too if needed. But there are humans in the loop, it's not a "auto-push if all tests pass" situation or anything like that.
For Google+'s most innovative feature, video conferencing with Hangouts, GigaOM has a good article on that stack, which is based on Announcing Google+ Hangouts, written by Tech Lead Justin Uberti. Unlike Skype, which runs on a cost effective P2P model, Hangouts is completely hosted by Google. This must cost a staggering amount of money. You are on your own here. Nobody can replace the bandwidth being donated by the Google fairy.
That's Google in a box. Then again, an ex-Googler thinks you can do better using MessagePack, JSON, Hadoop, jQuery, and MongoDB. If you can do better for a world wide base of a billion users is a completely different question.
Our stack is pretty standard fare for Google apps these days: we use Java servlets for our server code and JavaScript for the browser-side of the UI, largely built with the (open-source) Closure framework, including Closure's JavaScript compiler and template system. A couple nifty tricks we do: we use the HTML5 History API to maintain pretty-looking URLs even though it's an AJAX app (falling back on hash-fragments for older browsers); and we often render our Closure templates server-side so the page renders before any JavaScript is loaded, then the JavaScript finds the right DOM nodes and hooks up event handlers, etc. to make it responsive (as a result, if you're on a slow connection and you click on stuff really fast, you may notice a lag before it does anything, but luckily most people don't run into this in practice). Our backends are built mostly on top of BigTable and Colossus/GFS, and we use a lot of other common Google technologies such as MapReduce (again, like many other Google apps do).
t first I read Clojure, which would have been a real surprise, but it's Closure, a suite of JavaScript tools consisting of a library, compiler, and templates. The compiler is a true compiler for JavaScript for making JavaScript download and run faster. The library is modular and cross-browser JavaScript library. Templates is a server-side templating system that helps you dynamically build reusable HTML and UI elements. It's all open source so you can use it too.
While you don't have Google's stack available to you, you do have some open source options. HBase is replacement for BigTable. Then there's Hadoop MapReduce. Colossus is Google's next generation file system, a replacement for GFS. Since we don't know much about Colossus, it's hard to say what a suitable replacement would be. There's the Hadoop distributed file system HDFS. And if you are looking for some of the cloud like infrastructure glue there's OpenStack (which also has storage system).
Google probably uses a custom Java servlet container, but the choice here doesn't matter that much. Most of the work will be spawned in parallel and performed on other servers implemented in C++, Java, or Python.
Whereas most communication with Google is non-existent, the Google+ development team is noticeably more responsive, turning out visible improvements quickly and consistently. Joseph tells us why: We put extra emphasis on engineering speed/agility--we try to release code updates on a daily basis while still keeping quality/stability/latency as high as you'd expect from google. This helps us move fast and respond quickly to user feedback. We try to do a full push (almost) every day, and we sometimes sneak in patch releases too if needed. But there are humans in the loop, it's not a "auto-push if all tests pass" situation or anything like that.
For Google+'s most innovative feature, video conferencing with Hangouts, GigaOM has a good article on that stack, which is based on Announcing Google+ Hangouts, written by Tech Lead Justin Uberti. Unlike Skype, which runs on a cost effective P2P model, Hangouts is completely hosted by Google. This must cost a staggering amount of money. You are on your own here. Nobody can replace the bandwidth being donated by the Google fairy.
That's Google in a box. Then again, an ex-Googler thinks you can do better using MessagePack, JSON, Hadoop, jQuery, and MongoDB. If you can do better for a world wide base of a billion users is a completely different question.
Subscribe to:
Comments (Atom)