Audi Q6 car to launch in India in January 2050 @ 55.00 Lakh
| Labels : Google, search | |||||||||
| 0 comments | |||||||||
| Labels : Google, search | |||||||||
| 0 comments | |||||||||
Replace [bucket] with your bucket name.
gsutil -h "Vary:Accept-Encoding" -h "Cache-Control:public,max-age=31536000" cp -a public-read font-webfont.eot gs://[bucket]/fonts/font-webfont.eot gsutil -h "Vary:Accept-Encoding" -h "Cache-Control:public,max-age=31536000" cp -a public-read font-webfont.woff gs://[bucket]/fonts/font-webfont.woff gsutil -h "Vary:Accept-Encoding" -h "Cache-Control:public,max-age=31536000" cp -a public-read font-webfont.ttf gs://[bucket]/fonts/font-webfont.ttf gsutil -h "Vary:Accept-Encoding" -h "Cache-Control:public,max-age=31536000" cp -a public-read font-webfont.svg gs://[bucket]/fonts/font-webfont.svg
Now your font is accessible at http://[bucket].commondatastorage.googleapis.com/fonts/font-webfont.eot or http://[bucket].commondatastorage.googleapis.com/fonts/font-webfont.ttf etc.
Apply the code to your CSS.
@font-face {
font-family: 'fontFamilyName';
src: url('http://[bucket].commondatastorage.googleapis.com/fonts/font-webfont.eot');
src: url('http://[bucket].commondatastorage.googleapis.com/fonts/font-webfont.eot?#iefix') format('embedded-opentype'),
url('http://[bucket].commondatastorage.googleapis.com/fonts/font-webfont.woff') format('woff'),
url('http://[bucket].commondatastorage.googleapis.com/fonts/font-webfont.ttf') format('truetype'),
url('http://[bucket].commondatastorage.googleapis.com/fonts/font-webfont.svg#aller_displayregular') format('svg');
font-weight: normal;
font-style: normal;
}Unfortunately the last step is not enough to display the web-font on your website since the fonts need to be on the same domain as the website.
In order to allow web-fonts to be hosted elsewhere, the location of the web-fonts must have a Access-Control-Allow-Origin header sent.
For Google Storage, we do this :
<?xml version="1.0" encoding="UTF-8"?>
<CorsConfig>
<Cors>
<Origins>
<Origin>http://mydomain.com</Origin>
</Origins>
<Methods>
<Method>GET</Method>
<Method>HEAD</Method>
</Methods>
<ResponseHeaders>
<ResponseHeader>x-goog-meta-foo1</ResponseHeader>
</ResponseHeaders>
<MaxAgeSec>1800</MaxAgeSec>
</Cors>
</CorsConfig>Save this as font.xml.
Hmmm ... Google says :
gsutil setcors <cors-xml-file> uri
But using gsutil, we can set CORS to an entire bucket only and not to an object.
gsutil setcors font.xml gs://[bucket]
not uri as mentioned
Similarily, for getcors :
gsutil getcors gs://[bucket]and not
gsutil getcors gs://cats/mycats.png
| Labels : Google, storage | |||||||||
| 1 comments | |||||||||
My friend Sudhir bought this from the local store.

