Deprecated: Assigning the return value of new by reference is deprecated in /homepages/17/d244771740/htdocs/wp-settings.php on line 512

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/17/d244771740/htdocs/wp-settings.php on line 527

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/17/d244771740/htdocs/wp-settings.php on line 534

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/17/d244771740/htdocs/wp-settings.php on line 570

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

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

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

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

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

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

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

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

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

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

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

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

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/17/d244771740/htdocs/wp-includes/cache.php on line 431

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/17/d244771740/htdocs/wp-includes/query.php on line 61

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/17/d244771740/htdocs/wp-includes/theme.php on line 1109

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/17/d244771740/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/17/d244771740/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/17/d244771740/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/17/d244771740/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/17/d244771740/htdocs/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/17/d244771740/htdocs/wp-includes/http.php on line 61

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGeneratorLoader::Enable() should not be called statically in /homepages/17/d244771740/htdocs/wp-includes/plugin.php on line 339

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/17/d244771740/htdocs/wp-includes/plugin.php on line 166

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/post.php on line 2872

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/post.php on line 2833

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/classes.php on line 345

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/17/d244771740/htdocs/wp-includes/plugin.php on line 339

Warning: Cannot modify header information - headers already sent by (output started at /homepages/17/d244771740/htdocs/wp-settings.php:512) in /homepages/17/d244771740/htdocs/wp-includes/feed-rss2.php on line 8
Télé-Évangéliste du LOL http://yaourtiere.org Poney Locats et Grille de lecture (PJ )
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/post.php on line 2872

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 41
Sun, 08 May 2011 16:55:48 +0000
http://wordpress.org/?v=2.7 en hourly 1
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 55
[Billet Sponsorisé] Mon week end au milieu des Black-Hat rose…
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/poney-arc-en-ciel-et-chapeau-noir
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/poney-arc-en-ciel-et-chapeau-noir#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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 41
Sun, 08 May 2011 16:53:04 +0000
Yakamo http://yaourtiere.org/?p=136 Bon puisque la tradition le veut (et puis surtout parce que j’ai 4 heures de train à rien glander vu que je n’ai pas de film à mater ni de gnome à embêter) je vais vous faire un débrief totalement subjectif partial et tendancieux sur le Black Hat Camp.

Attention chanteurs du dimanche, poneys, derviches tourneurs et cornemuse inside. *

*(Liste non contractuelle)

Paris, Samedi 07mai 06h45: Réveil, enfin réveil c’est beaucoup dire, emmergeage laborieux dans état second de torpeur intellectuelle et physique serait plus vrai mais ne chipotons pas. Aujourd’hui c’est le grand jour, c’est le jour du bal … Euh ouais non … Aujourd’hui c’est black Hat chez les toulousains.

08h11: Montée dans le train, avec mes deux acolytes du jour Messieurs BlackMelvyn et Gwaradenn (que nous nommerons Mr. Black et Mr. Pink dans un souci de déformation de la réalité tarantinesque). Sauf qu’en fait je n’en trouve aucun des deux … L’organisation n’est pas une qualité requise pour un BH (surtout en matière de train).

13h44: Arrivée à Toulouse direction le capitole (par la droite c’est plus court … PJ) en compagnie cette fois ci de Mr. Black et Mr. Pink que j’ai finalement retrouvé l’un en l’attirant avec un café l’autre à coté d’une blonde enfin une histoire comme ça quoi …

18h30: Arrivée au lieu de rendez-vous… euh ouais non j’ai merdé sur la direction mais là quand même.

14h15: Arrivée au lieu de rendez-vous … Euh on m’avait dit une vingtaine de personnes, c’est qui les 60 autres ?!?

Heureusement que quelque têtes connues se distinguent dans la foule.

En vrac, notre seul et unique Breton 100% pur beurre garanti sans additif j’ai nommé Eclipsis, notre seul et unique marseillais 100% pur pastis garanti sans diluant monsieur Didier.

Monsieur Xavfun avec une casquette en cuir rose qui m’a rappelée les plus belles années des villages People.

Satanas et Diabolo ou l’inverse alias monsieur Bertimus et son acolyte de toujours Stoff (ça commence à faire beaucoup d’acolytes, si ça vire au trucs dégueulasses je suis pas responsable ).

LA MILF du SEO (pour ne pas choquer les oreilles des enfants le prénom de cette personne sera masqué, mais ceux qui étaient là, les vrais, sauront (œil), ouais je fous ça pour faire du rapprochement sémantique (et je fous des parenthèses dans des parenthèses dans des parenthèses , un genre de spin mais en différent)).

