public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: BRM <bm_witness@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Yahoo and strange traffic.
Date: Wed, 25 Aug 2010 06:21:06 -0700 (PDT)	[thread overview]
Message-ID: <497260.25873.qm@web51908.mail.re2.yahoo.com> (raw)
In-Reply-To: <4C74E95C.1040104@gmail.com>

----- Original Message ----

> Joshua Murphy wrote:
> > Well, glancing at the GET request it's making  there, as well as the
> > API google points me to when I look it  up...
> >
> >  http://developer.yahoo.com/messenger/guide/ch03s02.html#d4e4628
> >
> >  You're right that it's after an image from their profile, but the
> > cause  of the failure appears to be related to some sort of credentials
> > Yahoo  wants the messenger to provide. You might poke Kopete's
> > bugtracker to  see if they've a related bug on file already, and if
> > they don't, throw  one their way.
> >
> > The API Yahoo appears to be using there (based on  a response I got
> > back in poking lightly) is, or is based on, OAuth,  which according to
> > this:
> >
> >  http://oauth.net/core/1.0/#http_codes
> >
> > specifies that a request  should give a 401 response (Authorization
> > Required vs Unauthorized is  purely the choice of phrase used in the
> > program decoding the numerical  code, i.e. wireshark in your example of
> > it there) in the following  cases:
> >
> > HTTP 401 Unauthorized
> >    * Invalid  Consumer Key
> >    * Invalid / expired Token
> >     * Invalid signature
> >    * Invalid / used nonce
> >
> >  Yahoo, essentially, *does* give a "bugger off"!! with that response,
> > but  Kopete simply takes it, considers it a brief instant, then decides
> >  "Maybe the answer will change if I try again *now*!"... at which point
> >  it proceeds to introduce its proverbial cranium to the proverbial
> > brick  and mortar vertical surface one might term "the wall."
> >  Repeatedly.
> >
> >    
> 
> I was sort of figuring that it  was trying to get something and Yahoo 
> wasn't liking it.  At least now  we know for sure.
> 
> I went to bug.kde and searched but I didn't see  anything.  Of course, 
> I'm not really sure what the heck to look for  since I don't know what is 
> failing, other than  Kopete.

Best bet would probably be to check with the Kopete devs on IRC or mailing list 
(kopete-devel).

Ben




  reply	other threads:[~2010-08-25 13:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-15 20:34 [gentoo-user] Yahoo and strange traffic Dale
2010-08-15 20:55 ` Paul Hartman
2010-08-15 21:18   ` BRM
2010-08-15 21:35     ` Dale
2010-08-15 22:25       ` Peter Humphrey
2010-08-15 22:48         ` Dale
2010-08-15 21:29   ` Alan McKinnon
2010-08-16 22:55     ` Dale
2010-08-16 23:39       ` Adam Carter
2010-08-17  1:20         ` Dale
2010-08-17  1:32           ` Adam Carter
2010-08-17  5:46             ` Dale
2010-08-17  6:09               ` Adam Carter
2010-08-17 10:23                 ` Dale
2010-08-17 11:15                   ` Jake Moe
2010-08-17 11:26                     ` Dale
2010-08-17 14:29                   ` BRM
2010-08-17 16:10                     ` Mick
2010-08-17 20:15                       ` Dale
2010-08-17 21:11                         ` Mick
2010-08-17 21:32                           ` Dale
2010-08-18  2:09                             ` BRM
2010-08-18  2:18                               ` Dale
2010-08-18  2:18                               ` Dale
2010-08-25  2:36                     ` Dale
2010-08-25  8:08                       ` Joshua Murphy
2010-08-25  9:58                         ` Dale
2010-08-25 13:21                           ` BRM [this message]
2010-08-25 13:57                             ` Joshua Murphy
2010-08-25 22:34                               ` Dale
2010-08-15 21:32 ` Mick

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=497260.25873.qm@web51908.mail.re2.yahoo.com \
    --to=bm_witness@yahoo.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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