User talk:AalekhN/GSoC proposal 2014

From MediaWiki.org
Jump to navigation Jump to search

Asirra[edit]

Hi AalekhN, isn't this feature basically the same as what Asirra is doing with cats and dogs? See Extension:Asirra, and a real example running in MediaWiki here.--Qgil (talk) 23:06, 6 March 2014 (UTC)

--Hi Qgil, What i mentioned in this proposal is different from Asirra,in two ways:

ConfirmEdit / node[edit]

Two Questions:

  • Are you proposing to extend or integrate with the existing ConfirmEdit extension, or would this be a competing extension?
  • You mentioned node.js as a part of your development environment-- are you planning to do part of this in javascript instead of PHP? Having the captchas require other languages besides php has been an issue with fancy captcha (generation is in python), and I would caution against it unless there is a really compelling reason for it.

CSteipp (talk) 01:13, 7 March 2014 (UTC)

--Hi CSteipp,I plan to make it as an integration to ConfirmEdit extension....if required we can also make it as an separate extenstion.

Thanks. Please just integrate with ConfirmEdit-- a separate extension will make things more difficult in the future, which is why I was concerned about it. It sounds like you're on a good track. Good luck. — Preceding unsigned comment added by Csteipp (talkcontribs)
Also, when you consider your proposal complete and you've settled on a specific idea, please move it to the appropriate title as a subpage of CAPTCHA (per instructions). --Nemo 13:08, 8 March 2014 (UTC)

Watch the complexity[edit]

Just reading the captcha question gave me a headache... I'm not a designer so I'm unable to comment on specific ideas; but, again, you'll need some scientific research/usability testing to support whatever approach you choose. --Nemo 17:31, 13 March 2014 (UTC)

-- Thank You,I got similar advice from various community members and then I concluded to make the captcha question mentoined in approach 1 more user friendly ,I therefore have changed my approach and made it more user friendly --aalekhN 11:28, 14 March 2014 (UTC)

Layout[edit]

21.20 < aalekhN1> Nemo_bis: any suggestions regarding new layout of proposal?

Layout is certainly not the main problem. --Nemo 20:34, 19 March 2014 (UTC)

Mentors[edit]

Please, as I told you:

  • ask on the related bugzilla reports who's interested in the project and in mentoring it;
  • ask Siebrand if he's available to be the primary mentor and/or he prefers/recommends you (based on your skills etc.) to apply for another project he's mentoring. --Nemo 20:36, 19 March 2014 (UTC)
--Yes thank you, I did mailed to Siebrand yesterday itself and have evidently just posted on bugzilla report. AalekhN 03:30PM, 20 March 2014 (UTC)

Unrealistic without a data source[edit]

This proposal concentrates on the easy part of the image-recognition CAPTCHA problem (finding tasks where humans drastically outperform machines) and completely ignores the hard part (how to create images + verification data in a way that is not exploitable to spambots). You need a very large set of CAPTCHAs (hundreds of thousands, ideally), otherwise an attacker can just map your CAPTCHA database. If you use a public image repository (such as Commons) or a public data source (such as Commons categories), chances are an attacker can match the CAPTCHA to the source and figure out the solution from that.

Asirra works because Microsoft has an agreement with petfinder.com who provide them with an endless stream of new animal photos and manually created classifications; the classifications are initially not public and only available to the CAPTCHA software. How do you intend to obtain a similarly robust data source? As far as I can see, this would be the real challange in the project, not the choice of image transformation.

I suppose one could try the reCaptcha way and create some sort of bootstrap data set, then show people a mix of captchas with known and unknown solutions, and use the known ones for verification and the unknown ones for generating more data. But that is not easy and should get significant focus in the project if you want a CAPTCHA system which is of any practical use at the end. --Tgr (WMF) (talk) 01:42, 20 March 2014 (UTC)

--First of all thank you for raising this question,now to solve the problem of being recognized by bots, i have opted for Graphical Modification of the images and to support my argument i have gone through various research papers and testing ,one such test has been made on this image https://www.mediawiki.org/wiki/File:Cat123789_(1).gif by applying photobooth and pencil sketch effect, and to my surprise the image was not recognizable even on Google images and tin eye api's.This argument is supported in this research paper:http://web.media.mit.edu/~mehoque/Publications/Captcha-CameraReady.pdf . Also there are few approaches discussed,one of them on Google Research Blog as mentioned here:http://googleresearch.blogspot.in/2009/04/socially-adjusted-captchas.html which support secure captcha. Also in addition providing questions like Selecting Odd one out leaves little scope for the bots to be identified.AalekhN(talk) 03:24 , 20 March 2014 (UTC)
Another approach that can be worth trying is to play a little (or a lot) with categories. For example, don't rely directly on basic categories but on more general meta-categories. For example, I'll put three images and their categories which are easy for humans to find the "different one" but hard for bots to solve (I guess):

––Pginer (talk) 15:29, 26 March 2014 (UTC)

A few questions/remarks[edit]

  • What specifically will be the data (image) source? Wikidata or did you mean Commons?
  • I don't quite understand how the image indexing system would work. What does "downrate given image's in option" mean?
  • Have you thought about implementing it for mobile too? It shouldn't be much more work.
  • Try to clean the proposal up a little bit. It will read much better with proper punctuation (in particular with spaces after, not before a period).

Juliusz Gonera (talk) 00:48, 29 March 2014 (UTC)

--Right from the first point:
  • --Data source (images) will be fetched from Wikidata, although the images we will fetch will be present in Wikimedia Commons database.
Advantage:Wikidata can help us with metadata if needed to for making the categories more meaningful.
  • --Let me explain you about image indexing System with the help of an example: Suppose we provide this image:
https://commons.wikimedia.org/wiki/File:Cats_eye.jpg as one of the option to the captcha question.Now since this
image is not easily recognizable as image of cat the user will reload the Captcha, on reload the images provided in the option will
listed in the database of wiki for depreciated to be used again category, After several reloads of the given image combination
with different images this image will be listed in database as not to be used again. Hence this overtime improving
system would provide users with image options that are easily recognizable to the user.
  • --Yes i have planned to extend the captcha to mobile, details about the implementation is given here:
here:https://www.mediawiki.org/wiki/User:AalekhN/notes#Captcha_for_Mobile_Device
  • --Sorry for the problem in readability I am working on it.--AalekhN(talk)
1. Following the cat example I'd like to know how the data could be fetched exactly. Have you investigated what APIs could be used for that? I assume we'd somehow like to fetch the "cat" entry from Wikidata and then find images for that in Commons. Do all the APIs required for that already exist?
2. Regarding captcha on mobile, I'm glad you put some thought into it. Instead of using a jQuery lightbox plugin, a more appropriate approach would be to use the Overlay class from MobileFrontend. Just mentioning it, don't worry about it now.
3. I'm glad you're working on readability of your proposal. Clear communication is a really important factor.
Juliusz Gonera (talk) 00:48, 29 March 2014 (UTC)
--- Just an update for Community members after discussion with the mentor the use of Wiki Commons Api has been concluded AalekhN (talk) 15:05, 2 April 2014 (UTC)