Le BotBreeder Beunwa était là aussi (j’ai failli lui en acheter, des bottes (c’est pas une vanne de moi j’avoue)), encadré du mec qui serait capable de te vendre un ebook sur comment pisser debout et qu’en plus tu en sois content monsieur Manga59 de L’agriculteur/Terroriste de la barbe/Savoyard monsieur 512Banque.

Coté Fille la branche Toulousaine de la profession était représenté de fort belle manière par le duo chic et choc Sandrine et Aurélie ainsi que Kodama qui maintenant qu’elle est devenue Bretonne a perdu tout sens de L’humour :D. Enfin à nuancer tout de même par le fait que pour le temps elles ont sévèrement déconnées. On m’avait dit que Toulouse c’était dans le Sud pas à 15 bornes de Quimper.

Et en vrac mais en cool : 5eg, Tutrururulillilo (pardon je crois que j’arriverais pas à l’orthographier) Monsieur Lien Alain (eh ça rime) keeg, lafleur,  jesus, ses potes, la salade verte , le reblochon, 300gr de farine … Euh pardon c’est ma liste de courses. Et puis tous ceux à qui j’ai trop vite parlé, pas assez vu, pas vu, une journée c’est trop court pour parler à tout le monde … faudrait 3semaines.

Bien sur, je ne pouvais pas terminer sans citer les deux Stars, que dis-je les deux maître-étalons (je reste convaincu que cette vanne est drôle n’en déplaise au reste du monde) du SEOBlackHat. Messieurs Rudy et Paul aka la Google team (PJ).

Bon y’avais aussi toi, oui toi que je kiffe comme un rat mort, que quand je te vois je remue la queue comme un pangolin en rut, mais que j’ai bien évidemment oublié parce qu’on est demain et que demain c’est dur. Si tu te sens dans cette description signale toi je viendrais te faire moi-même un bisou. Bref revenons à nos moutons.

15h(30): Début des conférences là on vas faire par 1,2,3,4 etc… ce sera plus simple :

1. Miss Kodama nous présente les forums de presse, bon j’ai essayé de trouver des vannes drôles des anecdotes, n’importe quoi, même un petit truc, et non. Sté bien propre efficace et intéressant.

2. Mister Kevin monte sur scène (enfin vient au bout du bar, mais je trouve que scène ça donne tout de suite un coté épique, bref), pour nous parler des limites des robots sur certaines taches et de l’intérêt de l’humain et de la sous-traitance pour optimiser son temps et ses revenus. Moi je serai tenté de dire : DANS TA GUEULE SKYNET !!!!

3. Bon là y’a eu un trou un mec qui à tout pété. Aucun souvenir de ce passage.

4. The Black Melvyn est ensuite venu nous apprendre comment se faire des cookies en les bourrant. Habituellement je fais ça avec les filles mais il paraît que ça marche aussi pour les cookies (je suis pas sur d’avoir compris, je crois que le cookie dont il parlait ce n’est pas un gâteau). (oui je m’excuse pour la vanne de début de phrase je sais c’est nul mais j’ai pas résisté)

5. Beunwa: La revanche de Skynet. Adieu l’humain, bonjour l’automatisation … C’est pas le BotBreeder pour rien.

6. Vous saviez qu’au lieu de vous taper le grand google vous pouviez le faire avec des petits oiseaux qui gazouillent ? (je trouve ça passablement dégueulasse au demeurant) Merci Wecho_com !!!

7. Pas une conf. mais la personne la plus funky de ce Black Hat Camp est arrivée pour préserver son anonymat nous l’appellerons Madame tata (quel est l’enfoiré qui a dit Madame Claude au fond ?)

8. Monsieur Lafleur à fait une conférence qui à apparemment pas mal fait réagir mais (et je m’en excuse platement) j’ai tout manqué j’étais en train de me rouler dans des coussins de fourrure. Non vous ne voulez pas savoir pourquoi …

9. Back in Business pour Manga59 L’américain qui m’a expliqué qu’en fait c’est lui qui m’a vendu tout ces ebooks pour séduire les filles … Il est fort … très très fort. J’en ai achété 45 … du même modèle …

10. Wecho_com encore lui, Profil, sale, violent, sale, sanglant, sale, hardcore, sale… Voilà voilà … ( bravo quand même pour le gros niveau de monsieur Wecho_com même s’il n’a put être présent.)

