Introducing the Google Chrome OS

It's been an exciting nine months since we launched the Google Chrome browser. Already, over 30 million people use it regularly. We designed Google Chrome for people who live on the web — searching for information, checking email, catching up on the news, shopping or just staying in touch with friends. However, the operating systems that browsers run on were designed in an era where there was no web. So today, we're announcing a new project that's a natural extension of Google Chrome — the Google Chrome Operating System. It's our attempt to re-think what operating systems should be.

Google Chrome OS is an open source, lightweight operating system that will initially be targeted at netbooks. Later this year we will open-source its code, and netbooks running Google Chrome OS will be available for consumers in the second half of 2010. Because we're already talking to partners about the project, and we'll soon be working with the open source community, we wanted to share our vision now so everyone understands what we are trying to achieve.

Speed, simplicity and security are the key aspects of Google Chrome OS. We're designing the OS to be fast and lightweight, to start up and get you onto the web in a few seconds. The user interface is minimal to stay out of your way, and most of the user experience takes place on the web. And as we did for the Google Chrome browser, we are going back to the basics and completely redesigning the underlying security architecture of the OS so that users don't have to deal with viruses, malware and security updates. It should just work.

Google Chrome OS will run on both x86 as well as ARM chips and we are working with multiple OEMs to bring a number of netbooks to market next year. The software architecture is simple — Google Chrome running within a new windowing system on top of a Linux kernel. For application developers, the web is the platform. All web-based applications will automatically work and new applications can be written using your favorite web technologies. And of course, these apps will run not only on Google Chrome OS, but on any standards-based browser on Windows, Mac and Linux thereby giving developers the largest user base of any platform.


Google Chrome OS is a new project, separate from Android. Android was designed from the beginning to work across a variety of devices from phones to set-top boxes to netbooks. Google Chrome OS is being created for people who spend most of their time on the web, and is being designed to power computers ranging from small netbooks to full-size desktop systems. While there are areas where Google Chrome OS and Android overlap, we believe choice will drive innovation for the benefit of everyone, including Google.

We hear a lot from our users and their message is clear — computers need to get better. People want to get to their email instantly, without wasting time waiting for their computers to boot and browsers to start up. They want their computers to always run as fast as when they first bought them. They want their data to be accessible to them wherever they are and not have to worry about losing their computer or forgetting to back up files. Even more importantly, they don't want to spend hours configuring their computers to work with every new piece of hardware, or have to worry about constant software updates. And any time our users have a better computing experience, Google benefits as well by having happier users who are more likely to spend time on the Internet.


We have a lot of work to do, and we're definitely going to need a lot of help from the open source community to accomplish this vision. We're excited for what's to come and we hope you are too. Stay tuned for more updates in the fall and have a great summer.

Posted by Sundar Pichai, VP Product Management and Linus Upson, Engineering Director

Source : http://googleblog.blogspot.com/2009/07/introducing-google-chrome-os.html

Google Tricks

Enter just the word http for your search to find the top 1000 PageRanked sites.

Enter only www in your search to see how Google ranks the top 1,000 sites.

Manually type the following prefixes and note their utility:

# link:url Shows other pages with links to that url.
# related:url same as "what's related" on serps.
# site:domain restricts search results to the given domain.
# allinurl: shows only pages with all terms in the url.
# inurl: like allinurl, but only for the next query word.
# allintitle: shows only results with terms in title.
# intitle: similar to allintitle, but only for the next word. "intitle:seoforgoogle google" finds only pages with seoforgoogle in the title, and google anywhere on the page.
# cache:url will show the Google version of the passed url.
# info:url will show a page containing links to related searches, backlinks, and pages containing the url. This is the same as typing the url into the search box.
# spell: will spell check your query and search for it.
# stocks: will lookup the search query in a stock index.
# filetype: will restrict searches to that filetype. "-filetype:pdf" to remove Adobe PDF files.
# daterange: is supported in Julian date format only. 2452384 is an example of a Julian date.
# maps: If you enter a street address, a link to Yahoo Maps and to MapBlast will be presented.
# phone: enter anything that looks like a phone number to have a name and address displayed. Same is true for something that looks like an address (include a name and zip code)
# site:www.somesite.net "+www.somesite.+net" - (tells you how many pages of your site are indexed by google)
# allintext: searches only within text of pages, but not in the links or page title
# allinlinks: searches only within links, not text or title

