Archives du mot-clé spam

La SNCF se met-elle au spam ?

C’était le 22 septembre 2006, donc pas tout jeune. Mais ça ne change rien à l’affaire.

Spam de la SNCF

flattr this!

Viadeo et LinkedIn : un spammeur et un emploi

Jérôme Lauriol nous signale les inquiétantes pratiques de Viadeo : les campagnes de spam initiées par la direction de Viadeo ainsi que son message a été censuré sans aucune explication.

En revanche et à l’inverse, je tiens à remercier LinkedIn, grâce auquel j’ai décroché un emploi très intéressant. Je n’en dis pas plus pour le moment, sachez juste que j’agirais justement dans le domaine que je cherchais, à savoir l’accessibilité et la sémantique Web, et que je travaillerais à faire progresser la cause d’un Web meilleur, parce que ce qui fait courir Tristan me fait courir aussi. Merci à tous ceux qui m’ont proposé des pistes et des postes ; je ne vous oublie pas.

Je l’ai déjà dit, mais encore merci !

flattr this!

Some Devon Young’s great posts

Devon Young’s tech blog is gone (Been 86’d—surely a phrase, but I don’t know its meaning). This is sad, because there was a lot of interesting things there.

Now, the good news: thank to Opera’s fantastic caching system, I can still read it: Opera does not refresh a page when re-opening a session and this is GREAT (he is the only to do that, as far as I know). This is the second time that this feature helps me—it even doesn’t refresh if you close a tab and unclose it :-).

Now, thanks to Opera and Devon Young’s approval, I decided to post some posts.


Remove 75% of the spam on WordPress 2.1

original post

[…] The spambots weren’t using the form to post anything, they were just directly accessing the wp-comments-post.php file. Which surprised me. It didn’t surprise me that they were doing it. It surprised me that WordPress was allowing that. So I realized I had to create a small change in the script, that should’ve already been coded in by the WordPress coders before release. So at the start of the file, before any of the code that’s already there, I added this line:

if(strstr($_SERVER['HTTP_REFERER'],"devonyoung.com")) {

Then after all the code, I added these 4 lines:

} else { 	echo "You tried to bypass the form."; }

These 4 lines of code, reduced spam by about 75%. Yet, some spambots are somehow still posting comments. So I checked really quick and discovered that the ones still getting their posts through, aren’t using the comment form or the wp-comments-post.php. Huh? Now that surprises me. Anyone know how they can manage that? I know a little about WordPress, but not enough to know how this works. Likely, the spambots are exploiting a security hole or a bug in the system. I’m using WordPress 2.1.

Spamproof email address, with CSS

I think this is a case of parallel invention, since Devon Young doesn’t mention any inspiration, but this had already been done by the Polish Literary Moose (interview).

Anyway, here it goes:

p a:before { 	content: "soy"; } p a:after { 	content: "devonyoung.com"; }

This address is selectable with Opera (and Opera only; others will use their eyes). It is the only one I know to do this. That might be worth including in any Opera evangelism.

A Google limitation

I copy the whole of it, that’s better.

As if I wasn’t having enough problem with their Feedfetcher bot. Apparently Google thinks www.devonyoung.com is equivalent to devonyoung.com, because it applied my www’s robots.txt to my entire domain.

I used Google’s automatic URL removal system to remove all references to my outdated www. subdomain from the Google database.

I clicked the link titled “Remove pages, subdirectories or images using a robots.txt file” and typed http://www.devonyoung.com/robots.txt in the appropriate textbox. That robots.txt has disallow: / in it, so no crawlers will bother with the defunct subdomain. Knowing that robots.txt lists what you want a spider to ignore, I expected that what was listed, would be what would be removed. What else could it mean?

This morning, I wake up to find that my entire devonyoung.com domain is missing from Google. Try it, search for it. It’s gone. You can’t even google my name to get it. So apparently Google cannot distinguish between a www. and the main domain itself.

That was irritating, but I thought that fixing this would be relatively easy. I just go in again and type http://devonyoung.com/robots.txt (without www.) in the appropriate textbox, right? No. This caused Google to give me a notice that every single thing at my main domain will further be gone (again?), and not just the things I list in the robots.txt as ignorable.