11. Enfin Monsieur Aurélien nous à montrer comment systématiser le poste d’article en faisant du spin et tout un tat de truc.

12. Et tout du long les Astuces SEO de Paul et Rudy un peu à la manière d’une Maité ou d’un Joel Robuchon  dstillant la sauce de leur savoir sur l’anguille de nos connaissances (oui cette phrase ne veux rien dire … il est tard )

19h30: Fin de la première partie de la journée…

19h45: Arrêt crêpes pour Mr Pink. Puis direction chez Rudy (à 10 minutes à pieds)

20h25: Ok ne jamais laisser Google Map à BlackMelvyn point à la ligne.

Arrivée chez Rudy

20h45: Retour au bar on débute par un petit verre puis le repas. ARRIVEE DE PERRINE ET DE LA GRENOUILLE VOLANTE !!!! YOUPIIII !!!! (Oui je précise parce que bon mettre plus de trois an à rencontrer celle qui on a partagé sa tong pendant un petit moment c’est triste, je mentionne la grenouille parce qu’il le vaut bien. Point barre. )

21h15: Tout vas bien les discussions commencent bien, les bouteilles sont debouch… … …

Toulouse Dimanche 7 mai 7h45

PS: Merci encore une fois à Paul et Rudy qui se sont bougé le cul pour faire de cette aprèm et soirée un événement very very cool. Joyeux anniversaire à vous les copains et … A quand la prochaine ???

]]>

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/poney-arc-en-ciel-et-chapeau-noir/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 55
4Chan 2/7 : Les boards
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/4chan-27-les-boards
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/4chan-27-les-boards#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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 41
Thu, 09 Dec 2010 18:46:50 +0000
Yakamo http://yaourtiere.org/?p=111 4chan contient 48 sous forums … Voici un détail rapide de chacun d’eux de /a/ à /RB9k/ Il faut savoir que nombre de ces forums sont tout à fait non safe for work voir carrément franchement infâme comme la réputation de 4chan le veut mais qu’il y’en a aussi des tout à fait safe et tout à fait regardables limite trops mignons pour être honnétes. :D

Dans tous les channels (forums types 4chan : 2chan et compagnies) les boards (sous forum) sont représentés par des dossiers de type /bla/ généralement d’une lettre. .

Voici une liste quasi exhaustive des bestioles …

Avant de commencer je rappel que toutes les boards marquées NSFW (Non Safe For Work) sont pas pour les enfants

/3/

12916223079851

Tout ce qui est dédié à la 3D et à la CAO en général. Ca cause plutôt sérieux et y’a plutôt un bon niveau même.

/a/ - Anime & Manga

Dur de ne pas comprendre de quoi on parle. Lieu Safe théoriquement même si de plus en plus de hentaï  apparaît (Hentaï c’est du manga porno pour les non initiés …). C’est assez vite modéré mais ne vous étonnez pas de temps à autre de trouver une fille avec des tentacules dans un endroit pas du tout fait pour ça …

/an/ - Animals & Nature

Animal Varan du komodo

Le thread pour les amis des animaux et de la nature essentiellement des photos de la macro du paysage des trucs assez sympatoche.  De la photo du hamster du voisin jusqu’au plus beaux sommets au levé du soleil (voyez je vous avez dit que y’avait des trucs pour gens “normaux” )

/adv/ - Advice

Des conseils sur tout et n’importe quoi … La vie l’amour les poneys et le reste … C’est total Safe For Work normalement …

/c/ - Anime/Cute

12919164670771

Les images les plus Kawaïï du web  … Plein  de petits chiens, des bonshommes mignon, tout ski est bien quoi :D

/cgl/ - Cosplay & EGL

12919180048131

Tout les matins un grand bol de LOL avec un nuage de LOL et tout ça en costume :D … Mario en vrai :D  Je charie comme ça mais y’a réellement des trucs impressionnants par fois …

/ck/ - Food & Cooking

Des recettes de cuisines (même des bonnes des fois) et beaucoup de lol … Quand je dis du Lol c’est vraiment des trucs drôle halakon et rien de choquant.

/co/ - Comics & Cartoons

12919168854561

La board pour les fans du spandex et du slip par-dessus le pantalon … A titre perso j’y traine assez souvent on peut y trouver vraiment des trucs bien …

/d/ - Hentai/Alternative -NSFW

Bon, la ça commence à devenir clair. C’est du hentaï (cul dessiné), mais “alternatif”, Honnêtement ni moi ni vous ne voulons savoir ce qu’alternatif veut dire … Non vraiment pas …

