Blog Sprint Junior-Entreprise

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-settings.php on line 472

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-settings.php on line 487

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-settings.php on line 494

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-settings.php on line 530

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/26/d232013928/htdocs/blog/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/26/d232013928/htdocs/blog/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/26/d232013928/htdocs/blog/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/26/d232013928/htdocs/blog/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/26/d232013928/htdocs/blog/wp-includes/classes.php on line 611

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/26/d232013928/htdocs/blog/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/26/d232013928/htdocs/blog/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/26/d232013928/htdocs/blog/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/26/d232013928/htdocs/blog/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/26/d232013928/htdocs/blog/wp-includes/classes.php on line 728

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/26/d232013928/htdocs/blog/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/26/d232013928/htdocs/blog/wp-includes/cache.php on line 425

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-includes/theme.php on line 623

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/26/d232013928/htdocs/blog/wp-includes/class.wp-dependencies.php on line 15

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/exec-php/exec-php.php on line 22

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/exec-php/includes/manager.php on line 34

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/exec-php/includes/manager.php on line 35

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/exec-php/includes/manager.php on line 36

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/exec-php/includes/admin.php on line 42

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/exec-php/includes/admin.php on line 51

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/exec-php/includes/admin.php on line 52

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/exec-php/includes/admin.php on line 53

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/exec-php/includes/ajax.php on line 63

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/exec-php/includes/cache.php on line 33

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/exec-php/includes/cache.php on line 42

Strict Standards: Redefining already defined constructor for class ngg_Tags in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/lib/nggallery.lib.php on line 485

Deprecated: Function eregi() is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/wptouch/wptouch.php on line 144

Deprecated: Function eregi() is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/wptouch/wptouch.php on line 144

Deprecated: Function eregi() is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/wptouch/wptouch.php on line 144

Deprecated: Function eregi() is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/wptouch/wptouch.php on line 144

Deprecated: Function eregi() is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/wptouch/wptouch.php on line 144

Deprecated: Function eregi() is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/wptouch/wptouch.php on line 144

Deprecated: Function eregi() is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/wptouch/wptouch.php on line 144

Deprecated: Function eregi() is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/wptouch/wptouch.php on line 144

Deprecated: Function eregi() is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/wptouch/wptouch.php on line 144

Deprecated: Function eregi() is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/wptouch/wptouch.php on line 144

Deprecated: Function eregi() is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/wptouch/wptouch.php on line 144

Deprecated: Function eregi() is deprecated in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/wptouch/wptouch.php on line 144

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method cformsRSS::vars() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-includes/plugin.php on line 163

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/post.php on line 2747

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/post.php on line 2706

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/classes.php on line 230

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method cformsRSS::outputRSS() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-includes/plugin.php on line 311

Warning: Cannot modify header information - headers already sent by (output started at /homepages/26/d232013928/htdocs/blog/wp-settings.php:472) in /homepages/26/d232013928/htdocs/blog/wp-includes/feed-rss2.php on line 8
Blog Sprint Junior-Entreprise http://blog.sprint-je.com Un autre regard sur le management et les technologies.
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/post.php on line 2747

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41
Fri, 15 Apr 2011 06:00:11 +0000 http://wordpress.org/?v=2.6.1 en
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55
Traduction instantanée, une réalité grâce à Samsung ?
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/traduction-instantanee-une-realite-grace-a-samsung-590
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/traduction-instantanee-une-realite-grace-a-samsung-590#comments
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41
Fri, 15 Apr 2011 06:00:11 +0000 Valentin http://blog.sprint-je.com/?p=590 Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10
Pouvoir se balader dans n’importe-quel coin du monde sans avoir à subir les affres des barrières linguistiques, un rêve qui va peut-être bientôt devenir réalité. Samsung travaillerait sur la réalisation d’un outil de traduction simultanée, « Real Translator », qui permettrait à deux interlocuteurs ne parlant pas la même langue de se comprendre entre eux [...]]]> Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Pouvoir se balader dans n’importe-quel coin du monde sans avoir à subir les affres des barrières linguistiques, un rêve qui va peut-être bientôt devenir réalité.

