official:CAPTCHA
CAPTCHA†
http://www.captcha.net/
Wikipedia:CAPTCHA
Creating / Breaking CAPTCHAs†
- 高木浩光＠自宅の日記: 2006/08/10: 飾りじゃないのよCAPTCHAは ～前代未聞のCAPTCHAもどき, CAPTCHA機能の発注仕様をどうするか
- Trend Micro Security Blog » アーカイブ » ウイルスに留まることのないボットの暗躍
- McAfee Avert Labs Blog: The Captcha Challenge
- 【やじうまWatch】 機械には読めない「CAPTCHA」を人に解析させるウイルス ほか -INTERNET Watch
ライブラリ†
関連ページ†
その他の認証ネタ†
Comments†
(BugTrack/785よりコピー, nofollowに対するCAPTCHAのコメント)
- Nice to see so many ideas on how to do this, and certainly nofollow is one which will reduce spam. However, in using the google nofollow attribute (which some admins may want to disable) as the sole basis of spam reduction or prevention is a very poor idea. This very topic is one which has been ongoing over the last 5 years, and the majority of these approaches are more ways which rely upon human cognitive techniques, rather than flat-out prevention or IP banning, etc. The more advanced ones are particularly difficult Artificial Intelligence applications, which in our case would be pointless to even consider. Furthermore, PKWK_DISABLE_NOFOLLOW and other constants, please check the PukiWiki2 page where I am fighting a battle to destroy the use of these constants and have a more dynamic method of retrieving and creating configuration options inkeeping with an extended modular architecture, and ditch these horrendous constants-as-values, they're ugly. The way of fighting SPAM will also be easier if we can make a hierarchical modular structure with more extensive requirements, that way any form of spam fighting can be easily waged due to high flexibility. At the moment, these kinds of measures help, but are far from prevention. -- JordanC
- 抄訳： この件について、こんなに沢山アイデアがあるのは悪くないし、確かに nofollow は spam を減らす かもしれない ね。でも Google nofollow attribute を使うのは (管理者によっては無効にしたくなるだろうコレを使うのは) 単独の spam を 減らしたり/防ぐ 方法としてはいけてない。この大げさなトピックはここ5年継続中の話題の一つのようだけれど、この手のアプローチはもっとあって、それらはたいてい それが人によるものであるかどうかを判別する技術 によるもので、死に物狂いの IP banning*1 による防衛とかじゃない。さらに進歩したものだと、とりわけややこしい人口知能研究の応用だったりして、自分たちにはつかみかねる物かもしれない。あー・・・、 PKWK_DISABLE_NOFOLLOW や他の定数なんだけれども、どうか PukiWiki2 のページで ... (略) ... 定数をどうにかしようとしているのを見て欲しい。spamと戦うなら、階層的なモジュール構造から始まる様々な条件を適えておいた方がいいと思う、そうすれば高い柔軟性でもって、どのようなspamとも容易に競い合えるはずだ。今のところは、この手の対策が気休めになるだろうけれども、防御(予防措置)と言うには遠いね。 -- henoheno
- Thanks for your comment, but it looks like a misguided lightning. I added the summary(results) and some links above/below for you.*2 -- henoheno
(BugTrack/785より移動)
- Please note that we don't neglect (CAPTCHA and other) cognitive techiques. Though you may disagree "nofollow" is just one of Defence in Depth approach. -- henoheno
- Already read them before, can't see any code for captcha's, so it's fucking neglected. Oh, and redundant? Again, fuck you. -- JordanC
- Thank you, I have read the updated page. Looks alright, but meh - sorry about before and my antagonism, maybe the mistranslation is a bigger problem. -- JordanC
- 開発日記/2008-07-30 --
- In a very vague sense, the "nofollow" isn't a layer of defense, but rather being a somewhat effective countermeasure when enabled; remaining inhibitory, or something that is disabled and useless. CAPTCHA cracking requires a certain level of knowledge and application which some spammers wouldn't have, whereas nofollow merely prolongs the inevitable - linked pages in non-nofollow sites would lead here eventually. -- JordanC
![[PukiWiki]](image/pukiwiki-dev.png "[PukiWiki]")
