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:
by Aygul Zagidullina and
Misha Matiyenko-Kupriyanov, with Domenica Liberti, Google I/O Team
Google I/O 2012 is fast approaching, and to help energize you for three packed days of demos, announcements and developer fun, we chatted with a few attendees to see what excites them about this year’s agenda, and to get some tips on how to make the most of the event.
Today's conversation is with two passionate GDG leaders, Aygul and Misha, who spent part of their honeymoon at Google I/O last year! Aygul Zagidullina is a research scientist at the University of Stuttgart and Misha Matiyenko-Kupriyanov works as a web developer at Deutsche Online Medien GmbH. Their life together is documented and searchable on Google. They share their thoughts and web gems on Google+, plan trips across Europe and the US with Google Maps, check in on each other with Google Latitude, and live in the clouds with their Android devices. We would like to share with you their love story and how they are planning on making the most of 3 days of Google I/O 2012.
How did the two of you meet?
Our story began with a casual conversation in LiveJournal that we quickly outgrew and moved to Google Talk to keep up with each other by relying heavily on daily chat communication. We very quickly discovered how many similar interests and thoughts on a wide variety of topics we have. Within a month, we decided to have our first trip to Düsseldorf for Japan Day and started our shared Google Calendar and collaborative Google Docs to plan our activities and collect ideas of what we would like to do together.
In 2010 we both attended German GDG Battle organized by GDG Stuttgart . The team we both were part of got Nexus One smartphones as the first prize. At this event we fell in love with the GDG concept and became later on a part of the organizing team. It has been two exciting years now since we've joined the GDG Stuttgart's organizing team, two years full of planning and execution of public events such as Android DevCamp Stuttgart, tech talks, hackathons and many other local events on Google technologies as well as communication with local developers online via discussion boards and Google+.
Years later we are incredibly happy together, and are excited about our future. Today we can't even imagine how our life would be without technology.
Why did you choose Google I/O for your honeymoon last year?
We wanted our wedding and honeymoon to be perfect in all senses, memorable, breathtaking, and pleasantly useful! Getting married in Las Vegas and spending the honeymoon at our very first Google I/O - we could not have imagined celebrating the start of our new life together any other way. Today, one year later we are looking back and can't be happier about how right this decision was.
What’s the best memory you will always keep with you about being at Google I/O as newlyweds?
Two of our most memorable moments were definitely the keynotes on the first and second days. You had to see us, happy to tears, literally screaming with all other people in the room after each groundbreaking announcement. The feeling that technology revolution happens right here, right now is nothing but priceless!
Another amazing experience we will always keep in our hearts was meeting our international GDG community. We were extremely happy to finally put faces on the name of many GDG managers we were working with to build our community. Google gave us plenty of opportunities for communication, experience exchange and fruitful networking with members of the GDG community such as the Advocates Summit (with Vic Gundotra and Developer Relations team), GDG lounge, and a visit to the Googleplex (as a part of self-organized Silicon Valley Geek Tour).
Why is attending Google I/O important to what you do?
Aygul: I am primarily interested in fostering European (both West and East) developer communities. Being an enthusiastic co-organizer of two Google Developer Groups (GDGs) in Stuttgart, Germany and Ufa, Russia, I love engaging with local developers to help them be successful building products using Google technologies. Besides, I'm also a happy and proud Google Top Contributor (TC) at the Google+, Gmail, Google Web Search and several other product forums (English, German, and Russian) and am doing my best to help users on a daily basis to learn how to use Google products better and troubleshoot their issues. With such a broad network, many of whom cannot be at I/O in person, I am excited to take what I learn and share it with my fellow GDGers.
Misha: As a passionate web developer, I am mostly interested in web-related technologies like HTML5, Google Chrome as development tool, Google Chrome extensions, Google App Engine and the knowhow of Google APIs. Also, my skills in developing Android applications is something I would definitely like to boost. I am sure these new technologies will bring new boost to my mojo and attending I/O will inspire me to start new projects like the ones I've worked on recently, the Google Developer Day Android application, the FontVending Android application and the Helper for Google+ Chrome extension.
Tell us your plans for Google I/O this year.
Aygul: The day before we are planning to participate in the GDG Organizers Summit to meet GDG managers from around the world and discuss all together how we can take our community to the next level.
With all the sessions that are going in parallel, it's pretty challenging to choose only one session to attend at a time. I've said that I'm going to watch every Google I/O talk later at home, but some of them are definitely on my must-attend-and-hear-it-live list. Getting More from the Google+ Platform, Android Design for Success, The Web Can Do That!?, and From Weekend Hack to Funded Startup - How to Build Your Team and Raise Money are among them.
Besides Sessions and Code Labs, I'm really excited to see so many excellent products will be presented at Sandbox this year. As a true productivity junkie, I can’t wait to talk to creators of GQueues in person.
Misha: Every year Google presents at Google I/O some new pieces of technology that may form the future landscape of the web. I will make sure to learn about all the announcements on Google+ API, Google App Engine, Dart, Chrome tooling, Google Cloud Printing, and Google Drive API.
This year I would like to participate in as many Google I/O sessions as possible. Some of them are Dart - A Modern Web Language, Building Mobile App Engine Backends for Android, iOS and the Web, Beyond Paper: Google Cloud Print and the Future of Printing, and Powering your Application's Data using Google Cloud Storage. I chose these sessions because these are new Google technologies and I would like to incorporate them into my projects.
Not coming to Google I/O 2012 in person? Not a problem. Watch the keynote and dozens of other sessions streamed live at developers.google.com/io.
Aygul Zagidullina is a research scientist at the University of Stuttgart. Misha Matiyenko-Kupriyanov is a web developer at Deutsche Online Medien GmbH.
Edited and posted by Domenica Liberti and Scott Knaster, Google I/O Team.
2013, By: Seo Master
 |