/e/ - Ecchi - NSFW

C’est le film érotique d’ M6 en version manga :D :D Du hentaï mais non porno …

/fa/ - Fashion

12919179260501

Pour toutes les victimes de la mode . C’est assez drôle parfois de lire les conseils.

/fit/ - Health & Fitness -NSFW

La board Veronique et Davina … To to to youtou … bizzarement pas pour les enfants mais je comprends toujjours pas pourquoi cette board est envahie de semi-porn …

/g/ - Technology

12919141292161

Si toi aussi l’idée de lancer des missiles sur tes ptits voisins tout en overcloakant ton serveur de la mort te tente tu peux aller jeter un coup d’œil … Plus sérieusement ça parle matos et geekeries en général…

/gif/ - Animated GIF -NSFW

Bon je vous déconseilles très fortement d’y foutre les pieds . C’est du cul infma e..; et en plus comme c’est du gif … Ca bouge … Sérieux pour un gif drôle trouvé vous allez devoir vous taper des kilomètres de … enfin vous voyez quoi …

/h/ - hentai -NSFW

Vous voulez un dessin?

/hc/ - Hardcore - NSFW + Vomissement assurés

C’est supra hard … j’ai du y passer une fois et l’envie de vomir m’a pris ..; pour ceux qui connaissent c’est du rotten.com dans le texte … pour les autres cherchez pas vous ne voulez pas mettre les pieds sur cette partie.

/hr/ - High Resolution

Des images en HD et HR y’a souvent des trucs vraiment bien mais seulement rien n’empêche une b*** d’être en haute réso … Verdict Non Safe For Work mais on peu trouver des trucs bien.

/i/ - Oekaki - NSFW

La board des dessins fait à la main …  Souvent c’est bien moche mais de temps à autre on tombe sur un joli truc … Pourquoi NSFW ???  parce que qu’est ce que c’est le premier truc que tu dessine quand on te laisse faire … Oui je sais … un b*** … ne me mens pas …

/ic/ - Artwork/Critique

12919182193261

Tui es un artiste en herbe tu voudrais faire critiquer tes travaux ..; cette board est fait pour toi … Si tu supporte mal les critiques n’y vas pas quand même les Users sont très très critiques…

/jp/ - Japan/General

Un board sur la culture  Jap en général c’est absolument SFW mais j’avoue que j’y ai jamais foutu les pieds plus que ça …

/k/ - Weapons

12919184010421

La borad sur les armes ..; les grosses, les moins grosses, bref tout ce qui peut te permettre de potentiellement péter la gueule de ton voisin …

/m/ - Mecha

12919192737301

La boad Mecha c’est la board dédiée aux robots géants et autres : fan de Goldorak et Transformers tu trouvera certainement ton bonheur ici

/mu/ - Music

Parlez de musiques en général … y’a vraiment plein de bons trucs à choper ici … et tout les styles sont représentés …

/n/ - Transportation

Topic dédié aux moyens de transport. En fait c’est une blague de la part de M00t ( l’admin de 4chan) qui avait à l’origine lancé /n/ pour être un board news mais devant le peu de succès il l’a fermé . Depuis une autre board news à été crée.

/news/ - News

Ben voilà News …

/o/ - Auto

Vroom Vroom fait la voiture …

/p/ - Photography

Ici on cause photo et on en poste aussi plein … Y’a du déchet mais y’a vraiment des trucs bluffant de temps à autre. Tout à fait Safe for Work en théorie. J’ai vu passé un peu de nu artistique de tems à autre mais pas plus que ça.

/po/ - Papercraft & Origami

12907578032801

Fan des paper toys ou amateur de bateau/chapeaux en papier tu trouvera ton bonheur ici … (Bon je charrie mais y’a des mecs qui gèrent sacrément la fougère)

/r/ - Request - NSFW

Tu as besoin d’un truc demande le à 4chan … Bon alors oui ils sont capable de faire et trouver quasi n’importe quoi. Il faut généralement payer sa demande (une paire de sein et un bon moyen) de payer.

Sérieux j’y reviendrai plus tard mais vraiment t’as pas envie de demander un truc sur /r/ d’une c’est hautement Non Safe for Work .

/r9k/ - ROBOT9000 - NSFW

C’est comme /b/ mais avec du contenu original à chaque fois … C’est un peu bidon en fait … enfinn de mon point de vue .

