Gnus development mailing list
 help / color / mirror / Atom feed
From: Julien Danjou <julien@danjou.info>
To: Tassilo Horn <tsdh@gnu.org>
Cc: ding@gnus.org
Subject: Re: Username for gnus-notifications
Date: Thu, 30 Aug 2012 08:45:03 +0200	[thread overview]
Message-ID: <878vcwri8g.fsf@dex.adm.naquadah.org> (raw)
In-Reply-To: <87a9xcyk00.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Thu, 30 Aug 2012 08:25:03 +0200")

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

On Thu, Aug 30 2012, Tassilo Horn wrote:

> I wanted to try it out and added `gnus-notifications' to the relevant
> hook.  Now, after getting new mail, I'm queried for username/password
> for some google site.  I didn't remember the exact URL and it's not in
> *Messages*.  I tried with my google user account name tsdh80 + the
> corresponding password but was queried again.  Then I tried with my
> complete gmail email address as username and the same password, but
> still I was queried again.  So I've quit using C-g.
>
> Strangely, now when I hit `g` again, it asks for my gnome keyring
> password once, and then it shows the notifications as it should.

That's goole-contacts trying to get OAuth access. And it did get it
finally, so it stored the token in a GPG encrypted file (that's why
gnome-keyring's asking your password).

> So it seems to work, but for what was the first query loop good for
> then?

OAuth authentification, but the fact that it looped is strange.

Note that's nothing specific about gnus-notifications, more likely a
problem with google-contacts or oauth2.

-- 
Julien Danjou
/* Free Software hacker & freelance
   http://julien.danjou.info */

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2012-08-30  6:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-30  6:25 Tassilo Horn
2012-08-30  6:45 ` Julien Danjou [this message]
2012-08-30  6:54   ` Tassilo Horn
2012-08-30  8:08     ` Julien Danjou
2012-08-30  8:40       ` Tassilo Horn
2012-08-30 11:01         ` Peter Münster
2012-08-30 13:10           ` Tassilo Horn
2012-08-30 15:18             ` Julien Danjou
2012-08-30 17:45               ` Tassilo Horn
2012-08-30 19:04             ` Peter Münster
2012-08-30 19:46               ` Tassilo Horn
2012-08-30 21:02                 ` Julien Danjou
2012-08-31  6:23                   ` Tassilo Horn
2012-08-30 15:17         ` Julien Danjou
2012-08-30 14:13   ` Tassilo Horn
2012-08-30 15:19     ` Julien Danjou
2012-08-30 17:47       ` Tassilo Horn
2012-08-31  7:54       ` Tassilo Horn

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=878vcwri8g.fsf@dex.adm.naquadah.org \
    --to=julien@danjou.info \
    --cc=ding@gnus.org \
    --cc=tsdh@gnu.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;
as well as URLs for NNTP newsgroup(s).