From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: guile-oauth 1.2.0 released
Date: Wed, 29 Jun 2022 23:12:41 -0700 [thread overview]
Message-ID: <CA+XASoU-ZRp2X71Y+Rg_Je3R=s8QjVYOvp9viHdgOw6PfG5kwA@mail.gmail.com> (raw)
In-Reply-To: <CA+XASoVGAtOQ+nuTuXvQceteJ0DONUJxNAY1zsmJgV9An2rUMQ@mail.gmail.com>
I believe this should now work in 1.3.0 which I just released. Let me know
if you run into any issues if you try it out.
Thanks!
Aleix
On Wed, Jun 29, 2022 at 6:58 AM Aleix Conchillo Flaqué <aconchillo@gmail.com>
wrote:
> Thanks!
>
> That's actually currently not possible, but I guess we could pass a
> callback and call it whenever guile-oauth makes http requests. I'll see if
> I have time to add support for it.
>
> Aleix
>
> On Wed, Jun 29, 2022 at 12:47 AM Nala Ginrut <nalaginrut@gmail.com> wrote:
>
>> Nice work!
>> Is it possible to support guile-curl for its https client? There is
>> situation that the system can't install gnutls-guile.
>>
>> On Wed, Jun 29, 2022, 15:30 Aleix Conchillo Flaqué <aconchillo@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I'm pleased to announce guile-oauth 1.2.0. This is a bug fix release that
>>> fixes an OAuth 2.0 spec compliance issue when obtaining access tokens.
>>> Also
>>> a minor feature for OAuth 1.0a has been added, it is now possible to
>>> specify where the OAuth protocol parameters are sent ('header, 'query or
>>> 'body).
>>>
>>> https://github.com/aconchillo/guile-oauth/
>>>
>>> * About
>>>
>>> guile-oauth is an OAuth client module for Guile. It supports the
>>> following
>>> features:
>>>
>>> - OAuth 1.0a: HMAC-SHA1 and PLAINTEXT signatures.
>>> - OAuth 2.0: Authorization Code and Client Credentials grant types.
>>>
>>> * Download
>>>
>>> Compressed sources and a GPG detached signature[*]:
>>>
>>>
>>> https://download.savannah.nongnu.org/releases/guile-oauth/guile-oauth-1.2.0.tar.gz
>>>
>>> https://download.savannah.nongnu.org/releases/guile-oauth/guile-oauth-1.2.0.tar.gz.sig
>>>
>>> [*] To verify download both files and then run:
>>>
>>> gpg --keyserver keys.openpgp.org \
>>> --recv-keys 7CEC5511C8D057A9EF17470C54D4CC6FFC7468F4
>>>
>>> gpg --verify guile-oauth-1.2.0.tar.gz.sig
>>>
>>> * Changes since 1.2.0
>>>
>>> https://github.com/aconchillo/guile-oauth/blob/master/NEWS
>>>
>>> Bugs and comments can be reported at
>>> https://github.com/aconchillo/guile-oauth/issues
>>>
>>> Happy hacking!
>>>
>>> Aleix
>>>
>>
prev parent reply other threads:[~2022-06-30 6:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 7:28 guile-oauth 1.2.0 released Aleix Conchillo Flaqué
2022-06-29 7:47 ` Nala Ginrut
2022-06-29 13:58 ` Aleix Conchillo Flaqué
2022-06-30 6:12 ` Aleix Conchillo Flaqué [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+XASoU-ZRp2X71Y+Rg_Je3R=s8QjVYOvp9viHdgOw6PfG5kwA@mail.gmail.com' \
--to=aconchillo@gmail.com \
--cc=guile-user@gnu.org \
--cc=nalaginrut@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).