/rs/ - rapidshare

Tu as besoin de dl un truc sur rapidshare … tu trouvera peut être ton bonheur ici. C’est plus une sorte de Database qu’une vrai board de forum.

/s/ - Sexy Beautiful Women

De la nana dénudée et jolie … rien de plus rien de moins …

/sp/ - Sports

12919167155061

LA bord pour tout les fans de catch, à part ça ça parle beaucoup sports américains (basball / footballl américains etc … )

/t/ - Torrents

Du torrent (un peu comme pour la board rapidshare) … Ai-je mentionné que sté essentiellement du pr0n …

/tg/ - Traditional Games

Jeux de plateau , jdr , Jokari … enfin jeux traditionnels quoi … Y’a aussi du jeu vidéo mais je sais pas vraiment pourquoi …

/toy/ - Toys

12919182116231

J’achéte des figurines de filles à demi nue et je les expose …  nan je charrie encore c’est tout ce qui est figurines en résine et compagnie …

/trv/ - Travel

Pour tout cux qui voyagent …  Assez pratique quand tu voyage à l’étranger … il m’est arrivé de poser une ou deux question dessus quand je me suis perdu en Espagne. Les réponses ont té vraiment bonnes .

/tv/ - Television & Film

Télé/Séries/ Jack bauer est t’il plus puissant que Walker Texas Ranger

/u/ - Yuri - NSFW

Yuri ça veut dire lesbiennes en Jap… Au départ je m’attendais à des trucs assez infâmes quand j’y ai foutu les pieds … Et … pas tant que ça en fait, y’a du cul certes mais c’est sommes toute assez soft et c’est plus le coté amour entre femmes qui est mis en avant ..; (bon je suis peut être tombé dans un bon jour aussi et ce n’est pas pour ça que ça reste visionnable du bureau. )

/v/ - Video Games

1291919854604s1

Bon ben voilà quoi …

/w/ - Anime/Wallpapers et /wg/ - Wallpapers/General

Y’a des putains de wallpapers qui déchirent sérieux …  C’est SFW sérieux allez y faire un tour vous trouverez peut être votre nouveau WallPaper

/y/ - Yaoi -NSFW

Yaoi en jap c’est homo hommes (putain y’a pas de terme pour désigner les gays hommaes et seulement eux ?? c’est chelou … bref … ) . j’y ai foutu les pieds une fois pour voir … c’estun peu comme yuri pas trash la pluprtdu temps mais spa pour ça que ça ne peux pas le devenir …  (je me rappel j’étais tombé sur un dessin des daft punk  en train de s’embrasser … étrange … )

/x/ - Paranormal

12919132219231

Y’a un fantôme dans mon placard et Mulder et scully peuvent plus rien y faire … Tout le domaine de l’étrange et de l’inexpliqué est ici …

Une petite astuce toute con piour pas se faire avoir sur les boards et pas tomber sur des trucs infâmes :

  • Background bleu c’est à priori bon
  • Background Rouge … à tes risques et perils …

Conclusion

Voilà pour les boards … Ah non … Il en manque une … La principale /b/ mais comme je suis gentil je te résérve un article spécifique pour elle ..; y’a trop à en dire …

Pour le moment c’est pas en ligne mais qui sais peut être demain …

Ici bientôt la partie 3…

]]>

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/4chan-27-les-boards/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 55
4Chan 1/7 : 4Chan c’est quoi et on y fait quoi
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/4chan-17-4chan-cest-quoi-et-on-y-fait-quoi
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/4chan-17-4chan-cest-quoi-et-on-y-fait-quoi#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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 41
Thu, 09 Dec 2010 18:46:46 +0000
Yakamo http://yaourtiere.org/?p=109 Kikoo les gens … A la demande générale (enfin 3 personnes en fin de soirée mais c’est pareil pour moi) Je ressuscite ce blog le temps d’un article qui sera consacrés à un des trucs à la fois les plus drôles les plus triste et les plus terrifiant de l’internet (pas forcément dans cet ordre là d’ailleurs :D ) j’ai nommé 4Chan.

Petite tour d’horizon imparfait et hautement personnel d’un des monument du ouaibe …

4 chan

Petit livre rouge de la navigation et de la compréhension des tréfonds de l’internet (Je sais c’est un peu long ça se vendra jamais mais tant pis je suis comme ça moi chui un ouf :D ).

Avant tout un sommaire de ce qui viendra dans ces articles :

Sommaire

1. Intro