Samsung travaillerait sur la réalisation d’un outil de traduction simultanée, « Real Translator », qui permettrait à deux interlocuteurs ne parlant pas la même langue de se comprendre entre eux sans avoir à sortir un dictionnaire.

L’appareil se présente sous la forme d’un écran AMOLED transparent qui traduit et affiche au format texte les mots prononcés par chacun des protagonistes de la conversation, et ce sur chaque face de la dalle translucide.

Samsung indique que ce terminal magique pourrait être produit dans un délai assez court, ce qui paraît plausible quand on sait que chacune des technologies utilisées est déjà disponible sur divers appareils ou sous la forme de logiciels, à savoir :

la traduction instantanée (cf Google Translate)
le speech-to-text (voir les prouesses de l’application Dragon pour iPhone)
les écrans AMOLED translucides (justement chez Samsung…)

Pour réaliser ce projet, il « suffirait » donc d’assembler ces trois technologies en un seul appareil. Rappelons aussi à ce sujet que Google travaille sur « Conversation Mode », une fonctionnalité qui traduirait en temps réel une conversation téléphonique dans un autre langage, mais directement au format audio cette fois, comme le montrent les deux vidéos ci-après.

Voir les vidéos sur le Blog-note.

]]>
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/traduction-instantanee-une-realite-grace-a-samsung-590/feed
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55
France-IX, point d’échange Internet parisien, se consolide
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/france-ix-point-d%e2%80%99echange-internet-parisien-se-consolide-581
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/france-ix-point-d%e2%80%99echange-internet-parisien-se-consolide-581#comments
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41
Sun, 10 Apr 2011 06:00:22 +0000 Valentin http://blog.sprint-je.com/?p=581 Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10
Internet… Ça peut paraître complexe à première vue, mais en fait, ce réseau mondial n’est « que » l’agrégation de multiples réseaux nationaux de fournisseurs d’accès à Internet (FAI). Pour ce faire, Orange, SFR, Free, etc, s’échangent du trafic Internet avec Deustsche Telecom, British Telecom, Verizon, AT&T, etc, en des points spéciaux [...]]]> Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Internet… Ça peut paraître complexe à première vue, mais en fait, ce réseau mondial n’est « que » l’agrégation de multiples réseaux nationaux de fournisseurs d’accès à Internet (FAI). Pour ce faire, Orange, SFR, Free, etc, s’échangent du trafic Internet avec Deustsche Telecom, British Telecom, Verizon, AT&T, etc, en des points spéciaux du réseau que l’on appelle GIX ou IXP. Wikipedia résume cela :

Un Internet Exchange Point (ou IX ou IXP ou point d’échange Internet), également appelé Global Internet eXchange (ou GIX), est une infrastructure physique permettant aux différents fournisseurs d’accès Internet (ou FAI ou ISP) d’échanger du trafic Internet entre leurs réseaux grâce à des accords mutuels dits de «peering». Ces échanges de trafic se font ainsi sans coût supplémentaire.

Lancé il y a un peu plus de 8 mois, France-IX a pour mission de « consolider et d’élever Paris au rang de place de peering mondial, en développant une offre de services répondant aux besoins actuels du marché, et en réunissant des opérateurs et des fournisseurs de contenus et de services internet français, mais aussi étrangers ».

Face à l’essor du trafic Internet, l’association parisienne, qui exploite donc un point d’échange Internet, se dote de puissants multiplexeurs/démultiplexeurs capables de transporter les signaux à 120 Gbit/s via la fibre optique.

Lire la suite sur le Blog-note.

]]>
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/france-ix-point-d%e2%80%99echange-internet-parisien-se-consolide-581/feed
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55
Au Japon, le réseau Internet a tenu bon
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/au-japon-le-reseau-internet-a-tenu-bon-587
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/au-japon-le-reseau-internet-a-tenu-bon-587#comments
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41
Tue, 05 Apr 2011 06:00:37 +0000 Valentin http://blog.sprint-je.com/?p=587 Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10
A la différence du réseau de téléphonie mobile, le réseau Internet japonais a bien résisté aux tremblements de terre et au tsunami selon une étude de la société Renesys. Une chance pour les habitants. C’est malheureusement une des seules bonnes nouvelles en provenance du Japon après la terrible catastrophe qui frappe le [...]]]> Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

