Showing posts with label Google. Show all posts
Showing posts with label Google. Show all posts

Friday, February 12, 2010

Push Google Buzz buzz onto Twitter and Facebook

Until Google Buzz supports pushing updates natively here is a quick guide how to push your buzzes to social networking websites.
  1. Click 'buzz' in your GMail account
  2. Click on your name
  3. Click “Google Profile”
  4. Click on rss button in your browser to get the feed (http://buzz.googleapis.com/feeds/NNNNN/public/posted where NNNNN long string of numbers from your Google Profile URL)
  5. Go to twitterfeed.com to set up pushing your buzz feed to Twitter, Identi.ca, Facebook or pretty much to any social site using Ping.fm 
(from http://bit.ly/ahGKla)

Friday, December 25, 2009

Open Source as seen by Google

Jonathan Rosenberg, senior vice-president of product management at Google, put up on Dec. 21 what was more of a tome than a mere post on the company's blog. Entitled "The Meaning of Open," it was originally sent to Google employees as an e-mail, but it reads like a manifesto. It can be found here.

Jonathan Rosenberb says:
At Google we believe that open systems win. They lead to more innovation, value, and freedom of choice for consumers, and a vibrant, profitable, and competitive ecosystem for businesses. Many companies will claim roughly the same thing since they know that declaring themselves to be open is both good for their brand and completely without risk. After all, in our industry there is no clear definition of what open really means. It is a Rashomon-like term: highly subjective and vitally important.

The topic of open seems to be coming up a lot lately at Google. I've been in meetings where we're discussing a product and someone says something to the effect that we should be more open. Then a debate ensues which reveals that even though most everyone in the room believes in open we don't necessarily agree on what it means in practice.

This is happening often enough for me to conclude that we need to lay out our definition of open in clear terms that we can all understand and support. What follows is that definition based on my experiences at Google and the input of several colleagues. We run the company and make our product decisions based on these principles, so I encourage you to carefully read, review, and debate them. Then own them and try to incorporate them into your work. This is a complex subject and if there is debate (and I'm sure there will be) it should be in the open! Please feel free to comment.
He ends the post with:
Open will win. It will win on the Internet and will then cascade across many walks of life: The future of government is transparency. The future of commerce is information symmetry. The future of culture is freedom. The future of science and medicine is collaboration. The future of entertainment is participation. Each of these futures depends on an open Internet.


(Check out Jonathan Rosenberb blog for more)

Wednesday, December 09, 2009

Google Chrome Official release for Linux

Google has finally 'Officially' released Google Chrome for Linux (on 08 Dec 09). It is available at http://www.google.com/chrome/intl/en/w00t.html

Definitely the Linux fans are cheering!!


Also check out the loads of extensions/addons for the Google Chrome, a la 'Firefox'. Get it from here. Hope these extensions don't make Chrome as bloated as Firefox has become!!
Enjoy the web experience with Chrome - though for me, for the time being 'Firefox' would be my primary browser!! For the time being at least!!

Saturday, December 05, 2009

OpenDNS response to Google's DNS Service

Continuing with the news of Google's new free DNS Service which I posted earlier, the response from the OpenDNS founder is interesting and relevant. From his blog at:
http://blog.opendns.com/2009/12/03/opendns-google-dns/

Visit the site to check out the interesting comments readers have also made
- gantayet

====Extract from the blog=====

Some thoughts on Google DNS 
by David Ulevitch, Founder on Dec 3rd, 2009


Google launched a DNS service today, almost exactly four years after I started OpenDNS. This comes as no surprise as it was only a matter of time before one of the Internet giants realized the strategic importance of DNS. I’ve received a lot of questions from bloggers, journalists, friends and most importantly, our users. And so I want to share my thoughts on what this means for the recursive DNS space and what it means for OpenDNS.

First, it’s not the same as OpenDNS. When you use Google DNS, you are getting the experience they prescribe. When you use OpenDNS, you get the Dashboard controls to manage your experience the way you want for you, your family or your organization. People use OpenDNS because we are pioneers and innovators in the DNS space, offering the most secure recursive DNS service around. We run the largest DNS caches, the fastest resolvers, and we offer the most flexibility in controlling your DNS experience. For example, IT folks want to block malware in the DNS, parents sometimes want to block certain content from kids. All of that and more is possible with our DNS. It is not with Google DNS. Of course, we don’t force those things, we offer them as controls that you manage the way you see fit. Providing people with choice is core to our offerings.

Second, it means that Google realizes that DNS is a critical piece of our Internet’s infrastructure and that it’s of strategic importance to help people safely and reliably navigate the Internet. This is something we’ve championed since day one and will always keep as our primary mission. This is why big enterprise customers are switching to OpenDNS too, not because it’s free but because it’s the best and we add value to DNS and improve the security of their networks.

Third, Google claims that this service is better because it has no ads or redirection. But you have to remember they are also the largest advertising and redirection company on the Internet. To think that Google’s DNS service is for the benefit of the Internet would be naive. They know there is value in controlling more of your Internet experience and I would expect them to explore that fully. And of course, we always have protected user privacy and have never sold our DNS data. Here’s a link to our privacy policy.

Fourth, it means that Google is bringing awareness to a wide audience that there is a choice when it comes to DNS and that users don’t have to settle for what their ISP provides. And we believe that having choice is a good thing — just as Internet users have unbundled their email to services like Gmail, Yahoo! Mail and Hotmail people have been unbundling their DNS and switching to OpenDNS in huge numbers for the last 3+ years because we’re better.

Fifth, it’s not clear that Internet users really want Google to keep control over so much more of their Internet experience than they do already — from Chrome OS at the bottom of the stack to Google Search at the top, it is becoming an end-to-end infrastructure all run by Google, the largest advertising company in the world. I prefer a heterogeneous Internet with lots of parties collaborating to make this thing work as opposed to an Internet run by one big company.
So how will this impact us? It’s too early to tell, but largely I think this is a good thing for us. Google DNS currently offers none of the choice and flexibility that our service does. It’s new and untested. Having said that, it encourages us to keep making our service better. And ultimately, we’re a business that has been growing aggressively since we launched and has been competing in fair markets and winning. It raises awareness about the importance of DNS and it motivates us to continue providing world-class services to a global audience and to keep innovating.



We will continue to do that without distraction from Google or any of the other players in the DNS or security space. But we welcome Google to the neighborhood.

Friday, December 04, 2009

Faster web browsing using Google's DNS servers

A great news that I was waiting for!! You can now have faster web browsing experience using Google's DNS services!!

Google has launched a Public DNS (Domain Name Service) server and the details are available here.

Simply put, you can abandon the DNS IP addresses given by your ISPs like MTNL, BSNL or local Broadband provider and use the Google DNS IP addresses 8.8.8.8 or 8.8.4.4 

What is DNS? Simply put - when you type in a website address 'Name' on your web browser, say like http://www.google.com, your computer queries a DNS server (setup by your systems DNS setting IP address!!) to get an IP address (in this case http://www.google.com translates to http://209.85.231.99), and then proceeds to connect to the IP address that it gets from the DNS server. The above process is called as 'Name to IP address' resolving and is a very critical part (and time consuming) of every web browsing activity.

Generally, if the DNS server of your local ISP server is not configured/ administered properly, the 'Name to IP address' resolving takes some time. And when you realise that a single web page has many such 'Names', using the Google Public DNS server will save considerable time during the web browsing.


The Advantages?? Definitely faster browsing speed which would be noticeable. On a Linux machine, you can check yourself the speed advantages by giving these commands at the command prompt and comparing the time shown (my results showed a 50% time saving!!):
time dig @ www.blogspot.com
time dig @8.8.8.8 www.blogspot.com
time dig @8.8.4.4 www.blogspot.com

Other advantages (quoting from the Google Blog!):
  • Speed: Resolver-side cache misses are one of the primary contributors to sluggish DNS responses. Clever caching techniques can help increase the speed of these responses. Google Public DNS implements prefetching: before the TTL on a record expires, we refresh the record continuously, asychronously and independently of user requests for a large number of popular domains. This allows Google Public DNS to serve many DNS requests in the round trip time it takes a packet to travel to our servers and back.
  • Security: DNS is vulnerable to spoofing attacks that can poison the cache of a nameserver and can route all its users to a malicious website. Until new protocols like DNSSEC get widely adopted, resolvers need to take additional measures to keep their caches secure. Google Public DNS makes it more difficult for attackers to spoof valid responses by randomizing the case of query names and including additional data in its DNS messages.
  • Validity: Google Public DNS complies with the DNS standards and gives the user the exact response his or her computer expects without performing any blocking, filtering, or redirection that may hamper a user's browsing experience.

Sunday, November 08, 2009

How Google uses Linux

A great article on how Google uses Linux - http://lwn.net/Articles/357658/

An interesting read for the technical minded friends!!

On licensing issues, the below comments found at the site is very interesting. Have quoted here for quick read!!

====Some Comments to article quoted below=====

What a waste of resources...Google could just work tied with the kernel community. Come on Google what are you waiting for? Besides this fact, if linux kernel code is GPLv2 why don't they release their code and respect GPLv2 license terms?

===>> Reply==>>


KS2009: How Google uses Linux
Posted Oct 21, 2009 14:36 UTC (Wed) by drag (subscriber, #31333)
I don't know if you noticed or not, but the GPL licensing terms only kick in
during distribution. Seeing how a corporation is a independent legal person I
don't think that moving software and hardware around internally really counts
as distribution. And I don't think that Google has any plans on selling its
systems to other people.
So the GPL is pretty irrelevant.

So it is just a business case of whether working with the kernel community is
going to be more profitable or not. And so far they decided that taking care
of stuff internally is a better approach. Maybe that will change.

===>> Reply ==>>


GPL doesn't require, but maintenance kills you
Posted Oct 21, 2009 15:00 UTC (Wed) by dwheeler (subscriber, #1216)
Correct, the GPL doesn't require the release of this internal source code. However, the GPL does have an effect (by intent): Google cannot take the GPL'ed program, modify it, and sell the result as a proprietary program. Thus, what Google is doing is almost certainly wasting its own resources, by trying to do its own parallel maintenance. They could probably save a lot of money and time by working with the kernel developers; it's a short-term cost for long-term gain. And as a side-effect, doing so would help all other kernel users.
There's probably some stuff that will stay Google-only, but if they worked to halve it, they'd probably save far more than half their money. Google can do this, in spite of its long-term inefficiencies, because they have a lot of money... but that doesn't mean it's the best choice for them or anyone else.