From: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: Chuck Hallenbeck <chuckhallenbeck@gmail.com>,
Karl Dahlke <eklhad@comcast.net>,
edbrowse-dev@lists.the-brannons.com
Subject: Re: [edbrowse-dev] fastmail
Date: Fri, 20 Jul 2018 20:39:10 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.21.99.1807202020450.20362@workshop> (raw)
In-Reply-To: <20180720234438.GA1417@nautica>
Hi Dominique,
> Chuck Hallenbeck wrote on Fri, Jul 20, 2018:
>> My daughter with her Windows laptop created an account for me on
>> fastmail.com successfully. The kapcha took a form I have never seen
>> before. Instead of an image to copy to an input field, it took the
>> form of a series of statements to click on, each of them reading:
>>
>> I am not a robot
>
> These are google reCAPTCHA, most people only see this box... As an
> annoying user I get various image challenges (for example displays a
> grid of images and pick the ones with cars, street signs, store fronts
> etc)
Amazing. I had no idea.
> There also are audio challenges which aren't easy either, it's a track
> full of white noise and someone speaking difficult words with a strong
> accent -- I just tried two and I can't say I understood what they said,
Me too. I often fail to hear them correctly.
> so maybe I'm a robot?
I doubt it. Robots are not that helpful.
>> On my linux desktop, I entered:
>>
>> edbrowse www.fastmail.net
That's a typo. I entered www.fastmail.com, actually.
>> and got their opening page again. Selecting the Log In link this
>> time instead of the Sign Up link, I got to a page that said "3 lines
>> were replaced by line 1" and the page before me was one line long,
>> with no printable characters on that line.
>
> The 3 lines before that one empty line are:
> Sorry, your browser does not support the technologies needed to use our web interface.
> Please make sure you have the latest version, and that JavaScript is enabled.
> {Learn more about our browser requirements}.
There was a time not too many years ago when messages like the above
were much more blunt, often ending with "It really sucks being you!"
> I think there is no such thing as app-specific requirement. They say it
> works with thunderbird and there is no magic there, so
> mutt/alpine/edbrowse should work if we can get to the app password -
> it's just a password specific to imap/smtp that they call that way to
> differenciate it with the web interface password.
interesting.
> I'll admit I didn't try though, I stopped when they started asking for
> my phone number and my curiosity stops when I have to give personal
> information to these companies, but if you're willing to try maybe you
> can ask your daughter to generate that password for you as well. I
> believe that once it's setup it should work for classic imap/smtp and
> shouldn't change
That might be worth a try. I appreciate your attention, and
suggestions. Thanks.
Chuck
--
Here too, In Northeast Ohio, The Moon is Waxing Gibbous (62% of Full)
If you don't stand for something, you will fall for anything.
Sent from Matt's missing iPhone.
next prev parent reply other threads:[~2018-07-21 0:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 15:52 Erwin
2018-07-20 14:48 ` Karl Dahlke
2018-07-20 15:58 ` Chuck Hallenbeck
2018-07-20 23:44 ` Dominique Martinet
2018-07-21 0:39 ` Chuck Hallenbeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-19 10:06 Erwin
2018-07-19 13:27 ` Karl Dahlke
2018-07-19 14:03 ` Chuck Hallenbeck
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.21.99.1807202020450.20362@workshop \
--to=chuckhallenbeck@gmail.com \
--cc=asmadeus@codewreck.org \
--cc=edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).