Read : Google Agarbatti. (Agarbatti = Incense)
Update : Thanks to Sumit Ashok Kesarkar for the clarification. its Gugal which means Guggul == made from the sap of the plant "Commiphora mukul"
| Labels : Google | |||||||||
| 0 comments | |||||||||
There is one major limitation when sending out legit mass emails via SMTP ("compose") - a daily cap on the number of emails allowed to be sent from a mailbox. This applies to most e-mail service providers.
Google Apps Standard, the free edition, allows a maximum of 500 outgoing mails per day for each user id.
Even the Primier edition which costs $50 per user a year limits outgoing mails at 2000 per day for every email id.
There are two cost-effective ways to send out newsletter emails via Google's services - Google Friend Connect (GFC) and Google App Engine (GAE).
A lot of people are not unaware of the fact that you can actually send out newsletters for free to your subscribers via Google Friend Connect (GFC).
The catch is that the users have to be susbcribed exclusively via Google's Subscribe button without which there is no way for the newsletter to reach the user.
This is really a tough catch as you got to have it's subscribe button right from launch date.
Its a major turnoff, especially when a website collects registration infomation via a form and sends the data to a database, after which emails are sent separately.
Most email marketing systems like aweber, mailchimp, emailbrain, constantcontact, madmimi etc have the option to add subscribers manually externally.
And with GFC, you would not be able to retrieve the subscribed users' email ids via the control panel - export gives only names, ids, open id urls and thumbnail images.
So, at a later point in time, if you decide to switch to another email marketing system, you would need to send one last email asking them to re-subscribe to a new system.
Another bad news is that the subscriber's email address must be an open id ! (google a/c, yahoo a/c, twitter, AIM, netlog or any other openid)
Looks like all bad news, but if you think from the users' perspective, this is a good deal.
Its secure since there is no way for emails to be leaked accidentally.
Its safe because there is no room for errors in accidentally sending out mails to users who have unsubscribed.
Regarding the sender / from email address - It would be the same as the google account username. So if you don't want it sent from myusername@gmail.com, then create a google account under your app id. (This dual account chaos would be resolved soon : Google Apps Accounts Will Also Be Personal Google Accounts)
GFC is straigtforward, only bit of major work required is getting the audience to hit the google subscribe button.
If you are not convinced with GFC then check out GAE - Google App Engine.
It has a daily free quota of sending emails to 2000 recipients. Link
After that, its billed at $0.0001 per recipient - thats just $1 for sending to an additional 10,000 recipients which can execute in about 2 minutes ! Link
But you've got to code to take advantage of GAE and your website should most probably be powered by GAE as well.

Then there is always google's mailing list at google groups.

