edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Amazon Shortcuts
Date: Sun, 14 Jan 2018 07:08:50 -0500	[thread overview]
Message-ID: <20180014070850.eklhad@comcast.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]

Someone suggested calling up the login page instead of the home page to save debug output and time etc, and yes that works.
I took the session ID off of the login url, and all the search stuff, and went to this page.

https://www.amazon.com/gp/navigation/redirector.html/ref=sign-in-redirect

Since the session id was not in the path it barked, but oblidgingly made me a new one,
and told me to enable cookies. Fair enough.
Still the login fields were there, and I put Wendys credentials in and I'm in.

http://www.eklhad.net/amazon.wendy.5

But let's take another step.
After line 520 in jseng-duk.c, insert a return statement.
Now there are no timers. They don't set and thus they don't run.
Still I can sign in.

http://www.eklhad.net/amazon.notimers.5

That eliminates more debug stuff, and the chattiness that Chuck talks about.
It also supports what I said a week ago, maybe we should have a switch to turn timers off, that only we would use for debugging.
I'll probably implement that, but not as crude as described above.
Probably allow timers to set, just don't run them. Have to think about that for a bit.
Anyways, let's carry on.

If any of you wants to send me your login and password I'll try login over here, to eliminate more variables.
Send privately of course, eklhad@gmail.com which is encrypted.

Karl Dahlke

             reply	other threads:[~2018-01-14 12:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-14 12:08 Karl Dahlke [this message]
2018-01-15  1:22 ` 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:
  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=20180014070850.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /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).