What makes this even more painful and annoying is this note at the URL Removal System:

all pages submitted via the automatic URL removal system will be removed from the Google index temporarily for six months

This is more than fairly irritating. For 6 months, my entire website won’t be listed in Google. I only wanted the outdated and defunct stuff removed, and I get burned.

Oh, one more thought on this subject. They never confirmed with me that I had any authority to delete all references to the domain from their database. That just sounds like a huge security risk. I imagine I could sign up using an anonymous hotmail address and remove all references to microsoft domains from Google’s database. I bet Google would hear about that.

Sorry for the rant, but I thought you might all want to know about this for SEO reasons.

NewsFire limitation

I used it for a while (now I use NetnewsWire). In case you don’t know, it is a cool-looking RSS reader for OS X (it is made by David Watanabe. Nuff said).

Bottom line: NewsFire does not respect 301 notification (301 status code means file moved, so stop looking for it here. It is there now.).

Oh, by the way: Google’s RSS bot (Feedfetcher) don’t give a shit neither. Yep, Google sucks on this, he ignores my Redirect permanent.

Devon has a nice name for these rude bots: Deaf user agents.

flattr this!

Non aux lettres en chaîne (modèle)

Initialement publié le 04 février 2005 à 07:31:46

Modèle de message à ceux qui m’envoient des lettres en chaîne. Oui, je sais, vous pouvez me rétorquer que c’est de l’énergie gaspillée. Que voulez-vous, trop bon, trop con…

Bookmarkez cette page et copiez-collez le texte en réponse à vos lettres en chaîne. Vous pouvez aussi mémoriser l’adresse : david.latapie.name/blog/chain-letters-no-fr/#modele.

Bonjour,

L’un d’entre vous m’a récemment envoyé une lettre en chaîne (chain letter). Les autres étaient inclus dans la chaîne, c’est pourquoi je vous réponds également (en copie invisible).

Je vous prierais de bien vouloir lire les deux liens suivants.

Merci et bonne continuation,

flattr this!

Idée reçue sur l’origine du spam

J’entends parfois des gens suggérer que, pour lutter contre le spam, un bon premier rempart est de bloquer des pays entiers, au prétexte que de toute manière, il y a peu de chances que des vous ayez des turkmènes dans votre entourage.

Ça ne marche pas, et pour une raison très simple : les premiers spammeurs au monde sont les États-Unis. Et de loin.

flattr this!

Redirect from IP

Whoohoo, ça y est, ça marche !

Ils écrivent mal, mais je remercie quand même grandement le club informatique de Pouliguen pour m’avoir donné la solution pour mon « redirect from IP » :

ErrorDocument 403 /formulaire.php deny from xxx.xxx.xxx.xxx deny from yyy.yyy.yyy.yyy deny from zzz.zzz.zzz.zzz … <Files formulaire.php> allow from all </Files>

Désormais, les personnes bloquées par mon filtrage IP auront une chance de me signaler qu’elles y sont pour rien (adresses IP dynamiques, personnes qui téléchargent sans se méfier…). La majorité des innocents qui auraient bien voulu voir mes pages n’en feront rien, mais là, ce n’est plus (trop) mon problème.

Si vous voulez savoir comment ça fonctionne (par exemple pour le faire chez vous mais que vous n’avez pas tout compris avec juste l’exemple), continuez à lire.

Lire la suite

flattr this!

Humour involontaire d’un spammeur

L’homophonie entre escrow (qui veut dire séquestre) et escroc en français rend le texte du spam assez cocasse…

----- Forwarded message from Sheldon Katz <215burnard@yahoo.co.uk> ----- From: Sheldon Katz <215burnard@yahoo.co.uk> To: debian-devel-french@lists.debian.org Subject: Re: Job request Date: Tue, 27 Jun 2006 17:07:27 -0700 Hello Debian-devel-french.! We are an international escrow company. Now we are looking for a new partners. [… snip spam] ----- End forwarded message -----

merci Laura

flattr this!