2. Les différentes boards (les différentes parties du forum

3. La board /b/

4. Anonymous

5. Les haut faits et action de 4chan Anon et /b/

6. Les personnalités célébres (rééelles ou fictives de /b/)

7. Le lexique

Introduction

Bon on va commencer par un truc Simple 4chan c’est quoi :

Pour faire simple 4 chan est un forum tout ce qu’il y’a de plus normal (avec des sous-forums, des messages des sujets etc.) à quelques exceptions près :

  1. Il n’y a pas d’archivage chaque sous forum (aussi appelé board) peut contenir 15 pages de sujets et c’est tout, pas une de plus. Ainsi si un sujet dépasse la page 15 il disparaît purement et simplement ( 404, on y reviendra ).
  2. L’anonymat Pas besoin de s’inscrire n’importe qui peu poster n’importe comment. A la place du pseudo apparait alors un Anonymous (attention info importante j’en reparlerai).
  3. Le trois découle indirectement des deux autres : Pas ou Quasi pas de modération …
  4. C’est un Image Board C’est-à-dire 1 post 1 image en général ça peut paraitre anodin mais combiné aux autres infos …

Pour faire simple 4 chan et plus particulièrement /b/ c’est un truc anonyme sans historique sans modération … Combiné à internet = Chronique d’une catastrophe annoncée …

Attention il y’a quand même des règles sur 4chan même des plutôt sévères parfois … Je vous conseil de les lires (le mieux c’est après avoir lu mon deuxième chapitre comme ça vous saurez bien de quoi on parle … ) Les règles :

http://www.4chan.org/rules

Crée en 2003 par m00T sur le modèle du bulletin Board Japonais avec une seule board nommée /b/ qui regroupait tout les sujets en mode absolument random.

Le site est hébergé sur 4chan.net mais dès 2004 bouge sur 4chan.Org (si quelqu’un sait pourquoi d’ailleurs je suis preneur :D ).

Le site a à de nombreuses reprise été fermé pour des raisons financières inhérentes aux couts de Bande passante.

Bon voilà pour l’intro … Tout le monde me suis encore ???

Vous pouvez du coup passer à la partie 2: Les boards (ou sous forums)

]]>

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/4chan-17-4chan-cest-quoi-et-on-y-fait-quoi/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 55
Restos du Coeur : 10 repas contre un Article
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/restos-du-coeur-10-repas-contre-un-article
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/restos-du-coeur-10-repas-contre-un-article#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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 41
Thu, 25 Feb 2010 11:21:21 +0000
Yakamo http://yaourtiere.org/?p=88 Hier dans la journée (ou était-ce avant hier je ne sais plus trop ) . Bref cette semaine, un de mes éminent collègue ( aussi grand par l’esprit que petit par la taille et sa propension à voler les slips d’autrui ) m’a annoncé qu’on pouvais gagner 10 repas si j’écrivais un article.Et comme j’ai toujours préféré la nourriture à l’argent …

Bon trêve de plaisanterie soyons sérieux deux minutes les enfants (pour de vrai ). Carrefour et Danone ont lancé une campagne dont le but est en gros: Si toi webmaster tu écris un article pour dire à quel point on est gentil tout plein on file 10 repas aux Restos du cœur.

operation-blog

Du coup me voilà à rédiger en article à la gloire de Carrouf … Hein ? Qui l’eût cru ? Pas eux en tout cas :D

Bref je vais as vous bassiner 107 ans, le truc c’est : si vous avez un blog, faite un article et envoyez un mail à  hub at lanetscouade.com .

Pour les raisons de le faire je vais les piquer au même collègue mais néanmoins ami que tout à l’heure lus certaines de mon cru:

  • Cela aide des personnes
  • Cela ne coûte rien
  • Cela fera les pieds à Danone
  • Cela obligera Carrefour à lâcher de l’argent
  • De toute façon il se passe rien sur le web en ce moment
  • C’est ça ou un énième article sur l’Ipad …
  • Si vous me lisez vous êtes des gens biens … enfin j’espère …
  • Ca m’a pris 10 minutes top chrono, c’est la première fois que vous ferais des repas pour 10 personnes aussi vite  !!!