A la différence du réseau de téléphonie mobile, le réseau Internet japonais a bien résisté aux tremblements de terre et au tsunami selon une étude de la société Renesys. Une chance pour les habitants. C’est malheureusement une des seules bonnes nouvelles en provenance du Japon après la terrible catastrophe qui frappe le pays. D’après une étude publiée sur le blog de la société Renesys, spécialiste de

la surveillance du Web, l’infrastructure Internet du Japon n’a pas été affectée par le tremblement de terre et ses répliques ni par le tsunami qui ont frappé le pays.

Selon James Cowie, le directeur technique de Renesys, la plupart des sites restent opérationnels et Internet offre des fonctions de communications essentielles pour les habitants en cette période de crise (messagerie instantanée Twitter, murs Facebook, téléphonie IP avec Skype, etc.).

La société qui a aussi étudié les variations du trafic Internet en Égypte et en Libye suite à la censure opérée par les dictatures en place cite notamment les mesures de trafic fournies par Google dont les graphiques sont éloquents.

Mais pourquoi Internet fonctionne-t-il si bien ? Plus d’explications sur le Blog-note.

]]>
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/au-japon-le-reseau-internet-a-tenu-bon-587/feed
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55
Qwiki : entrez dans le futur des moteurs de recherche
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/qwiki-entrez-dans-le-futur-des-moteurs-de-recherche-579
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/qwiki-entrez-dans-le-futur-des-moteurs-de-recherche-579#comments
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41
Thu, 25 Nov 2010 06:00:17 +0000 Valentin http://blog.sprint-je.com/?p=579 Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10
Connaissez-vous Qwiki ? Il s’agit d’un moteur de recherche de nouvelle génération. Non pas qu’il soit plus « intelligent » que les nouveaux entrants mais qu’il propose une expérience unique de restitution des résultats. À l’origine de ce projet, il y a le fondateur d’AltaVista (le français Louis Monier, Cocorico !). La page d’accueil de Qwiki Qwiki [...]]]> Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Connaissez-vous Qwiki ? Il s’agit d’un moteur de recherche de nouvelle génération. Non pas qu’il soit plus « intelligent » que les nouveaux entrants mais qu’il propose une expérience unique de restitution des résultats. À l’origine de ce projet, il y a le fondateur d’AltaVista (le français Louis Monier, Cocorico !).

La page d’accueil de Qwiki

Qwiki se différencie des autres moteurs sur deux points :

Il n’y a pas de page de résultats de recherche (grâce à un système de recherche assistée)

Les résultats sont consultés directement dans l’interface sous forme d’un diaporama animé qui résume différentes sources et dicte le texte grâce à une synthèse vocale

La page de résultat de Qwiki

Autant le dire tout de suite : l’expérience est bluffante, car le résumé est de très bonne qualité (malheureusement en anglais) et car la synthèse vocale est très agréable (diction fluide). Ici une petite vidéo de démonstration :

Fenêtre externe

Avec ce mode d’interaction nous pouvons tout à fait affirmer que c’est un nouveau paradigme de la recherche d’information en ligne, Qwiki s’apparente ainsi plus à une meta-encyclopédie à la volée qu’à un moteur de recherche classique. Est-ce la fin de Google ou de Wikipedia ? Non absolument pas car l’information remontée est beaucoup plus pauvre… mais bien plus facile à consommer.

C’est donc là que réside le secret de Qwiki : offrir une expérience plus proche du divertissement que de la recherche documentaire. Donc non, Qwiki n’est absolument pas un concurrent de Google sur votre ordinateur, mais trouvera tout à fait sa place et son utilité sur des terminaux alternatifs comme les touchbooks ou les TV connectés. Nous sommes donc dans une optique assez proche de celle proposée par Youtube Leanback.

Ce moteur de recherche préfigure à mon avis une nouvelle vague de services en ligne (nouveautés ou adaptation de services existants) proposant une expérience d’utilisation radicalement différente et parfaitement adaptée aux nouveaux terminaux (Faut-il réinventer le web pour les touchbooks ?).

