From: Nala Ginrut <nalaginrut@gmail.com>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: guile-oauth 1.3.0 released
Date: Thu, 30 Jun 2022 14:31:24 +0800 [thread overview]
Message-ID: <CAPjoZod0TmwzejvBKQt0xye0mXP60wPZQys1Pi4wMaE1Z5DLiQ@mail.gmail.com> (raw)
In-Reply-To: <CA+XASoWwUr--bt0upenDNO8rpoA3bR_2voBT2hNO-BpbOthNWA@mail.gmail.com>
Thank you very much!
I'll try to add oauth to Artanis in the next release!
On Thu, Jun 30, 2022, 14:15 Aleix Conchillo Flaqué <aconchillo@gmail.com>
wrote:
> Hi,
>
> I'm happy to announce guile-oauth 1.3.0. This release allows you to use
> other HTTP client libraries to perform HTTP requests. An *http-proc*
> procedure can be specified in all guile-oauth procedures that make HTTP
> requests, it defaults to Guile's (http-request). Thank you Nala Ginrut for
> the suggestion.
>
> 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.3.0.tar.gz
>
> https://download.savannah.nongnu.org/releases/guile-oauth/guile-oauth-1.3.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.3.0.tar.gz.sig
>
> * Changes since 1.3.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
>
next prev parent reply other threads:[~2022-06-30 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 6:11 guile-oauth 1.3.0 released Aleix Conchillo Flaqué
2022-06-30 6:31 ` Nala Ginrut [this message]
2022-06-30 7:29 ` Blake Shaw
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=CAPjoZod0TmwzejvBKQt0xye0mXP60wPZQys1Pi4wMaE1Z5DLiQ@mail.gmail.com \
--to=nalaginrut@gmail.com \
--cc=aconchillo@gmail.com \
--cc=guile-user@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 read-only IMAP folder(s) and NNTP newsgroup(s).