Création des Logiciels de gestion d'Entreprise, Création et référencement des sites web, Réseaux et Maintenance, Conception
Seo Master present to you: Google I/O attendees and speakers this year had the opportunity to participate in some fascinating and important conversations around the social web. The Developer Sandbox featured 16 companies on hand to talk about their social efforts, including Atlassian, eBay, IBM, LinkedIn, MySpace, Ning, Plaxo, Playfish, Yahoo!, and Voxeo.
In addition, nine sessions on social topics took place during the 2-day conference -- dealing with everything from real-time streams to OpenSocial in the enterprise. Of particular emphasis were open standards such as ActivityStreams, PubSubHubbub, OAuth, Salmon, and Webfinger that are fast becoming the foundational technologies for a more open and social web. The Google Buzz API was announced and covered in detail. And, of course, a deep look was taken at the future of the social web.
This is a big year for the social web, and we hope that the videos and slides from each session will expand your knowledge of and engagement with these exciting ideas and technologies:
You can also find all the Social Web I/O 2010 session videos on this YouTube playlist.
We had a great time at Google I/O this year and look forward to a long and fruitful discussion of everything social as we continue to work hard at making the the web more social, and the social web more open. Stay tuned to our progress on the Google Social Web Blog
2013, By: Seo Master
In addition, nine sessions on social topics took place during the 2-day conference -- dealing with everything from real-time streams to OpenSocial in the enterprise. Of particular emphasis were open standards such as ActivityStreams, PubSubHubbub, OAuth, Salmon, and Webfinger that are fast becoming the foundational technologies for a more open and social web. The Google Buzz API was announced and covered in detail. And, of course, a deep look was taken at the future of the social web.
This is a big year for the social web, and we hope that the videos and slides from each session will expand your knowledge of and engagement with these exciting ideas and technologies:
- Fireside chat with the Social Web team - Rockstars of the Social Web team at Google gather to talk with attendees about a truly open and social web.
- What's the hubbub about Google Buzz APIs? - Chris Chabot introduces the Google Buzz API and provides a deep dive on the open standards it uses such as ActivityStreams, PubSubHubbub, OAuth, Salmon, and WebFinger, and demonstrates how to build your own apps on top of the API.
- Surf the stream: Google Buzz, location, and social gaming - Bob Aman and Timothy Jordan continue the Google Buzz API party with Buzz Bingo, a social game built on App Engine and Google Buzz.
- iGoogle developer portal and tools - The iGoogle Gadget Dashboard and the OpenSocial Development Environment are introduced by Shih-chia Cheng and Albert Cheng to help you build and maintain better OpenSocial gadgets for iGoogle.
- Make your application real-time with PubSubHubbub - Atom and RSS feeds are even more valuable when they’re pushed to subscribers in real-time. In this session, Brett Slatkin (Google) and Julien Genestoux (Superfeedr) show you how to implement PubSubHubbub for better stream publishing and consumption.
- The open & social web - Chris Messina uses a cartoon narrative to tell the epic story of Jack and Kate, explaining how immigration, staying in touch, and sharing rich media relate to emerging technologies like OpenID, WebFinger, and publishing technologies like PubSubHubbub, ActivityStreams, and Salmon.
- Bridging the islands: Building fluid social experiences across websites - Once you’ve seen Chris Messina’s talk on the open & social web, you’re bound to ask how you connect your site to the rest of the Social Web to increase traffic, engagement, and relevance. John Panzer and Joseph Smarr give you the answer: by adopting the awesome open technologies described in this talk!
- Where is the social web going next? - Kara Swisher moderates a panel of leading experts from LinkedIn, Yahoo, Google, Microsoft, Twitter, and MySpace debating issues like privacy and providing their best guesses at the direction of the foundational technologies of the social web.
- Best practices for implementing OpenSocial in the Enterprise - Experts in the deployment of OpenSocial in the enterprise gather to talk implementation and best practices as well as review existing challenges.
You can also find all the Social Web I/O 2010 session videos on this YouTube playlist.
We had a great time at Google I/O this year and look forward to a long and fruitful discussion of everything social as we continue to work hard at making the the web more social, and the social web more open. Stay tuned to our progress on the Google Social Web Blog
2013, By: Seo Master
Seo Master present to you: The Google Client Team had an exciting and inspiring two days last week at Google I/O. We had the opportunity to talk to developers and have insightful conversations on what we're doing in the realm of HTML 5, Chrome, V8, Native Client, and 3D graphics on the web.
Today we're excited to reflect on these conversations at I/O, and kick off a series of videos and presentations from Google I/O. Starting with the Client track today, session videos and presentations from I/O will be posted online over the course of the next seven days and free to the world, on the Google I/O website.
Chrome: Extensions, Internals, V8 and more
Aaron Boodman gave a great talk on creating extensions for Chrome, and built several extensions live during his talk. I think this reflects our commitment to make it easy to build extensions, and I hope that developers -- not only those in the room, but those around the world who watch the recorded video of Aaron's talk -- will be inspired to create great extensions.
Darin Fisher delved into Chrome internals, managing to cover large swaths of Chrome code, philosophy, and lore without breaking a sweat. Darin's talk is a great way for developers to see that Chrome is more than just a fast browser with a slick UI -- we believe that developers at I/O came away realizing that there is a lot going on behind the scenes that sets Chrome apart.
Mads Ager talked about V8, walking attendees through the reason Google decided to build a new JavaScript engine, how some of the internals of V8 work including hidden classes, inline caching and garbage collection, and recent improvements made to further speed up JavaScript execution in V8. We were glad to present a thought-provoking session for developers, as attendees left the session with impressed and contemplative looks on their faces.
HTML5, Native Client, O3D and moving the web forward
Matt Papakipos, in addition to making an appearance in Wednesday's keynote, gave a great talk on where Chrome is, with respect to HTML5 and the open web platform. He explored what the platform means for developers, how they can use it, as well as the vision going forward. Matt delivered this talk to a packed room - attendees were spilling out to the aisles and doorways in our largest session room at the Moscone Convention Center in San Francisco. We're thrilled and humbled that developers are as excited as we are about the web platform and where we are taking it.
At the session on Native Client, Brad Chen got developers excited about the possibility of running native code as part of their web applications. Brad gave a comprehensive low-down on how Native Client works, and how it can be used to further strengthen the platform and move the web forward.
Vangelis Kokkevis and Gregg Tavares gave a talk on bringing 3D graphics to the web via O3D. Vangelis started the presentation with an overview of the O3D project and its goals and highlighted some its most significant features. Gregg then took over and demonstrated how, in a few simple steps, one can go from a blank HTML page to the beginnings of an entertaining mini-game with only a handfull of calls to the O3D API.
In addition, Henry Bridge led a panel with developers from Large Animal and Crazy Pixel, sharing insights about developing 3D graphics applications using O3D and getting developers excited about 3D on the web. You can also view sandbox video interviews with these two developers (Large Animal, Crazy Pixel) in the Developer Sandbox section, along with many other developers.
Browsers and standards development
To give developers more insight into how standards development and implementation in browsers work, we put together a panel with Jonas Sicking from Mozilla, Charles McCathieNevile from Opera, and myself, moderated by Mike Schroepfer (formerly of Mozilla now at Facebook). At this session, we talked more about the vision advanced by various browsers, and deliberated questions on where the browsers and the web are going.
Beyond the sessions, I/O provided the Client team the opportunity to interact with developers through Fireside Chats, where developers freely asked a broad range of questions. We also staffed Chrome Office Hours, where I/O attendees could stop by with their burning questions about the browser and chat with the team. We got developers excited about Chrome extensions, HTML5, <video>, O3D and more at the the Client developer sandbox pod.
All in all, we're thrilled to have spent two days with developers in conversation about Chrome, the web platform, and a shared future that we are all working so hard to create. We're excited to now bring these conversations to a larger community of developers with our I/O session videos and presentations. If you like, drop us comments through the Google Friend Connect gadget we have enabled on the session web pages - we'd be delighted to hear from you.
2013, By: Seo Master
Today we're excited to reflect on these conversations at I/O, and kick off a series of videos and presentations from Google I/O. Starting with the Client track today, session videos and presentations from I/O will be posted online over the course of the next seven days and free to the world, on the Google I/O website.
Chrome: Extensions, Internals, V8 and more
Aaron Boodman gave a great talk on creating extensions for Chrome, and built several extensions live during his talk. I think this reflects our commitment to make it easy to build extensions, and I hope that developers -- not only those in the room, but those around the world who watch the recorded video of Aaron's talk -- will be inspired to create great extensions.
Darin Fisher delved into Chrome internals, managing to cover large swaths of Chrome code, philosophy, and lore without breaking a sweat. Darin's talk is a great way for developers to see that Chrome is more than just a fast browser with a slick UI -- we believe that developers at I/O came away realizing that there is a lot going on behind the scenes that sets Chrome apart.
Mads Ager talked about V8, walking attendees through the reason Google decided to build a new JavaScript engine, how some of the internals of V8 work including hidden classes, inline caching and garbage collection, and recent improvements made to further speed up JavaScript execution in V8. We were glad to present a thought-provoking session for developers, as attendees left the session with impressed and contemplative looks on their faces.
HTML5, Native Client, O3D and moving the web forward
Matt Papakipos, in addition to making an appearance in Wednesday's keynote, gave a great talk on where Chrome is, with respect to HTML5 and the open web platform. He explored what the platform means for developers, how they can use it, as well as the vision going forward. Matt delivered this talk to a packed room - attendees were spilling out to the aisles and doorways in our largest session room at the Moscone Convention Center in San Francisco. We're thrilled and humbled that developers are as excited as we are about the web platform and where we are taking it.
At the session on Native Client, Brad Chen got developers excited about the possibility of running native code as part of their web applications. Brad gave a comprehensive low-down on how Native Client works, and how it can be used to further strengthen the platform and move the web forward.
Vangelis Kokkevis and Gregg Tavares gave a talk on bringing 3D graphics to the web via O3D. Vangelis started the presentation with an overview of the O3D project and its goals and highlighted some its most significant features. Gregg then took over and demonstrated how, in a few simple steps, one can go from a blank HTML page to the beginnings of an entertaining mini-game with only a handfull of calls to the O3D API.
In addition, Henry Bridge led a panel with developers from Large Animal and Crazy Pixel, sharing insights about developing 3D graphics applications using O3D and getting developers excited about 3D on the web. You can also view sandbox video interviews with these two developers (Large Animal, Crazy Pixel) in the Developer Sandbox section, along with many other developers.
Browsers and standards development
To give developers more insight into how standards development and implementation in browsers work, we put together a panel with Jonas Sicking from Mozilla, Charles McCathieNevile from Opera, and myself, moderated by Mike Schroepfer (formerly of Mozilla now at Facebook). At this session, we talked more about the vision advanced by various browsers, and deliberated questions on where the browsers and the web are going.
Beyond the sessions, I/O provided the Client team the opportunity to interact with developers through Fireside Chats, where developers freely asked a broad range of questions. We also staffed Chrome Office Hours, where I/O attendees could stop by with their burning questions about the browser and chat with the team. We got developers excited about Chrome extensions, HTML5, <video>, O3D and more at the the Client developer sandbox pod.
All in all, we're thrilled to have spent two days with developers in conversation about Chrome, the web platform, and a shared future that we are all working so hard to create. We're excited to now bring these conversations to a larger community of developers with our I/O session videos and presentations. If you like, drop us comments through the Google Friend Connect gadget we have enabled on the session web pages - we'd be delighted to hear from you.
2013, By: Seo Master
salam every one, this is a topic from google web master centrale blog: Webmaster Level: All
In this final installation in our URL removal series, let's talk about following up on your removal requests, as well as when not to use Google's URL removal tool. If you haven't already, I recommend reading the previous posts in this series:
Part I: Removing URLs & directories
Part II: Removing & updating cached content
Part III: Removing content you don't own
Companion post: Managing what information is available about you online
Understanding the status of your requests
Once you've submitted a removal request, it will appear in your list of requests. You can check the status of your requests at any time to see whether the content has been removed, or whether the request is still or pending or was denied.
If a request was denied, you should see a "Learn more" link next to it explaining why that particular request was denied. Since different types of removals have different requirements, the reason why a particular request was denied can vary. The "Learn more" link should help you figure out what you need to change in order to make your request successful. For example, you may need to change the URL in question so that it meets the requirements for the type of removal you requested; or, if you can't do that, you may need to request a different type of removal (one whose requirements your URL currently meets).
If a request has been marked "Removed" but you still see that content in search results, check the following:
this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com
In this final installation in our URL removal series, let's talk about following up on your removal requests, as well as when not to use Google's URL removal tool. If you haven't already, I recommend reading the previous posts in this series:
Part I: Removing URLs & directories
Part II: Removing & updating cached content
Part III: Removing content you don't own
Companion post: Managing what information is available about you online
Understanding the status of your requests
Once you've submitted a removal request, it will appear in your list of requests. You can check the status of your requests at any time to see whether the content has been removed, or whether the request is still or pending or was denied.
If a request was denied, you should see a "Learn more" link next to it explaining why that particular request was denied. Since different types of removals have different requirements, the reason why a particular request was denied can vary. The "Learn more" link should help you figure out what you need to change in order to make your request successful. For example, you may need to change the URL in question so that it meets the requirements for the type of removal you requested; or, if you can't do that, you may need to request a different type of removal (one whose requirements your URL currently meets).
If a request has been marked "Removed" but you still see that content in search results, check the following:
- Is the URL that's appearing in search results the exact same URL that you submitted for removal? It's fairly common for the same, or similar, content to appear on multiple URLs on a site. You may have successfully removed one URL, but still see others containing that same content.
Solution: Request removal of the other URL(s) in question. See this article for help. - Keep in mind that URLs are case sensitive, so requesting removal of http://www.example.com/embarrassingstuff.html is not the same as requesting removal of http://www.example.com/EmbarrassingStuff.html
Solution: Request removal of the exact URL(s) that appear in search results, including the same capitalization. See this article for help. - When a request is marked "Removed," that can mean different things depending on what type of request you submitted. If you requested removal of an entire URL, then "Removed" should mean that that entire URL no longer appears in our search results. If you requested removal of the cached copy of a URL, "Removed" means that the cached copy has been removed and will no longer appear in search results; but the URL itself may still appear.
Solution: Double-check what type of removal you requested by looking at the "Removal Type" column. If you requested a cache removal but you want the entire URL gone, make sure the URL meets the requirements for complete removal and then file a new request for complete removal of the URL.
- To clean up cruft, like old pages that 404.
The tool is intended for URLs that urgently need to be removed, such as confidential data that was accidentally exposed. If you recently made changes to your site and just have some outdated URLs in the index, Google's crawlers will see this as we recrawl your URLs, and those pages will naturally drop out of our search results over time. There's no need to request an urgent removal through this tool. - To remove crawl errors from your Webmaster Tools account.
The removal tool removes URLs from Google's search results, not from your Webmaster Tools account. There's currently no way for you to manually remove URLs from this report; they will drop out naturally over time as we stop crawling URLs that repeatedly 404. - To "start from scratch" with your site.
If you're worried that your site may have a penalty, or you want to "start from scratch" after purchasing a domain from someone else, we don't recommend trying to use the URL removal tool to remove your entire site and then "start over." Search engines gather a lot of information from other sites (such as who links to you, or what words they use to describe your site) and use this to help understand your site. Even if we could remove everything we currently know about your site, a lot of it would come back exactly the same once we'd recrawled all the other sites that help us understand your site and put it in context. If you're worried that your domain has some bad history, we recommend filing a reconsideration request letting us know what you're worried about and what has changed (such as that you've acquired the domain from someone else, or that you've changed certain aspects of your site). - To take your site "offline" after hacking.
If your site was hacked and you want to get rid of bad URLs that got indexed, you can use the URL removal tool to remove any new URLs that the hacker created, e.g., http://www.example.com/buy-cheap-cialis-skq3w598.html. But we don't recommend removing your entire site, or removing URLs that you'll eventually want indexed; instead, simply clean up the hacking and let us recrawl your site so that we can reindex the new, cleaned-up content as soon as possible. This article contains more details on how to deal with hacking. - To get the right "version" of your site indexed.
When a request to remove https://www.example.com/tattoo.html is accepted, http://www.example.com/tattoo.html is also removed. The same is true of the www and non-www versions of your URL or site. This is because the same content is often available at each of these URLs and we realize that most webmasters and searchers don't want these duplicates appearing in search results. In short, the URL removal tool should not be used as a canonicalization tool. It won't keep your favorite version, it'll remove all versions (http/https and www/non-www) of a URL.
this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com