User talk:SelimLakhdar/sandbox
relecture de l'article
editForme
editRésumé Introductif
edit- "while reaming" : "while remaining"
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "relies on the fact " : un peu lourd, non?
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- " if a bot succeeded" : toujours au présent
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "so theoretically if a bot succeeded on the test it could be used for solving AI problems" : "so theoretically," ... reformuler en supprimant le "if"? Tjrs au présent (T.A.P.)
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "access took priority to security" : pas anglais (et TAP)
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
History and evolution
edit- "which consists on trying" : "which consists in trying"
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "growth of Internet users" : growth of the number of users ? How to say ?
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- " between normal human actions, and automated actions through bots" : what is opposed to here? Is "normal" compulsory in the end?
- "The first attempt led to different attacks to break the system which lights up new ways" : led(past)#lights up(present). + light up : rather trigger?
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "not a easy" : "not an easy"
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "challenge have to " : has
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- " for human to pass" : humans
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "and hard as" : "as hard"
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "was introduced like, " : "were introduced, like"
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "puzzle based CAPTCHA" : ", the puzzle based CAPTCHA"
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "new HIPs systems" : "new HIP systems"
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "was using" : "is using"?
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "if hackers could break it" : "if hackers could not break it"?
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "1024 integer " : "1024 integers"
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
Usage and utility
edit- "HIPs systems" : "HIP systems", rather?
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "Generally they are" : "They are generally"
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- is HIPs acronym usable? Not seen in the Internet
- Yes, i reused it from somes articles.
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "control the access" : rather "control access"
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "this scheme works also to detect" : to detect what?
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "usage" : usages
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "crawler." : "crawlers."
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "Interactions of social networks: tracking online bots." : maybe reversing the order "tracking online bots (in the interactions of social networks)" to keep listing gerundive forms (-ing) beginning the list?
- Done !
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
- "Specifically, in the TLS protocol to counter the MITM attack." : lacks the reminder of what is specifically, reformulation needed.
- There are wiki links.
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
Usability/accessibility
edit- "trade off" : trade-off
- "between the accessibility and the strength" : "between accessibility and strength"
- "The HIP have to" : "The HIP has to"
- "They state" : who ? (authors presumably) --> to "anonymize"
- Done, suppress they state
- Nowitsover (talk) 13:10, 28 January 2019 (UTC)
- "or a success rate" : "or have success rate"
- "rate of .01%" : is it a correct way of displaying a rate? I couldn't find any like this in the Internet
- Yes, it's 0.1%
- Nowitsover (talk) 13:10, 28 January 2019 (UTC)
- "human recognition filed" : " human recognition field"
- "analysis and understand" : "analyses and understands"
- "it don't" : "it doesn't"
- "leaded" : "led"
- "is the greatest security related" : "is the greatest security-related"
- "security related problems" : "security related problem"
- "for user with disabilities" : "for users with disabilities"
- "audio based" : seems "audio-based" is more correct
Security
edit- "to defeat computer bots from bypassing" : "to prevent computer bots from bypassing"
- "bot-attacks" : "bot attacks"
- "CAPTCHA is usable" : "CAPTCHA be usable"
- "bot-attacks" : ditto
AI usage
edit- "a way to advance in that filed" : [field] "a way to progress in that field"?
- Yes, you are right.
- Nowitsover (talk) 13:59, 28 January 2019 (UTC)
- "But in another hand" : usually used after a "in one hand" first sentence
- Yes, you are right, i just suppress "in another hand".
- 13:59, 28 January 2019 (UTC)
- "well oriented" : "well-oriented"
- "This came from the segmentation problem, which relies on breaking the interlacing between words, but this seems to be broken" : difficult to understand (this, which, this). A problem ("segmentation problem") cannot "rely" on something.
- The distorted text came from the segmentation problem, the challenge for AI is to breaking the interlacing between words, but this seems to be broken.
- Is it better ?
- Nowitsover (talk) 13:59, 28 January 2019 (UTC)
Segmentation resistance
edit- "we" : third person only
- I don't find any we is this part
- Nowitsover (talk) 14:04, 28 January 2019 (UTC)
- "break a text-based CAPTCHA" : rather 'hack' or 'bypass' than 'break', no?
- "More we combine effects for designing a strong HIP more the HIP is secured" : [the more ... the more] --> "The more effects for designing a strong HIP are combined, the more the HIP is secured"
Challenge generation
edit- "many instance" : "many instances"
- "an aspect on interest" : "an aspect of interest"
Public Sources
edit- "Beyond the several rules to design" : "Beyond the preceding rules to design"
- "the more effective" : "the most effective"
- "CAPTCHA systems which relies" : "CAPTCHA systems which rely"
- "on private database or algorithms" : "on private databases or algorithms"
- "This risk of an" : lacks a verb : "This" ... (emphases, focuses,) raises the ... "risk of an"
- "trying to reverse engineering" : improper use : "trying to reverse engineer" or " trying to use/do reverse engineering"
- "CAPTCHA systems which rely on private databases or algorithms to generate their challenges are prohibited. And this rise a risk of an adversary generating all possible tests and using a hash function to look up the answer in a pre-computed database or he try to do reverse engineering." is this good for you ?
- Nowitsover (talk) 14:21, 28 January 2019 (UTC)
--G7tiiR (talk) 22:24, 21 January 2019 (UTC)
CAPTCHAs
edit- "It depends on the gap" : "It relies on the gap"?
- "many other implementation" : "many other implementations"
- "Many fields was studied" : "Many fields were studied"
- "find body parts" : "body parts finding" to keep the gerundive listing?
- Yes, its sounds better
- Nowitsover (talk) 14:34, 28 January 2019 (UTC)
- "deciding nudity" : also reverse in "nudity deciding", though it's a quote, no?
- Yes, it is
- Nowitsover (talk) 14:34, 28 January 2019 (UTC)
- "in different categories;" : announces a list : rather with a ':' in the end, and, better to use lists (*), rather than sections. — Preceding unsigned comment added by 81.199.32.90 (talk) 12:16, 22 January 2019 (UTC)
- Is it better now ?
- Nowitsover (talk) 14:34, 28 January 2019 (UTC)
Text-Based CAPTCHA
edit- "It depends on" : "it relies on"
Image-Based CAPTCHA
edit- "It depends on" : "it relies on" (and so, modifying the 'relies on' just after)
- "difficulty for computers" : "difficulty for bots"?
- "some aspect" : "some aspects"
Non-Visual CAPTCHA
edit- "Those CAPTCHAs was" : "Those CAPTCHAs were"
- "sonor recognition" : "sound recognition"
Semantic CAPTCHA
edit- "to attacks using" : "to attack using" is convenient also
Audio CAPTCHA
edit- "sonor deformation" : ditto
Others approaches
edit- "those different technique" : "those different techniques"
--G7tiiR (talk) 13:08, 22 January 2019 (UTC)
Attacks on HIPs
edit- "hackers/researcher" : "hackers/researchers"
- "We can cite" : :-D
- "project PWNtcha" : "PWNtcha project"
- "" PWNtcha stands for "Pretend We’re Not a Turing Computer but a Human Antagonist", as well as PWN capTCHAs. This project’s goal is to demonstrate the inefficiency of many captcha implementations. " : isn't that quotation too long? (and it's pure quotation :(
OCR
edit- "and detect letters" : "and detect letters."
- "we can" : no, we can't (use 'we')
Machine learning
edit- "It consist on" : "It consists in"
- "pure recognition tasks which" : "pure recognition tasks that"
- "machine learning based" : "machine learning-based" ?
- "text distortion based" : "text distortion-based" ? (even found text-distortion-based : a rule to hyphen words when 'adjectivization' is used?)
Stealing cycles (redirection)
edit- "One of possible attack" : "One of possible attacks"
- "on a CAPTCHA system, it's to" : "on a CAPTCHA system is to"
Fond
editRésumé Introductif
edit- "Designing an accessible HIP is a new major concern" : why? (argument esseulé)
-- G7tiiR (talk) 14:54, 21 January 2019 (UTC)
- "It's related to the trade off between security and accessibility"
SelimLakhdar (talk) 09:34, 28 January 2019 (UTC)
Challenge generation
edit--
- only two lines, can you densify a bit?
- --G7tiiR (talk) 23:11, 29 January 2019 (UTC)
CAPTCHAs
edit- "was trying to achieve some goals." : which ones? — Preceding unsigned comment added by 81.199.32.90 (talk) 12:08, 22 January 2019 (UTC)
- Done !
SelimLakhdar (talk) 15:31, 29 January 2019 (UTC)
Others approaches
edit- "combining those different technique to come with a hybrid one." : what is a hybrid technique? Isn't it purely a "combination of techniques"? And why are these techniques "to come"?
--G7tiiR (talk) 13:09, 22 January 2019 (UTC)
Stealing cycles (redirection)
edit--
- only one lines, can you also densify a bit?
- --G7tiiR (talk) 23:11, 29 January 2019 (UTC)
Deuxième relecture de l'article
editintro
edit- Second paragraph : "This test", the reference is not clear. The previous sentence doesn't speak about an only test.
- Done !
- Second paragraph : "This test ... for a bot", this sentence is redundant compared to the previous. Maybe maintain only the second part (after ',').
- Done !
- The paragraphs 3, 4 and 5 are on the same subject so they can be regroup. Avoid isolated sentences.
- You can add the wiki reference for "bot".
- Done !
History and evolution
edit- The paragraphs 2 and 3 can be regroup.
- 5th paragraph : In the last sentence, modify the second ',' to "and"
- The paragraphs 4 and 5 can be regroup.
Usage and utility
edit- You can add the wiki reference for "front-end", "back-end" and "layer"
- Done !
- Modify the ';' to ':' before the ref 11.
- Done !
- In last sentence of this section, put the point before ref 13.
- Done !
Usability/accessibility
edit- Remove the '.' after ref 16.
- Done !
- First paragraph : the 3th sentence is redundant compared to the previous.
- Paragraph 2 and 3 : Specify when studies were conducted.
- Done !
- The paragraphs 3 and 4 can be regroup.
- Done !
Security
edit- Specify who are Basso and al.
- Done ! link in the ref
- The sentence with "0.01%" is always in the previous section.
AI usage
edit- Remove the '.' after the ref 33.
- Done !
- Move the '.' after ref 35 before ref 34.
- Done !
Segmentation resistance
edit- Regroup the two paragraphs (Avoid isolated sentences).
- Done !
Challenge generation
edit- Regroup the two paragraphs (Avoid isolated sentences).
- Done !
Public Sources
edit- You can add the wiki reference for "database".
- Done !
CAPTCHAs
edit- The paragraphs 2 and 3 can be regroup.
- Done !
- Put the '.' before the ref 52.
- Done !
- You can add the wiki reference for "noise" (in "Text-Based CAPTCHA" point)
- I didn't find a related article
- They are no references for each item of the list, is it normal ?
- Done !
Attacks on HIP
edit- Remove the '.' after the ref 55
- Done !
- Before the ref56, modify <<. ">> to <<".>>
- We normally use ""
OCR
edit- You can add the wiki reference for "binarization".
- Done !
Machine learning
edit- Specify who are Bursztein and al.
- Try to regroup the paragraphs.
- Done !
Stealing cycles
edit- Use the full word "pornographic" not "porn"
- Done !
ref et biblio
edit- Remove the parenthesis to the references.
- The references are not linked to the biblio, here an example : [1]
- For the references to a website or a pdf document for example, it's better to use a External Link section. Here an example :
- "Les smart contracts : révolution sociétale ou nouvelle boîte de Pandore ? Regard comparatiste" (PDF). tendancedroit.fr (in French). Bruno ANCEL. extLien_1.
- We had problems with our template, i don't know why it doesn't work :(
MedhiB (talk) 00:29, 30 January 2019 (UTC) SelimLakhdar (talk) 10:15, 30 January 2019 (UTC)