But this cannot really be act a newsletter system.
If you want to submit ideas / suggestions to the Google team for its products, you can submit or vote at Google Product Ideas which is open to the public.
| Labels : email, Google | |||||||||
| 0 comments | |||||||||
When Gmail was first launched in 2004, its most attractive features were fast AJAX interface and POP+SMTP ! Though Microsoft Email clients like Outlook & Express managed to emulate POP & SMTP for Hotmail accounts, POP+SMTP was not really available. But above all, it was Gmail's initial 1GB and growing storage capacity what really lured people to using it. By 2007, with space of almost 3GB and 10GB for the paid versions, Google has recently increased their capacity to 4GB (targetted to 6GB by Jan '08) and 25GB for paid versions.
And now for the most anticipated feature of all - IMAP. Thats right. Google has just started rolling out IMAP for gmail accounts. This may not come as a very big excitement for most users, but it definitely does for developers who can now access gmail accounts directly via the IMAP protocol. The only other free service that was providing this so far, was AOL.
There may have been a lack of new services by Google this year, but if definitely seems to be improving their existing ones dramatically. After all, it reached the $600 a share mark a couple of weeks back and is close to $670 as of now.
| Labels : email, Google | |||||||||
| 0 comments | |||||||||
| Indian City, State or District | Occurrence | % |
|---|---|---|
| Ranchi | 8739 | 25.2 |
| Hardwar | 3224 | 9.3 |
| GOA | 2643 | 7.6 |
| Diu | 2527 | 7.3 |
| Rewa | 2204 | 6.4 |
| Nadia | 2203 | 6.4 |
| Agra | 2121 | 6.1 |
| Puri | 1859 | 5.4 |
| Kota | 1306 | 3.8 |
| Punch | 1004 | 2.9 |
| Salem | 892 | 2.6 |
| Bid | 817 | 2.4 |
| Chandel | 716 | 2.1 |
| Banda | 681 | 2 |
| Guna | 441 | 1.3 |
| Thane | 378 | 1.1 |
| Basti | 334 | 1 |
| Latur | 323 | 0.9 |
| Leh | 292 | 0.8 |
| Alwar | 237 | 0.7 |
| Etah | 230 | 0.7 |
| DELHI | 196 | 0.6 |
| Pali | 174 | 0.5 |
| Tonk | 95 | 0.3 |
| Bangalore | 87 | 0.3 |
| Erode | 75 | 0.2 |
| Theni | 63 | 0.2 |
| Mandi | 57 | 0.2 |
| Morena | 57 | 0.2 |
| Hyderabad | 54 | 0.2 |
| Mumbai | 52 | 0.2 |
| Chennai | 47 | 0.1 |
| New Delhi | 44 | 0.1 |
| Solan | 42 | 0.1 |
| Baster | 36 | 0.1 |
| PUNJAB | 35 | 0.1 |
| Dhar | 33 | 0.1 |
| Pune | 30 | 0.1 |
| Mahe | 21 | 0.1 |
| Anand | 19 | 0.1 |
| Godda | 17 | 0 |
| KERALA | 15 | 0 |
| Krishna | 15 | 0 |
| Harda | 13 | 0 |
| Jaipur | 12 | 0 |
| Ambala | 10 | 0 |
| Betul | 10 | 0 |
| Daman | 9 | 0 |
| Saran | 9 | 0 |
| Almora | 8 | 0 |
| Mansa | 8 | 0 |
| Gaya | 7 | 0 |
| GUJARAT | 7 | 0 |
| Hassan | 7 | 0 |
| Baran | 6 | 0 |
| Gonda | 6 | 0 |
| Gurgaon | 6 | 0 |
| ORISSA | 6 | 0 |
| Surat | 6 | 0 |
| ASSAM | 5 | 0 |
| WEST BENGAL | 5 | 0 |
| ANDHRA PRADESH | 4 | 0 |
| KARNATAKA | 4 | 0 |
| Kolkata | 4 | 0 |
| Satara | 4 | 0 |
| Durg | 3 | 0 |
| MANIPUR | 3 | 0 |
| Moga | 3 | 0 |
| Sagar | 3 | 0 |
| Yanam | 3 | 0 |
| Cachar | 2 | 0 |
| Chandigarh | 2 | 0 |
| Chatra | 2 | 0 |
| Indore | 2 | 0 |
| Lucknow | 2 | 0 |
| MAHARASHTRA | 2 | 0 |
| Mysore | 2 | 0 |
| Patan | 2 | 0 |
| TAMIL NADU | 2 | 0 |
| Umaria | 2 | 0 |
| UTTAR PRADESH | 2 | 0 |
| Washim | 2 | 0 |
| Aligarh | 1 | 0 |
| Allahabad | 1 | 0 |
| Banka | 1 | 0 |
| Bhopal | 1 | 0 |
| Chamba | 1 | 0 |
| Coimbatore | 1 | 0 |
| Ghaziabad | 1 | 0 |
| Hamirpur | 1 | 0 |
| Haora | 1 | 0 |
| HARYANA | 1 | 0 |
| Haveri | 1 | 0 |
| Jalandhar | 1 | 0 |
| Jamnagar | 1 | 0 |
| Jind | 1 | 0 |
| Kancheepuram | 1 | 0 |
| Kanker | 1 | 0 |
| Kargil | 1 | 0 |
| Kurukshetra | 1 | 0 |
| Lalitpur | 1 | 0 |
| Madurai | 1 | 0 |
| Maldah | 1 | 0 |
| Medak | 1 | 0 |
| Nagpur | 1 | 0 |
| Panna | 1 | 0 |
| Patna | 1 | 0 |
| RAJASTHAN | 1 | 0 |
| Sikar | 1 | 0 |
| SIKKIM | 1 | 0 |
| South Goa | 1 | 0 |
| Vellore | 1 | 0 |
| Visakhapatnam | 1 | 0 |
| Warangal | 1 | 0 |
| Labels : Google | |||||||||
| 1 comments | |||||||||
| Labels : borat, Google | |||||||||
| 0 comments | |||||||||
| Labels : Business, Google, technology | |||||||||
| 0 comments | |||||||||
Come on Google, I'm a big fan of G, but you should atleast get the billionaires names mapped correctly !
| Labels : Billionaire, Google | |||||||||
| 1 comments | |||||||||