Source : http://www.seoforgoogle.com/google-tricks.cfm

How to Create Google Adsense Pages

First let me preface this article by stating that you should NOT create pages for the "gaming" of AdSense. Most companies who use AdWords are small to medium sized businesses trying to grow.

With rampant click fraud, those advertisers won't be able to advertise, and AdSense won't pay out as well.

That said, let's begin the process.

For our example, our topic is that of "widgets", so where do get started?

Create the page - Sounds simple enough, but there are some coding standards you should always use. They are:

* Name of the page - Use the name of the keyword you are targeting. So, in this example it would be widget.htm. You can use your web server's technology as well, but if in doubt, you can never go wrong with the .htm
* Title the page - Use the keyword again for the title.
* Meta Tags - Yes, they are still used. Make sure you include the keywords in your meta keyword list, and give a definition of the word in your meta description tag
* H1 - Put your keyword in stylized H1 tags. Use CSS to make the tag look consistent to the rest of your site

Content - This is often the biggest obstacle non-writers have. Don't worry, follow these steps and you'll soon be on your way to original content.

* Go to MSN, Yahoo and Google
* Enter your keyword into the search box
* Look at the top 5 sites listed from each search engine
* Educate yourself on the topic from the content found on these sites

Page Copy - Now that you've absorbed more information, compose your own page of ORIGINAL content. You can take bits and pieces from the other pages, but be sure to inject your personality into your writing. That will make it uniquely yours.

Links - Don't forget to link to authority sites about your subject. It's very natural for web pages to have links to other sites, don't forget about this key point. Take a moment to see why you need outbound links.

Traffic - The most obvious is getting traffic to your site. Your site will have higher paying ads if your page gets more traffic. If you need help with this, be sure to visit the SEO resources section.

Personally, I tried using the traffic generating sites, and quite frankly, they are a waste of time. Sure you'll build up your traffic numbers, but it's usually from an autosurfing program.

One last note. On September 1st, 2005 Google shut down my account because they suspected click fraud. I really don't have a problem with them shutting me down, because as an advertiser I want to know that they are watching my money. However, I believe they should show proof of the supposed fraudulent activity. I was even proactive in letting them know when I saw suspicious activity, but they never replied to my inquires.

Here's a great article on what to watch for, and how click fraud is committed.

I hope you have better luck than I did.

Paul Bliss
www.SEOforGoogle.com

Source : http://seoarticles.seoforgoogle.com/How-to-Create-Google-Adsense-Pages.cfm

How to Create a Google Site Map

Officially announced on June 6th, 2005 at Google'e Blog, Google Site Map allows you to submit a listing of all your urls for Google to crawl.

There have been many questions concerning the procedure of creating a Google Site Map. Below is the non-Python way of creating one. (Note: Google has further documentation at their site)

First, create a file named sitemap.xml

Use the following code in any HTML editor:


<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.google.com/schemas/sitemap/0.84">
<url>
<loc>http://www.seoforgoogle.com/
<lastmod>2005-06-30T14:12:14+00:00
<changefreq>daily
<priority>1.0
</url>
<url>
<loc>http://www.seoforgoogle.com/glossary.cfm
<lastmod>2005-06-30T14:12:14+00:00
<changefreq>weekly
<priority>1.0
</url>
</urlset>


Here's a breakdown of those properties:

lastmod -
This is the date the document was last modified and uses the following formats:

dd.mm.yyyy
dd.mm.yyyy hh:mm
dd/mm/yyyy
dd/mm/yyyy hh:mm

changefreq -
Tells Google Sitemaps the frequently that content of a particular URL will change.

Your options are "always", "hourly", "daily", "weekly", "monthly", "yearly" or "never".

The value "always" should be used to describe documents that change each time they are accessed. The value "never" should be used to describe archived URLs.

priority -
The priority of a particular URL relative to other pages on your site.
You may select between 0.0 and 1.0, where 0.0 identifies the lowest priority page(s) on your website and 1.0 identifies the highest priority page(s) on your website.

Add as many pages as there are in your website.

Google Sitemap supports up to 50,000 pages per XML file.

Once you've completed all of those steps, you'll need to submit your site map page.

Submit to: (requires gmail account)

https://www.google.com/webmasters/sitemaps/login

[If you don't have a gmail account send an email requesting a gmail account and I'll give them out until I run out of invites. (ts@seoforgoogle.com)]