Source : Retrouvez d’autres articles (aussi intéressants) sur Blog-Note.tk

]]>
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/qwiki-entrez-dans-le-futur-des-moteurs-de-recherche-579/feed
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55
SmavNet, rétablir les communications en milieu hostile grâce à des minirobots
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/smavnet-retablir-les-communications-en-milieu-hostile-grace-a-des-minirobots-570
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/smavnet-retablir-les-communications-en-milieu-hostile-grace-a-des-minirobots-570#comments
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41
Sat, 20 Nov 2010 07:00:47 +0000 Valentin http://blog.sprint-je.com/?p=570 Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10
En cas de catastrophe naturelle ou humaine, en plus des questions d’approvisionnement en eau, en vivres et en matériels de premiers secours, se pose désormais la question des réseaux de communications. L’Ecole Polytechnique de Lausanne s’est intéressée au sujet est à développer le projet SMAVNET pour [...]]]> Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

En cas de catastrophe naturelle ou humaine, en plus des questions d’approvisionnement en eau, en vivres et en matériels de premiers secours, se pose désormais la question des réseaux de communications. L’Ecole Polytechnique de Lausanne s’est intéressée au sujet est à développer le projet SMAVNET pour Swarming Micro Air Vehicle Network. Il s’agit de petits robots volants capable de déployer un réseau aérien fonctionnel.

Ce « Swarming Micro Air Vehicle Network » se compose d’une dizaine de petits avions légers qui transportent sur eux un dongle USB permettant une connexion sans fil.

Une fois dans le ciel, les avions optimisent leur position pour couvrir la zone et fournissent ainsi un accès sans fil sur une large distance à n’importe quel ordinateur (ou téléphone) se trouvant au sol. L’objectif est de rétablir le réseau rapidement pour maintenir les communications.

Pour le moment, les MAV (Micro Air Vehicle) ne sont pas autonomes (30 minutes environ) mais avec quelques petits panneaux solaires, ils seront dans le futur capables de tourner indéfiniment dans le ciel…

Source : Retrouvez d’autres articles (aussi intéressants) sur Blog-Note.tk

]]>
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/smavnet-retablir-les-communications-en-milieu-hostile-grace-a-des-minirobots-570/feed
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55
Les interfaces du futur
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/les-interfaces-du-futur-568
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/les-interfaces-du-futur-568#comments
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41
Mon, 15 Nov 2010 07:00:32 +0000 Valentin http://blog.sprint-je.com/?p=568 Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10
A quels types d’interfaces aurons-nous à faire en 2014 ? Et 2014 c’est vraiment demain. Alors il y aura du tactile, beaucoup de tactile et encore du tactile. C’est en tout cas la vision de TAT, une société suédoise spécialisée dans l’innovation et le design. Bureau, miroir, téléphone/tablette, tout y passe. Rien de [...]]]> Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

A quels types d’interfaces aurons-nous à faire en 2014 ? Et 2014 c’est vraiment demain. Alors il y aura du tactile, beaucoup de tactile et encore du tactile. C’est en tout cas la vision de TAT, une société suédoise spécialisée dans l’innovation et le design.

Bureau, miroir, téléphone/tablette, tout y passe. Rien de révolutionnaire mais une vision que je trouve réaliste au regard des technologies et usages actuels. Je vous laisse juges…

Source : Retrouvez d’autres articles (aussi intéressants) sur Blog-Note.tk

]]>
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/les-interfaces-du-futur-568/feed
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55
La réalité augmentée bientôt dans nos magazines
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/la-realite-augmentee-bientot-dans-nos-magazines-572
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/la-realite-augmentee-bientot-dans-nos-magazines-572#comments
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41
Wed, 10 Nov 2010 07:00:09 +0000 Valentin http://blog.sprint-je.com/?p=572 Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10
La réalité augmentée s’invite un peu partout et investit maintenant la presse écrite, ce qui offrira peut-être à cette dernière des espoirs d’autres débouchés que les tablettes multimédia. Réalité augmentée ? Mais si.. vous en avez entendu parlé, j’en suis certain. Non ? Bon si cela ne vous dit rien, Wikipedia vous en rappelle le [...]]]> Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

La réalité augmentée s’invite un peu partout et investit maintenant la presse écrite, ce qui offrira peut-être à cette dernière des espoirs d’autres débouchés que les tablettes multimédia.

