Posts Tagged “google”
Every day, there are more than a billion searches for information on Google. Have you ever wondered what those searches are about—or whether what you’re searching for also happens to be on the minds of millions of others across the country? We’re introducing a new way to find out—a regular video series called the Google Beat that highlights some of the hottest searches on Google in the U.S.
Using data from Google Trends, Google Insights for Search and some additional tools, the Google Beat will give you a snapshot of some of the topics that prompted people to turn to the web over the past week. You’ve probably seen our previous deep dives into Google search trends, like our annual year-end Zeitgeist and posts here about search trends related to events like the World Cup, the Oscars® and beyond. Searches can be unexpected, and sometimes what’s popular one week could never have been predicted the week before (think of Falcon Heene, last October’s “balloon boy” or Steven Slater). We’re looking forward to seeing what our data will reveal.
Check out this week’s premier video below, and subscribe to the Google Beat YouTube channel to get regular updates. We hope you enjoy.
Posted by Emily Wood, Editor, Google Blog team
Tags: google
Possibly Related posts
No Comments »
Posted by Nassar Stoertz, Software Engineer
In the next day or so, you’ll start to see some changes to the event page in Google Calendar which should make scheduling events easier. We’ve made the style more consistent with other Google apps, put information that’s most commonly used at the top of the screen, simplified the layout, and added some functionality.
A new repeating event editor
The old interface for creating recurring events was clumsy and took up too much space on the screen. Now you’ll see only a summary of your recurring event on the main event page; if you want to edit it, you can use a window that opens when you select the “Repeats” checkbox.
A new tool to help you find a time for your event
You’ll notice a new tab on the event page that should make it easier to find a good time to schedule an event. When your friends or coworkers give you permission to see their calendars, you can click this tab to see a preview of their schedules and hover over their events to see what conflicts they might have. This should make scheduling a tad easier, especially for events with large numbers of guests. For Google Apps users, the new schedule preview can also show data from other calendar services using our Google Calendar Connectors API.
Changes under the hood
As browsers and other technologies both within and outside of Google have evolved, we’ve found it necessary to occasionally make structural code changes in order to keep up. These visible changes are only the surface; underneath we’ve added a new model for how we represent calendar events in the browser and a new mechanism for how we make sure those events get properly saved. We’ve paid special attention to performance, consistency, and extensibility. In the short term, you’ll hopefully notice that the event page opens slightly faster than it did before.
Tags: google
Possibly Related posts
No Comments »
Here is how to get an RPM-based Linux distro (example Fedora) to work with the recently released Google talk / video drivers:
-
Acquire the driver package at http://www.google.com/chat/video by clicking the download link. This should download a file named “google-talkplugin_current_i386.deb”.
-
Put the .deb file in a temporary empty directory, by itself.
-
Open a command shell and navigate to that directory.
-
Type the following commands (don’t type the ‘$’ at the left):
$ ar vx google-talkplugin_current_i386.deb
$ sudo tar xvzf data.tar.gz -C /
-
Step (4) installs the drivers, but there is one problem at present — the Google voice driver needs to have access to particular versions of libraries named “libcrypto” and “libssl”. This is solved by creating symlinks to suitable versions.
-
Navigate to /usr/lib
-
Type the following commands (Fedora 13) with root authority:
$ ln -s ../../lib/libcrypto.so.1.0.0a libcrypto.so.0.9.8
$ ln -s libssl.so.1.0.0a libssl.so.0.9.8
(non-Fedora distributions, and other versions of Fedora, may have different locations and version numbers for these libraries, but the same basic method should work.)
-
Navigate to /opt/google/talkplugin
-
Type the following command:
$ ./GoogleTalkPlugin
The plugin should respond with:
./GoogleTalkPlugin: /usr/lib/libssl.so.0.9.8: no version information available (required by ./GoogleTalkPlugin) ./GoogleTalkPlugin: /usr/lib/libcrypto.so.0.9.8: no version information available (required by ./GoogleTalkPlugin)
But don’t despair — these are warnings, not errors, and the plugin should work.
On some systems, Firefox will now recognize and run the Google Talk plugin. On other systems and for an unknown reason, only the Google Chrome browser will work.
HTH
submitted by lutusp
[link] [1 comment]
Tags: firefox, google, linux
Possibly Related posts
No Comments »
When we first introduced our real-time search features last December, we focused on bringing relevance to the freshest information on the web. Our goal was to provide real-time content from a comprehensive set of sources, integrated right into your usual search results. Today we’re making our most significant enhancements to date, giving real-time information its own home and more powerful tools to help you find what you need. Now you can access Google Realtime Search at its own address, www.google.com/realtime (the page is rolling out now and should be available soon. Use this link if you want to try out the new features right away).
On the new homepage you’ll find some great tools to help you refine and understand your results. First, you can use geographic refinements to find updates and news near you, or in a region you specify. So if you’re traveling to Los Angeles this summer, you can check out tweets from Angelenos to get ideas for activities happening right where you are.
In addition, we’ve added a conversations view, making it easy to follow a discussion on the real-time web. Often a single tweet sparks a larger conversation of re-tweets and other replies, but to put it together you have to click through a bunch of links and figure it out yourself. With the new “full conversation” feature, you can browse the entire conversation in a single glance. We organize the tweets from oldest to newest and indent so you quickly see how the conversation developed.
Finally, we’ve also added updates content to Google Alerts, making it easy to stay informed about a topic of your choosing. Now you can create an alert specifically for “updates” to get an email the moment your topic appears on Twitter or other short-form services. Or, if you want to manage your email volume, you can set alerts to email you once per day or week.
Check out our demo video of the new features and quick tips on how to use them:
You can access Realtime Search by typing www.google.com/realtime directly into your browser, or clicking the “Updates” link in the left-hand panel of your search results. Set up your Google Alerts at www.google.com/alerts. Realtime Search and updates in Google Alerts are available globally in 40 languages, and the geographic refinements and conversations views are available in English, Japanese, Russian and Spanish. The features are rolling out now, but you can use this link to see them right away.
Posted by Dylan Casey, Product Manager
Tags: google, ideas, travel, twitter
Possibly Related posts
No Comments »
Raise your hand if any of this sounds familiar to you:
- You just set up your tracking code and you’re wondering if it’s correct–and you want to know right now.
- You have decided to migrate your tracking to the new asynchronous syntax–but you want to know if your syntax has any errors.
- You finally decided to customize the tracking code for cross-domain tracking–but you’re worried that you might break your tracking.
- You want to make sure that your campaign is set up to the correct goal.
Enter: The Google Analytics Tracking Code Debugger and a new debug version of our JavaScript code.
The Google Analytics team has launched a debugging version of the Analytics Tracking code called ga_debug.js to verify your tracking code setup. To make it even simpler, we also created a Chrome extension which uses the ga_debug.js script, which allows you to use the new ga_debug.js without re-tagagging any of your content. You can also use this extension to verify what information is sent to Analytics with each page.
How does it work? First, the ga_debug.js script provides a testing version of the tracking code which will print common syntax errors and tracking analysis messages to the browser’s JavaScript console. Secondly, the Chrome extension which automatically enables your page to use the debug version of the JavaScript without any need for you to retag or recode your pages.
How do you use it? The most simple thing to do is to download the Tracking Code Debugger extension for your Chrome browser. Next, turn on the extension by clicking on the icon to the right of the address bar on Chrome.
 Finally, visit a page that contains the tracking code you want to test and open up the Chrome JavaScript console to see the messages (detailed instructions). That’s it!
If you want to go use ga_debug.js without the Chrome extension, read all about how to do this in our newly revised Troubleshooting Guide on Google Code. You can use the script on your testing environment to verify extensive tracking code changes. Make sure, however, that you don’t use this version of the tracking code on your production website–the script is meant for debugging and analysis, not speed, so you should always use this as a testing mechanism only. If you want to learn more about the kinds of errors this script can help you find, see Common Tracking Code Errors/Typos in our Troubleshooting Guide. While the ga_debug.js script doesn’t catch all possible errors yet, we think it’s off to a great start and will get even better over time.
Happy testing!
Brian Kuhn on behalf of the Analytics Team
Tags: analytics, google
Possibly Related posts
No Comments »
|
Entries (RSS)