| Domenica |
 |
| Misha |
 |
| Aygul |
Misha Matiyenko-Kupriyanov, with Domenica Liberti, Google I/O Team
Google I/O 2012 is fast approaching, and to help energize you for three packed days of demos, announcements and developer fun, we chatted with a few attendees to see what excites them about this year’s agenda, and to get some tips on how to make the most of the event.
Today's conversation is with two passionate GDG leaders, Aygul and Misha, who spent part of their honeymoon at Google I/O last year! Aygul Zagidullina is a research scientist at the University of Stuttgart and Misha Matiyenko-Kupriyanov works as a web developer at Deutsche Online Medien GmbH. Their life together is documented and searchable on Google. They share their thoughts and web gems on Google+, plan trips across Europe and the US with Google Maps, check in on each other with Google Latitude, and live in the clouds with their Android devices. We would like to share with you their love story and how they are planning on making the most of 3 days of Google I/O 2012.
How did the two of you meet?
Our story began with a casual conversation in LiveJournal that we quickly outgrew and moved to Google Talk to keep up with each other by relying heavily on daily chat communication. We very quickly discovered how many similar interests and thoughts on a wide variety of topics we have. Within a month, we decided to have our first trip to Düsseldorf for Japan Day and started our shared Google Calendar and collaborative Google Docs to plan our activities and collect ideas of what we would like to do together.
In 2010 we both attended German GDG Battle organized by GDG Stuttgart . The team we both were part of got Nexus One smartphones as the first prize. At this event we fell in love with the GDG concept and became later on a part of the organizing team. It has been two exciting years now since we've joined the GDG Stuttgart's organizing team, two years full of planning and execution of public events such as Android DevCamp Stuttgart, tech talks, hackathons and many other local events on Google technologies as well as communication with local developers online via discussion boards and Google+.
Years later we are incredibly happy together, and are excited about our future. Today we can't even imagine how our life would be without technology.
Why did you choose Google I/O for your honeymoon last year?
We wanted our wedding and honeymoon to be perfect in all senses, memorable, breathtaking, and pleasantly useful! Getting married in Las Vegas and spending the honeymoon at our very first Google I/O - we could not have imagined celebrating the start of our new life together any other way. Today, one year later we are looking back and can't be happier about how right this decision was.
What’s the best memory you will always keep with you about being at Google I/O as newlyweds?
Two of our most memorable moments were definitely the keynotes on the first and second days. You had to see us, happy to tears, literally screaming with all other people in the room after each groundbreaking announcement. The feeling that technology revolution happens right here, right now is nothing but priceless!
Another amazing experience we will always keep in our hearts was meeting our international GDG community. We were extremely happy to finally put faces on the name of many GDG managers we were working with to build our community. Google gave us plenty of opportunities for communication, experience exchange and fruitful networking with members of the GDG community such as the Advocates Summit (with Vic Gundotra and Developer Relations team), GDG lounge, and a visit to the Googleplex (as a part of self-organized Silicon Valley Geek Tour).
Why is attending Google I/O important to what you do?
Aygul: I am primarily interested in fostering European (both West and East) developer communities. Being an enthusiastic co-organizer of two Google Developer Groups (GDGs) in Stuttgart, Germany and Ufa, Russia, I love engaging with local developers to help them be successful building products using Google technologies. Besides, I'm also a happy and proud Google Top Contributor (TC) at the Google+, Gmail, Google Web Search and several other product forums (English, German, and Russian) and am doing my best to help users on a daily basis to learn how to use Google products better and troubleshoot their issues. With such a broad network, many of whom cannot be at I/O in person, I am excited to take what I learn and share it with my fellow GDGers.
Misha: As a passionate web developer, I am mostly interested in web-related technologies like HTML5, Google Chrome as development tool, Google Chrome extensions, Google App Engine and the knowhow of Google APIs. Also, my skills in developing Android applications is something I would definitely like to boost. I am sure these new technologies will bring new boost to my mojo and attending I/O will inspire me to start new projects like the ones I've worked on recently, the Google Developer Day Android application, the FontVending Android application and the Helper for Google+ Chrome extension.
Tell us your plans for Google I/O this year.
Aygul: The day before we are planning to participate in the GDG Organizers Summit to meet GDG managers from around the world and discuss all together how we can take our community to the next level.
With all the sessions that are going in parallel, it's pretty challenging to choose only one session to attend at a time. I've said that I'm going to watch every Google I/O talk later at home, but some of them are definitely on my must-attend-and-hear-it-live list. Getting More from the Google+ Platform, Android Design for Success, The Web Can Do That!?, and From Weekend Hack to Funded Startup - How to Build Your Team and Raise Money are among them.
Besides Sessions and Code Labs, I'm really excited to see so many excellent products will be presented at Sandbox this year. As a true productivity junkie, I can’t wait to talk to creators of GQueues in person.
Misha: Every year Google presents at Google I/O some new pieces of technology that may form the future landscape of the web. I will make sure to learn about all the announcements on Google+ API, Google App Engine, Dart, Chrome tooling, Google Cloud Printing, and Google Drive API.
This year I would like to participate in as many Google I/O sessions as possible. Some of them are Dart - A Modern Web Language, Building Mobile App Engine Backends for Android, iOS and the Web, Beyond Paper: Google Cloud Print and the Future of Printing, and Powering your Application's Data using Google Cloud Storage. I chose these sessions because these are new Google technologies and I would like to incorporate them into my projects.
Not coming to Google I/O 2012 in person? Not a problem. Watch the keynote and dozens of other sessions streamed live at developers.google.com/io.
Aygul Zagidullina is a research scientist at the University of Stuttgart. Misha Matiyenko-Kupriyanov is a web developer at Deutsche Online Medien GmbH.
Edited and posted by Domenica Liberti and Scott Knaster, Google I/O Team.
2013, By: Seo Master
salam every one, this is a topic from google web master centrale blog: Webmaster level: All
One of the great things about working at Google is that we get to take advantage of an enormous amount of computing power to do some really cool things. One idea we tried out was to let webmasters know about their potentially hackable websites. The initial effort was successful enough that we thought we would take it one step further by expanding our efforts to cover other types of web applications—for example, more content management systems (CMSs), forum/bulletin-board applications, stat-trackers, and so on.
This time, however, our goal is not just to isolate vulnerable or hackable software packages, but to also notify webmasters about newer versions of the software packages or plugins they're running on their website. For example, there might be a Drupal module or Joomla extension update available but some folks might not have upgraded. There are a few reasons a webmaster might not upgrade to the newer version and one of the reasons could be that they just don't know a new version exists. This is where we think we can help. We hope to let webmasters know about new versions of their software by sending them a message via Webmaster Tools. This way they can make an informed decision about whether or not they would like to upgrade.
One of the ways we identify sites to notify is by parsing source code of web pages that we crawl. For example, WordPress and other CMS applications include a generator meta tag that specifies the version number. This has proven to be tremendously helpful in our efforts to notify webmasters. So if you're a software developer, and would like us to help you notify your users about newer versions of your software, a great way to start would be to include a generator meta tag that tells the version number of your software. If you're a plugin or a widget developer, including a version number in the source you provide to your users is a great way to help too.
We've seen divided opinions over time about whether it's a good security practice to include a version number in source code, because it lets hackers or worm writers know that the website might be vulnerable to a particular type of exploit. But as Matt Mullenweg pointed out, "Where [a worm writer's] 1.0 might have checked for version numbers, 2.0 just tests [a website's] capabilities...". Meanwhile, the advantage of a version number is that it can help alert site owners when they need to update their site. In the end, we tend to think that including a version number can do more good than harm.
We plan to begin sending out the first of these messages soon and hope that webmasters find them useful! If you have any questions or feedback, feel free to comment here.
this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com
One of the great things about working at Google is that we get to take advantage of an enormous amount of computing power to do some really cool things. One idea we tried out was to let webmasters know about their potentially hackable websites. The initial effort was successful enough that we thought we would take it one step further by expanding our efforts to cover other types of web applications—for example, more content management systems (CMSs), forum/bulletin-board applications, stat-trackers, and so on.
This time, however, our goal is not just to isolate vulnerable or hackable software packages, but to also notify webmasters about newer versions of the software packages or plugins they're running on their website. For example, there might be a Drupal module or Joomla extension update available but some folks might not have upgraded. There are a few reasons a webmaster might not upgrade to the newer version and one of the reasons could be that they just don't know a new version exists. This is where we think we can help. We hope to let webmasters know about new versions of their software by sending them a message via Webmaster Tools. This way they can make an informed decision about whether or not they would like to upgrade.
One of the ways we identify sites to notify is by parsing source code of web pages that we crawl. For example, WordPress and other CMS applications include a generator meta tag that specifies the version number. This has proven to be tremendously helpful in our efforts to notify webmasters. So if you're a software developer, and would like us to help you notify your users about newer versions of your software, a great way to start would be to include a generator meta tag that tells the version number of your software. If you're a plugin or a widget developer, including a version number in the source you provide to your users is a great way to help too.
We've seen divided opinions over time about whether it's a good security practice to include a version number in source code, because it lets hackers or worm writers know that the website might be vulnerable to a particular type of exploit. But as Matt Mullenweg pointed out, "Where [a worm writer's] 1.0 might have checked for version numbers, 2.0 just tests [a website's] capabilities...". Meanwhile, the advantage of a version number is that it can help alert site owners when they need to update their site. In the end, we tend to think that including a version number can do more good than harm.
We plan to begin sending out the first of these messages soon and hope that webmasters find them useful! If you have any questions or feedback, feel free to comment here.
this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com
salam every one, this is a topic from google web master centrale blog:
Webmaster Level: Beginner
Cross-posted on the Google Grants Blog
A New Year’s resolution
In the spirit of the holidays, here at Google we wanted to take the time to help out those who spend their days making our world a better place: non-profit organizations. A few weeks back, we asked webmasters of non-profits to submit their organization’s site to our Search Quality team for analysis. After some number crunching and trend analysis, we’re back to report on general areas for improvement and to guide you towards some useful resources!
Making our list, checking it twice
First, we’d like thank all of the amazing organizations who participated by submitting their sites. We got some great results, and are excited about all the diverse non-profit causes out there.
Our analysis will take place in the following two posts. The first post will focus on cleaning up HTML tags in your source code, while the second will examine improving user experience via better content accessibility.
Visions of... URLs... dancing in our heads
The great news is, every single site submitted had at least one or two areas to tweak to make it even better! So this information should be helpful to everyone out there, big or small. Just to whet your appetites, here’s a quick list of items that will not be addressed in our following posts, but that had some room for improvement in a large percentage of submitted sites:
- Keep an eye on proper canonicalization: 56% of analyzed non-profit sites could improve their canonicalization practices. You can read more about canonicalization in this blog post from a previous site clinic.
- Make sure your volunteer/support sections are visible: 29% of our submissions could improve their sites by making their support, volunteer, or donation sections easier to find. A great way to accomplish this is to add a donations tab to your navigation bar so it’s just one click away at all times.
- Protect your confidential information: Lots of non-profits, especially those in the medical industry, deal with some very important and confidential information. Read up on how to control your crawled and indexed content, and remember to protect confidential content through proper authentication measures.
- Make your Flash sites search engine friendly: We saw some beautiful sites running on Flash. Search engines have a hard time understanding Flash files, and we’re working to improve Flash comprehension on our end, but here are some discussion points on how you can help us understand your Flash content.
Contributors: Aditya Goradia, Brandon Falls, Charlene Perez, Diara Dankert, Michael Wyszomierski, and Nelson Bradley
this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com