Réalité augmentée ?
Mais si.. vous en avez entendu parlé, j’en suis certain.
Non ? Bon si cela ne vous dit rien, Wikipedia vous en rappelle le sens :

Le concept de réalité augmentée vise à compléter notre perception du monde réel, en y ajoutant des éléments fictifs, non perceptibles naturellement. La réalité augmentée désigne donc les différentes méthodes qui permettent d’incruster de façon réaliste des objets virtuels dans une séquence d’images. Ses applications sont multiples et touchent de plus en plus de domaines : jeux vidéo et edutainment, chasses au trésor virtuelles, cinéma et télévision (post-production, studios virtuels, retransmissions sportives…), industries (conception, design, maintenance, assemblage, pilotage, robotique et télérobotique, implantation, étude d’impact…), médical, etc.
Le quotidien allemand Süddeutsche Zeitung a publié ce week-end un supplément magazine intégrant plusieurs pages avec réalité augmentée, dont les suppléments visuels, dont certains animés et d’autres en 3D sont accessibles via iPhone avec iOS4 ou smartphone Android.

Cette vidéo montre les meilleurs extraits en réalité augmentée.

Suite au succès de cette édition, relayée sur AugmentedBlog, le magazine a mis à disposition trois pages au format image à imprimer afin que chacun puisse s’essayer à la lecture enrichie avec son smartphone. Vous pouvez donc vous aussi tenter l’expérience. Pour cela vous devrez d’abord imprimer les pages proposées. Installez ensuite l’application gratuite de réalité augmentée Junaio pour iPhone ou Android, puis allez dans les « Channels » et sélectionnez « Süddeutsche Zeitung Magazin » dans les catégories « New » ou « Featured ». Pointez ensuite le capteur photo de votre mobile sur les pages que vous avez imprimées et regardez.

Source : Retrouvez d’autres articles (aussi intéressants) sur Blog-Note.tk

]]>
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/la-realite-augmentee-bientot-dans-nos-magazines-572/feed
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55
Naviguez de mail en mail dans Gmail (sans repasser par la boite de réception)
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/naviguez-de-mail-en-mail-dans-gmail-sans-repasser-par-la-boite-de-reception-574
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/naviguez-de-mail-en-mail-dans-gmail-sans-repasser-par-la-boite-de-reception-574#comments
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41
Fri, 05 Nov 2010 09:25:59 +0000 Valentin http://blog.sprint-je.com/?p=574 Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10
Gmail vient de publier dans ses labs une nouvelle fonction que certains trouveront probablement très pratique : « Avance auto », qui permet de passer automatiquement d’un email au suivant sans repasser par la liste. A l’image de ce que propose déjà de nombreux courrielleurs comme Thunderbird par exemple, il est maintenant possible de passer [...]]]> Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Gmail vient de publier dans ses labs une nouvelle fonction que certains trouveront probablement très pratique : « Avance auto », qui permet de passer automatiquement d’un email au suivant sans repasser par la liste.

A l’image de ce que propose déjà de nombreux courrielleurs comme Thunderbird par exemple, il est maintenant possible de passer au mail suivant (ou précédent dans la chronologie de réception en fonction de vos préférences) dans Gmail lorsque, dans sa boîte ou dans un label, on vient de supprimer, archiver ou ignorer un mail ou une conversation.

Gain de temps garanti dans la lecture de vos mails quotidiens, même s’il est parfois utile de revenir à sa liste pour avoir une vue d’ensemble et garder quelques repères dans ses conversations (vous pourrez toujours y retourner manuellement).

La fonction Avance auto est disponible dans les paramètres à l’onglet « Labs » (ou « Labos » en français), où il vous faudra aller l’activer pour pouvoir l’utiliser.

Source : Retrouvez d’autres articles (aussi intéressants) sur Blog-Note.tk

]]>
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/naviguez-de-mail-en-mail-dans-gmail-sans-repasser-par-la-boite-de-reception-574/feed
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55
Guide GoogleBots : comprenez-les pour le plaisir, ou pour améliorer votre référencement
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/guide-googlebots-comprenez-les-pour-le-plaisir-ou-pour-ameliorer-votre-referencement-565
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/guide-googlebots-comprenez-les-pour-le-plaisir-ou-pour-ameliorer-votre-referencement-565#comments
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41
Thu, 30 Sep 2010 11:29:48 +0000 Valentin http://blog.sprint-je.com/?p=565 Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10
GoogleBot, ça vous dit quelque chose ? Si non, sachez que ce sont des robots appartenant à Google, qui passent leurs journées à scanner les pages du Web (ça en fait du boulot !) et à les indexer grâce aux éléments qu’ils y trouvent. Pour rassurez l’Association Protectrice des Robots, ces machines ne sont [...]]]> Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

