edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: commandline@yahoogroups.com
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] wikipedia
Date: Fri, 14 Feb 2014 05:40:44 -0800	[thread overview]
Message-ID: <8738jldd7n.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140114052756.eklhad@comcast.net> (Karl Dahlke's message of "Fri, 14 Feb 2014 05:27:56 -0500")

> I have three sources to confirm credibility: it's packaging in debian, ubuntu,
> and free bsd.

It's also packaged on Gentoo, and it is available from the 
Arch User Repository (a collection of community-supplied build scripts)
on Arch Linux.
So if you count Arch, that makes 4 Linux distros and a BSD.

> And even if I did all that I still have to get past the last captcha.

Well sometimes I get around them using the following techniques.
Unbrowse the page.  Find the form.  Find the <img> tag for the captcha.
Send the image to a sighted friend.
Also, are they using recaptcha?  It is ubiquitous, so they probably are.
If they are, then there's an audio captcha.
Recaptcha is very JS-intensive, and by default it isn't usable.  They do
have a non-JS option though.  It's inside a <noscript> tag on the page
containing the form.  Unfortunately, edbrowse discards text in
<noscript></noscript>.  So you'll have to edit the page and remove the
tags to find it.  Once you have the JS-free recaptcha html, it's fairly
straightforward to get an audio captcha from them and fill it out.
Technically straightforward.  In the past, their audio captchas were
notoriously hard to understand.  For instance, when we deleted our
Facebook accounts last year, I had to listen to between 30 and 50 of
them before I could find one that I could understand.  Google owns
recaptcha, and I think they've fixed this by now.  They got a lot of bad
press last summer, because a blindness-related petition on
whitehouse.gov was protected by their inscrutable audio captcha, and
therefore inaccessible to most of the blind!  I solved it, but I have good
hearing and lots of patience.

-- Chris

  reply	other threads:[~2014-02-14 13:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 10:27 Karl Dahlke
2014-02-14 13:40 ` Chris Brannon [this message]
2014-02-14 20:17   ` [Edbrowse-dev] [commandline] wikipedia Robert Ransom
2018-07-13 13:58 [edbrowse-dev] wikipedia, if anybody cares, if it really matters Karl Dahlke
2018-07-17  1:44 ` [edbrowse-dev] wikipedia Kevin Carhart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8738jldd7n.fsf@mushroom.PK5001Z \
    --to=chris@the-brannons.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=commandline@yahoogroups.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).