-To your online success!

Paul Bliss
www.SEOforGoogle.com

Source : http://seoarticles.seoforgoogle.com/How-to-Create-a-Google-Site-Map.cfm

গুগুল মনে করিয়ে দিবে আপনার কাজ

নিকটজনের জন্ম তারিখ, বিশেষ মুহুর্ত বা দরকারি কাজের সময় যদি ভুলে যান এবঙ সময়ান্তে মনে পড়ে, তাহলে নিজের চুল ছিড়তে ইচ্ছে হয় না কার ! কেউ যদি আপনাকে এসএমএস এর মাধ্যমে এসব গুরুত্ব পূর্ণ মুহুর্তের আগে জানিয়ে দেয় তাহলে কেমন হয়।
গুগুল ক্যালেন্ডার আপনার ইভেন্ট গুলোর নিদ্দিষ্ট সময় আগেই আপনার মোবাইলে এবং ই-মেইলে রিমান্ডার হিসেবে জানিয়ে দেবে, তাও আবার বিনে পয়সায়।

এ জন্য আপনার গুগুল একাউন্ট থাকতে হবে ।।



গুগুল ক্যালেন্ডার প্রবেশের জন্য জি-মেইলে ঢুকে ওপরের Calander Link এ ক্লিক করে অথবা সরাসরি www.google.com/calendar সাইটে গিয়ে লগইন করতে পারেন। এবার Settings-এ ক্লিক করে Mobile Setup ট্যাবে ক্লিক করুন। Phone number অংশে +৮৮ সহ আপনার মোবাইল নম্বর দিন এবং Send Verification Code-এ ক্লিক করুন, তাহলে আপনার মোবাইলে ভেরিফিকেমন কোড আসবে। বর্তমানে বাংলাদেশের গ্রামীণফোন, একটেল এবং ওয়ারিদ গ্রহকেরা এই সুবিধা পাবেন। এবার আপনার মোবাইলে আসা ভেরিফিকেশন কোডটি Verification code টেক্সট বক্সে লিখে Finish setup বাটেন ক্লিক করে ভেরিফিকেশন সমাপ্ত করুন। এখানে By default, remind me via-এর ড্রপডাউন থেকে SMS নির্বাচন করুন এবঙ ইভেন্টের কত সময় আগে এসএমএস পেতে চান তা লিখুন এবং Choose how you would like to be notified-এর SMS অংশে সবগুলো চেক বক্স চেক করে সেভ করুন। ব্যস এখন থেকে গুগুল ক্যারেন্ডারে আপনার ইভেন্টের নিদিষ্ট সময় আগে আপনার মোবাইলে বার্তা আসবে ।

Register your mobile phone

To register your mobile phone with Google Calendar, you need to obtain a verification code. Here's how:

1. Click Settings at the top of any Google Calendar page, then select the Mobile Setup tab.
2. Select your country from the 'Country' drop-down menu.
3. Enter your phone number in the 'Phone number' field.
4. Select your carrier from the drop-down menu, if applicable. However, if you see the link See Help Center for supported providers, please check if your provider is supported before requesting your verification code.
5. If your carrier is supported, click the Send Verification Code button, and you'll get a text message on your phone.
6. Once you receive this message, enter the code you received into the 'Verification code' box and click the Finish setup button.

Source : প্রথম আলো ১লা জুলাই ২০০৯

Could Not Connect To Blogger.Com - A Possible Workaround

One possible reason for the odd distribution of the well known pink warning

Could not connect to Blogger.com. Saving and publishing may fail.

or similarly

Cannot View Webpage

may be that it involves several different problems, coming together.


It's possible that Pete Hopkins explains one of the problems as a side effect of the cookies generated by Blogger, some of which are used in post editor.

Cookies are normally small and unassuming, but there's a bit of unusual behavior in that Blogger automatically saves the first few k of your post in a set of cookies as you're typing. That way, if your browser crashes you can use the "recover post" link to get at least the first part of it back. However, the side effect of using cookies in this way is that even though they're only being used (abused?) for local/offline storage, your browser will send the cookies with every request to a blogger.com server.


This might explain why some Bloggers report temporary relief by clearing cache and cookies, and other Bloggers report relief by making shorter posts - Publishing, then editing repeatedly.