restos-coeur

]]>

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/restos-du-coeur-10-repas-contre-un-article/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 55
Le Pagerank est mort … Encore … Ou pas … Quoique …
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/le-pagerank-est-mort-encore-ou-pas-ou-si-en-fait-quoique
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/le-pagerank-est-mort-encore-ou-pas-ou-si-en-fait-quoique#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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 41
Fri, 30 Oct 2009 12:51:45 +0000
Yakamo http://yaourtiere.org/?p=80 Youpi le pagerank c’est fini c’est 1ère-position qui l’a dit mais en fait Sebastien nous dit que non pas tant que ça …  De mon coté j’ai bien réfléchi au probléme ..; de longues heures durant. Je me suis rendu compte qu’il n’y avait que deux possibilités :

Soit c’est un Zombie … Soit c’est : CHEV CHELIOS !!!!

Pagerank is still Alive

PS: Pour ceux qui ne connaissent pas Chev Chelios la BA par ici: Crank 2 High Voltage

]]>

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/le-pagerank-est-mort-encore-ou-pas-ou-si-en-fait-quoique/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 55
Et si les services web etaient des vrais gens ???
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/et-si-les-services-web-etaient-des-vrais-gens
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/et-si-les-services-web-etaient-des-vrais-gens#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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 41
Tue, 25 Aug 2009 14:05:57 +0000
Yakamo http://yaourtiere.org/?p=74 C’est vrai ça vu qu’on personifie sans cesse les boites il était bon de leur donner un visage … Et ben c’est fait , je sais pas qui l’a fait mais c’est ultra classe :

Human google twitter youtube myspace yahoo

Human google twitter youtube myspace yahoo

]]>

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/et-si-les-services-web-etaient-des-vrais-gens/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 55
Moi aussi je veux un sticker Mandellia !!!
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/moi-aussi-je-veux-un-sticker-mandellia
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/moi-aussi-je-veux-un-sticker-mandellia#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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 41
Tue, 30 Jun 2009 11:35:12 +0000
Yakamo http://yaourtiere.org/?p=70 Alors oui je sors ce blog de sa torpeur pour faire un article quasiment sans intérêt pour gagner un sticker … Oui je sais c’est mal je suis une sorte de prostituée du marketing. Mais que voulez vous je peux pas m’empêcher…

Bon j’explique en quelque mots. Mandellia pour ceux qui connaissent pas c’est un site sympatoche qui fait dans la déco genre stickers muraux , pour Pc , pour Ipod, des portraits Pop arts , de la déco plus général.. Enfin que des trucs inutiles DONC indispensable.

Et comme ils font des trucs trop de la balle de pingouin explosif ben ils ont pu faire une levée de fond !!! (Argent , argent !!!) cf. Ici.

Et comme c’est des gens gentils il ont décidés d’offrir un Sticker aux 100 premiers qui leur ferai un article pour parler de ça.

Et comme en plus ils ferons un billet de remerciement avec un Backlink dedans même pour ceux qui aiment pas les stickers ça peut valoir le coup … C’est fou la vie non !!!

Et comme vous voulez être gentil vous pouvez aussi aller vous acheter un sticker chez eux ils sont franchement pas mal en plus.

Voili voilo …

]]>

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/moi-aussi-je-veux-un-sticker-mandellia/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 55
Démonstration sur l’intéret des espaces vides dans le design.
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/demonstration-sur-linteret-des-espaces-vides-dans-le-design
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/demonstration-sur-linteret-des-espaces-vides-dans-le-design#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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 41
Wed, 18 Feb 2009 19:56:49 +0000
Yakamo http://yaourtiere.org/?p=47

fille




Pour ceux qui sont pas passez par la page d’accueil et qui ne comprenne pas bien voilà ce qu’ils auraient du lire avant de cliquer sur le lien :

Il est fini le temps ou il fallait remplir chaque pixel d’un site. Ne sous-estimez jamais l’importance des expaces vides, et leur rôle dans l’emphase avec les éléments important de la page.

Une régle de design : Penser simplicité !


Inspiration : www.yousuckatwebsites.com/

]]>

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/demonstration-sur-linteret-des-espaces-vides-dans-le-design/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 55
Les référenceurs sont des cons !
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/les-referenceurs-sont-des-cons
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/les-referenceurs-sont-des-cons#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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 41
Wed, 18 Feb 2009 02:32:06 +0000
Yakamo http://yaourtiere.org/?p=38 Z’avez vu le titre racoleur par excellence. Si j’avais voulu j’aurai pu dire les référenceurs sont des paranos obtus mais ça aurai fait moins de trafic et et pis c’est pas drôle.

Et pourquoi ça donc ???