GoogleBot, ça vous dit quelque chose ?

Si non, sachez que ce sont des robots appartenant à Google, qui passent leurs journées à scanner les pages du Web (ça en fait du boulot !) et à les indexer grâce aux éléments qu’ils y trouvent.
Pour rassurez l’Association Protectrice des Robots, ces machines ne sont (a priori) pas doté de « vie » (même robotique). D’ailleurs, comme ce sont des « machines », elles utilisent des éléments (plus ou moins) fixes sur les pages Web pour les indexer. Ce sont ces éléments que l’on peut optimiser sur son site pour améliorer son référencement sur le Web (un vrai Graal pour beaucoup de site).

Si vous voulez approfondir vos connaissances en SEO (Search Engine (les fmaeux GoogleBots !) Optimization) et en référencement, ou si vous débutez dans cet art passionnant et parfois un peu mystérieux, vous pouvez aller puiser à la source (Google) et feuilleter le Search Engine Optimization Starter Guide de Google, un fascicule gratuit de 32 pages édité au format PDF par Google, qui vient d’en publier une mise à jour.

Si vous n’êtes pas trop familier avec l’anglais, vous pouvez toujours vous rabattre sur la version précédente, dont le blog Ramenos avait fait une traduction en français.

Source : blog-note.tk

]]>
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/guide-googlebots-comprenez-les-pour-le-plaisir-ou-pour-ameliorer-votre-referencement-565/feed
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55
Le club robot de TMSP en finale .
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/le-club-robot-de-tmsp-en-final-559
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/link-template.php on line 98
http://blog.sprint-je.com/non-classe/le-club-robot-de-tmsp-en-final-559#comments
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/26/d232013928/htdocs/blog/wp-includes/functions.php on line 41
Thu, 04 Jun 2009 07:09:09 +0000 Baptiste http://blog.sprint-je.com/?p=559 Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10
Les nuits blanches auront finies par payer pour le club robot de TELECOM & Management SudParis, en effet l’équipe Tech The Wave a reussi à se classer second à la coupe de France de robotique. Cette compétition ( anciemenent connue comme coupe E=M6), organisé par Planète Sciences, s’est déroulée du mercredi 20 au samedi 23 mai [...]]]> Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/26/d232013928/htdocs/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Les nuits blanches auront finies par payer pour le club robot de TELECOM & Management SudParis, en effet l’équipe Tech The Wave a reussi à se classer second à la coupe de France de robotique.

Cette compétition ( anciemenent connue comme coupe E=M6), organisé par Planète Sciences, s’est déroulée du mercredi 20 au samedi 23 mai dernier. Le club INTech de Telecom SudParis y a envoyé deux équipes, Arch’INTech et Tech The Wave pour se mesurer au près de 200 autres.
Les deux équipes se sont préparées toute l’année, ont vu leurs robots homologués pour la coupe, preuve qu’elles sont parvenues à construire un robot fonctionnel. Après cette première étape s’est déroulée la phase de qualification ou l’équipe Tech The Wave a terminée 3ème du classement, ce qui lui a valu une place pour les finales. Les 16 robots qualifiés ont été mis à rude épreuve, enchaînant les matchs à intervalles très courts. L’équipe de TSP, disposant d’un robot fiable malgré sa simplicité s’est hissée jusqu’à la finale-même où elle a obtenu le titre de vice-championne de France, derrière Microb Technology. Ce résultat a octroyé à l’équipe une place pour le lendemain à Eurobot, la coupe internationale, où elle a finie cinquième.
En tant que premier club universitaire de la coupe, 4 étudiants de l’équipe sont invités au Japon du 5 au 19 aout pour l’IDC à Tokyo afin d’y representer la France. Quelle aventure !