Pete continues in his discussion, to suggest a workaround, to block the problem created by the cookies. You'll have a little script, that you'll have to run each time you start a post editor session. You run the little script, having previously saved it as a bookmark (favorite), from your browser.

* Go to Pete's website.
* Make a bookmark from the code that he provides, per his instructions.
* Each time that your browser links to a screen where the Blogger connection testing is done (anywhere you see the pink error message), execute the bookmark, created from Pete's website, after the page has loaded.
* See the WikiPedia article about bookmarklets, for more information.


Various Bloggers have reported mitigation of the well known pink warning, when using Pete's bookmarklet. Give it a shot, and see if it provides you any improvement to your problem.

Solution : stop post backup

Source :
Could Not Connect To Blogger.Com
Pete's website

What is the AJAX Libraries API?

The AJAX Libraries API is a content distribution network and loading architecture for the most popular, open source JavaScript libraries. By using the Google AJAX API Loader's google.load() method, your application has high speed, globaly available access to a growing list of the most popular, open source JavaScript libraries including:

• jQuery
• jQuery UI
• Prototype
• script.aculo.us
• MooTools
• Dojo
• SWFObject^New!
• Yahoo! User Interface Library (YUI)^New!

Google works directly with the key stake holders for each library effort and accepts the latest stable versions as they are released. Once we host a release of a given library, we are committed to hosting that release indefinitely.

The AJAX Libraries API takes the pain out of developing mashups in JavaScript while using a collection of libraries. We take the pain out of hosting the libraries, correctly setting cache headers, staying up to date with the most recent bug fixes, etc.

// Load jQuery
google.load("jquery", "1");
// on page load complete, fire off a jQuery json-p query
// against Google web search
google.setOnLoadCallback(function() {
  $.getJSON("http://ajax.googleapis.com/ajax/services/search/web?q=google&v=1.0&callback=?",
    // on search completion, process the results
    function (data) {
      if (data.responseData.results &&
          data.responseData.results.length > 0) {
        var results = data.responseData.results;
        for (var i=0; i < results.length; i++) {
          // Display each result however you wish
          alert(results[i].titleNoFormatting);
        }    
      }
    });
});

Getting Adsense Payment in Bangladesh

New and potential Adsense publishers of Bangladesh have many questions and confusions regarding getting payments from Adsense. Here in this article I'll clarify some confusions from my personal experience :)

1. Address verification: After your earnings reach $10, Google will send you a letter by post [not email] containing secret PIN. This will be sent to you to verify if your address is okay. You'll be required to insert the PIN in your account and verify your existence! This is a primary and a very critical step as you'll be eligible to receive all future payments only after you pass this step successfully. It takes 3-4 weeks for the PIN letter to reach Bangladesh from USA.

2. Payment Options: For Bangladeshi publishers, the only option so far for receiving payments is by check. You can choose from either Standard Delivery check [this is free and arrives within 3-4 weeks by regular mail] or Secured Express Delivery check [$28 fee and arrives in a week]. There are lots of complains on Bangladesh Post Offices, but my experience with them is good! I received Standard Delivery check in time intact!

In Bangladesh we can't receive Adsense payments through Western Union or credit/debit cards.

3. Eligibility of getting first payment: Once you earn $100, you're ready to have your first payment from Google Adsense! Google will send you the payment check at the end of next month after you reach $100 in any month. Confused? Don't be! To make it more clear - My earnings reached $100 in February and Google sent me the check just before the end of March.

4. Timeline: A very common question from publishers are, "How much time does the check requires to reach to my address?" The answer is - 3/4 weeks from the delivery date. You can find the delivery date under 'Payment History' in your Adsense account anytime.

5. Converting check to cash: You can convert the check from any commercial bank in Bangladesh. Just make sure that the payee name in your Adsense account and your bank account name is identically the same. But the bank won't convert it to cash straight away; again you have to be patient! The bank will take 3/4 weeks to convert your check. And shockingly, the fee bank takes is very high - almost $80 [I had processing cost of $50 + tk 2000 in Dutch Bangla Bank]. It was heart-breaking as my check was of of $140 that time and after conversion I was left only with about $60! But later I was a bit relieved to learn that the charge of this $80 is the same for any amount of conversion of this type [no matter if it's $140 or $10,000].

6. What if you don't receive PIN or check: In case you don't receive PIN or check in time [after waiting for at most 6 weeks], you should request Google to re-issue the PIN/check. There is no additional fee for re-issue requests.