1.Il a un ego démesuré :

  • « Bien sur que je suis Expert en référencement j’ai 20 ans de métier derrière moi et si je vous dit que texte blanc sur fond blanc c’est ce qui marche faites-le ! »
  • « Si je n’apparais pas dans les résultats c’est impossible que ce soit de ma faute parce que mon site est pourri et sans contenu original. Non c’est une pénalité de Google. »

2.Il est hypocrite:

  • Devant le client « Non madame le cloaking c’est mal et le spam ça marche plus » une fois chez lui «  Bon ça y est j’ai fini le contenu alternatif de mon énième MFA, je vais pouvoir faire poster Natacha sur quelques blog pour faire du jus de liens… »
  • «Les annuaires c’est mort ça sert à rien pour le ref !!  Euh non mais si j’inscris mes sites dedans c’est pas la même chose c’est juste que c’est pour les utilisateurs que ça rapporte … »
  • « Non les liens ça sert à rien seul le contenu prévaut, oui bon OK je bosse sur un site qui possédait déjà 200000 liens au début de la presta mais c’est pas pareil »

3.Il est jaloux :

  • «  Pitaing tous des cons ces blogueurs, savent pas optimisé un site il font du traff sur des requêtes déloyales et en plus c’est trop naze le linking avec la blogroll » mais il aimerait bien que son blog à lui fassent autant de trafic.
  • « Si mon concurrent m’est passé devant c’est parce qu’il triche pas parce que j’ai fait de la zouille… »

4.C’est un grand parano :

  • « Oh mon dieu il a mis son site en noarchive il fait surement du cloaking pour essayer de nous rouler dans la farine. » Et le pire c’est que je l’ai pas inventé celui-là !!!
  • «Oh pitaing, Google a rajouté un carré de 4 pixels en haut de ses résultats est ce que mon site va être pénalisé.»

5.Et puis en vrac :

  • Il est même plus capable de dire quel est exactement son métier . Et d’ailleurs les gens comprennent rarement quand il essaie d’expliquer.
  • Il passe son temps à casser du sucre sur le dos de google mais il est bien content de choper les adsenses à la fin du mois.
  • Il pense que le seul moyen de se faire de l’argent sur le web c’est les moteurs de recherche , le reste c’est de la gnognotte

Donc comme je le disais : Les référenceurs sont des cons

Et moi le premier !!!.

MAIS car il y’a un MAIS de taille. Toi, client potentiel si tu es gentil avec lui il pourra te permettre de faire péter des records à ton chiffre d’affaire.

Bien entendu ce billet est un pur acte de mauvaise foi, mais néanmoins tiré de choses vues ou entendu lors de mes pérégrinations dans ce milieu étrange. Vous pouvez commencer à jeter les petits cailloux pointus.

]]>

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/les-referenceurs-sont-des-cons/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 55
The hunt for gollum : Le fan Movie le plus classe du monde
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/the-hunt-for-gollum-le-fan-movie-le-plus-classe-du-monde
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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/the-hunt-for-gollum-le-fan-movie-le-plus-classe-du-monde#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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/functions.php on line 41
Tue, 17 Feb 2009 16:27:26 +0000
Yakamo http://yaourtiere.org/?p=35 Bon je sais j’écris pas souvent … mais j’ai pleins de trucs en cours donc les articles sérieux devraient arriver bientôt (enfin j’espère … ).

Donc sans plus m’excuser, on va parler d’un fan-movie (film fait par les fans en français) complètement hallucinant !!!

Le pitch sur le site officiel nous explique que le film est complétement indépendant de ce qu’a déjà fait Peter Jackson (Le Seigneur des Anneaux) ou de ce qu’il va faire (Bilbo le Hobbit). Il raconte la légende d’Isildur “le plus grand rodeur et voyageur des terres du milieu” et de sa traque de Gollum. La créature doit être trouvée afin de connaitre la vérité à propos de l’anneau

Le film d’une durée de 40 minutes (environ) sera disponible gratuitement au téléchargement le 3 mai 2009. Il faut savoir que ce film à était réalisé pour seulement 3000£ ce qui est proprment hallucinant quand on voit la qualité du trailer !!!


THE HUNT FOR GOLLUM - FULL Trailer 1 from Independent Online Cinema on Vimeo.

Est ce que je suis le seul à avoir bavé ???

]]>

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 107

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 'CEST/2.0/DST' instead in /homepages/17/d244771740/htdocs/wp-includes/link-template.php on line 132
http://yaourtiere.org/the-hunt-for-gollum-le-fan-movie-le-plus-classe-du-monde/feed