With social media services allowing people to tag the locations of the photos they’ve uploaded, check-in to shops, bars and parks online, and have geolocation attached to their tweets, it’s clear that online technologies and the city are becoming increasingly integrated, with no signs of this stopping. This data is accessible and is already being utilised by a variety of innovative applications, further suggesting that data, technology and the built environment will soon be fully intertwined.
However, our planning system is progressing at a much slower pace, and some might say not at all. Potential developments are stuck on a nearby lamp post, and if you have any issues, you can write a letter or attend a meeting. The most active contributors are the ‘NIMBY’ (not in my backyard) and ‘BANANA’ (build absolutely nothing anywhere near anything) crowd, halting bad developments, but good ones too.
With a wealth of data suggesting the general public have a real interest in online interactions with the built environment, is it time that the planning system opened itself up to the world wide web and the vast amount of data being generated by social media interactions, encouraging engagement from the masses?
Does the user data already being generated from online interactions with the built environment have a value within the planning process, and if so, should it be promptly integrated when making planning considerations? Could this create a greater sense of community, forging connections between people and place, or are the general public genuinely not interested in city planning? Would it improve the overall quality of the design of buildings and public space or would we end up with an exaggerated built-by-committee situation?
When Google launched its Pac-Man logo on Friday, we immediately heard amused groans in our tweet-streams. “Well, so much for my morning,” said one. “Google’s Pac Man logo just ruined millions of dollars in productivity today, nationwide,” said another.
Here’s what we all saw on Friday:
Here are two of the tweets we saw in response:
Given our repository of hundreds of millions of man hours of second by second attention data, we figured there’s no one better than RescueTime to tell the world about the cost of Google Pac-Man on that fateful Friday. Here’s what we learned.
The first thing to understand is that Google does not result in a lot of active usage, in terms of time. Yes, we all use Google. But a Google search only requires a few seconds, and we’re all pretty well trained to click one of the first few links. Add to that the fact that many people use Google as a navigation tool (“Googling “IBM” instead of typing in “www.ibm.com”). Nonetheless, it might surprise you that our average Google user spends only 4 and a half activeminutes on Google search per day, spread over about 22 page views. That’s roughly 11 seconds of attention invested in each Google page view. It doesn’t sound like a lot, but next time you do a search, count to 11- it’s a long time.
This weekend, we took a hard look at Pac-Man D-Day and compared it with previous Fridays (before and After Google’s recent redesign) and found some noticeable differences. We took a random subset of our users (about 11,000 people spending about 3 million seconds on Google that day) The average user spent 36 seconds MORE on Google.com on Friday.. Thankfully, Google tossed out the logo with pretty low “perceived affordance” – they put an “insert coin” button next to the search button, but I imagine most users missed that. In fact, I’d wager that 75% of the people who saw the logo had no idea that you could actually play it. Which the world should be thankful for.
If we take Wolfram Alpha at its word, Google had about 504,703,000 unique visitors on May 23. If we assume that our userbase is representative, that means:
Google Pac-Man consumed 4,819,352 hours of time (beyond the 33.6m daily man hours of attention that Google Search gets in a given day)
$120,483,800 is the dollar tally, If the average Google user has a COST of $25/hr (note that cost is 1.3 – 2.0 X pay rate).
For that same cost, you could hire all 19,835 google employees, from Larry and Sergey down to their janitors, and get 6 weeks of their time. Imagine what you could build with that army of man power.
$298,803,988 is the dollar tally if all of the Pac-Man players had an approximate cost of the average Google employee.
I hope you’ve enjoyed our Pac-Man data journey as much as we have. Next up in our on our data-hacking list, we’ll be digging in to find the laziest and most productive countries and cities in the world. Where do you think yours ranks?
About the data:
RescueTime provides a time management tool to allow individuals and businesses to track their time and attention to see where their days go (and to help them get more productive!). We have hundreds of millions of man hours of second-by-second attention data from hundreds of thousands of users around the world, tracking both inside and outside the browser. The data for this report was compiled from 11,000 randomly selected Google users.
About our software:
If you want to see how productive you are vs the rest of our users, you should check out our product tour. We offer both individual and group plans (pricing starts at FREE).
Medya kontrol grubu Recma, geçtiğimiz son 3 yıl içerisinde rekabet edebilirlik ve iş kazanımları bakımından en başarılı bulduğu ajansları açıkladı.
C den A+'a kadar derecelendirilen medya ajanları, önce tek tek ülkeler bazında değerlendirilmeye tabi tutuldu. Ardından bölgesel bazda derecelendirilen ajanslar en son global olarak sıralandı. 26 ülkeden 297 medya ajansının dahil edildiği araştırmada RECMA 6 büyük grubu 2009, 2008, 2007 yılları için derecelendirdi.
Global derecelendirmede OMD birinci, Mediaedge:cia ikinci, Starcom MediaVest üçüncü sırada yer aldı.
Avrupa'nın en iyi 3 medya ajansı ise MPG (Havas medya ajansı), ZenithOptimedia ve OMD oldu.
Ajansların derecelendirmesi rekabet edebilirlik ve yeni iş kazanımlarına göre yapıldı.
Google Chrome contains many features that can be harnessed by webmasters to deliver a better end-user experience. Google Chrome comes with Gears built in, which allows webmasters to take advantage of APIs such as offline storage. In addition, Google Chrome allows your web application to look and feel like a "desktop" application, as users can launch Google Chrome in a mode with a minimalist UI, featuring nothing but a title bar.
Google Chrome also uses a brand new JavaScript engine (V8), which is much faster than existing JavaScript interpreters. This means you can create more complex and more intensive AJAX applications with fewer speed and processing constraints. Finally, Google Chrome is built on top of WebKit, so Google Chrome users will benefit from the CSS3 features being added to WebKit as those features are released.
2. Where can I find information about other browsers?
There are a number of other browsers to choose from. Find out about some of the more widely used browsers at the websites listed below:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.X.Y.Z Safari/525.13.
Google Chrome uses the WebKit rendering engine, which is shared by other browsers such as Apple's Safari. Web pages should look the same in Google Chrome as they will in these other WebKit-based browsers. You can look for webkit in user agent strings to target these browsers, rather than a specific browser name (such as Google Chrome or Safari).
Language encoding
4. Google Chrome isn't displaying characters correctly
To help browsers render your content correctly, you should always provide content and character encoding information at the top of your document's source. If you're using frames or iframes, specify the encoding at the top of the source of those frames, as well. Some browsers (including Google Chrome) won't recognize encoding declarations that appear deep in a document (such as after CSS or script in your document's head section).
Example of good encoding placement:
.......
Also make sure that your web server is not sending conflicting HTTP headers. Headers sent by the web server will override any charset declarations in your page.
5. Declaring encoding using JavaScript (document.write) doesn't work
Google Chrome doesn't read encoding information that's declared with document.write(). If you're using this method to declare encoding in iframes, for example, you may see garbled characters when the iframe is rendered. Instead of:
frame1.js
document.write("");
... other JavaScript code ...
...we recommend the following:
frame1.html
...
6. Google Chrome is displaying '%B1%C1%C3%E5' instead of two Chinese characters
Google Chrome percent-encodes query parameters within a URL. Make sure that your server-side scripts are properly decoding percent-encoded characters before processing the data.
ActiveX is only supported by Internet Explorer (and browsers built on top of Internet Explorer) on Windows. Google Chrome, Mozilla Firefox, Apple Safari, and others do not support ActiveX. Instead, these browsers make use of the Netscape Plugin Application Programming Interface (NPAPI).
8. My JavaScript isn't executing properly
There are a couple of ways to view JavaScript errors and work to debug them in Google Chrome:
JavaScript Console: click the Page menu icon and select Developer > JavaScript Console. From here, you'll be able to view errors in the JavaScript execution, and enter additional JavaScript commands to execute.
JavaScript Debugger: available as Page menu icon > Developer > Debug JavaScript, the debugger provides a command prompt from which you can set breakpoints, backtrace, and more. Type help at the debugger command line to get started.
Rendering and browser behaviour
9. My site renders differently in Google Chrome than in Internet Explorer
Google Chrome uses a different rendering engine than Internet Explorer, so may display web pages differently. Apple Safari uses the same rendering engine as Google Chrome (WebKit) and should display pages the same way.
If your site isn't rendering properly in any browser, make sure your HTML and CSS are valid by testing them at http://validator.w3.org/.
There are several tools to help you test your website in Google Chrome:
Web Inspector
Right-click on any component on a web page to launch the web inspector. You'll be able to see the elements and resources associated with the component on which you clicked, including a hierarchy view of the DOM and a JavaScript console.
Task Manager
Select the Page menu icon, then Developer > Task Manager (or press Shift+Esc). The task manager shows all running Google Chrome processes, and the resources that they're using (memory, CPU, and network).
JavaScript Debugger
Select the Page menu icon, then Developer > Debug JavaScript. This launches a JavaScript debugger that can be used to attach to existing processes.
11. Font specifications in an external style sheet do not take effect
Make sure that your external stylesheets are being served with the correct charset and content-type. They should be served as text/css ortext/css;charset=X.
It's better not to specify charset for a style sheet in the HTTP header; instead, add the declaration to the very beginning (no preceding characters, including spaces and line breaks) of your CSS stylesheet as follows:
@charset "xxx"
Neglecting to specify encoding information could prevent your stylesheet from being properly parsed.
12. My website's popups aren't appearing in Google Chrome
Google Chrome's default behavior is to minimize and then display only the title bar of pop-ups in the lower-right section of the browser window. Users can view a pop-up's content by dragging its title bar into a more visible position. This allows pop-ups to load, so as not to break the functionality of sites which depend on them. It also prevents undesired pop-ups from covering the page and distracting users.
13. My SSL-protected website is showing an exclamation mark in Google Chrome, instead of a lock
This indicates a problem with the use of SSL on the page. Clicking on the exclamation mark in Google Chrome will provide more details about the issue. Often, issues are the result of mixed content on your page - for example, your top level webpage is served over HTTPS and is protected via SSL, but you have also included elements on the page (such as images, script, or CSS) via HTTP. All content must be served over HTTPS in order for the lock to display.
14. The HTML5 database API isn't supported in Google Chrome
The Google Chrome team plans to support the HTML5 database API, as well as the other APIs that WebKit supports, including offline and workers, in a future release.
15. How can I customize the appearance and function of Google Chrome shortcuts that point to my page?
Google Chrome users can create shortcuts for any web page by selecting Create application shortcuts from the Page menu icon. By default, new shortcuts take the title and favicon of the page to which the shortcut is pointing.
You can specify the title, description, and URL of Google Chrome shortcuts that point to your page by inserting specific meta tags in your document's section.
To customize:
Tag
Example
The shortcut title
application-name
The description (used when more space is available, such as in the preferences panel)
description
The URL to open when the shortcut is clicked
application-url
The shortcut icon
For example:
These tags closely match those of the Gears Desktop API. Please refer to the Gears Desktop API documentation for more details.
16. How can my web page open a new tab in a separate process?
Google Chrome has a multi-process architecture, meaning tabs can run in separate processes from each other, and from the main browser process. New tabs spawned from a web page, however, are usually opened in the same process, so that the original page can access the new tab using JavaScript.
However, Google Chrome will look for hints to open new tabs in a separate process, if you are navigating the new tab to a different web site.
The easiest approach is to use a link to a different web site that targets a new window without passing on referrer information. Google Chrome recognizes this as a hint to keep the new page isolated from the original page, and it will load the new page in a separate process. For example:
If you want the new tab to open in a new process while still passing on referrer information, you can use the following steps in JavaScript:
Open the new tab with about:blank as its target.
Set the newly opened tab's opener variable to null, so that it can't access the original page.
Redirect from about:blank to a different web site than the original page.
For example:
var w = window.open();
w.opener = null;
w.document.location = "http://differentsite.com/index.html";
These hints only work for URLs that are on a different domain or protocol than the page spawning the pop-up. For example, if the page spawning the popup is on http://www.example.com/:
a different domain would be http://www.example.org or http://www.example2.com
a different protocol would be https://www.example.com
Search
17. Entering an intranet website address brings up a search results page, rather than the intranet site
When a user enters a single word into the address bar, Google Chrome performs a search for the term and returns results using the user's default search engine. At the same time, Google Chrome issues a HEAD request for http://term, to see if it's a valid website. If Google Chrome receives an HTTP/2xx response (such as HTTP/200 OK), the user will be asked if they want to visit the site instead. Clicking through to the site from the prompt will set the website as the default target for that term for future requests.
Google Chrome will also display the prompt if it receives:
an HTTP/401 or HTTP/407 response
an HTTP/3xx redirect that terminates in a page with any of the above responses
You should make sure that your web server properly responds to HEAD requests, and not just GET requests for a page.
For example, if a site exists at http://project.intranet.example.com, and a user within that corporate network enters project into the address bar:
Google Chrome will return search results for the term project
At the same time, Google Chrome will check if http://project is a valid website. If so,
A prompt will appear, asking if the user would like to visit http://project
Once the user clicks through to http://project, Google Chrome sets http://project as the target for all future instances of project in the address bar
Users can override the default (search) behavior by entering project/ or http://project, or by selecting the address bar entry that reads project/instead of Search for project.
18. How can I include my site's search in Google Chrome's search options?
By providing an OpenSearch description document (OSDD), you enable Google Chrome to include your site in the list of search engines in the browser. For more information about OpenSearch, please visit http://www.opensearch.org.
