unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Aleksandr Vityazev <avityazev@posteo.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,  emacs-devel@gnu.org
Subject: Re: [ELPA] New package: srht
Date: Thu, 19 May 2022 21:06:28 +0000	[thread overview]
Message-ID: <87ilq1tep7.fsf@posteo.org> (raw)
In-Reply-To: <87czg9waac.fsf@gnu.org> (Tassilo Horn's message of "Thu, 19 May 2022 21:50:14 +0200")

On 2022-05-19, 21:50 +0200, Tassilo Horn <tsdh@gnu.org> wrote:

> Aleksandr Vityazev <avityazev@posteo.org> writes:
>
> Hi Aleksandr,
>
>>> Out of curiosity, what are you planning to do?
>>>
>>> I didn't quite get Stefan's compaint to begin with.  I would imagine
>>> one sets srht-domain on a per-project basis, i.e., in a
>>> .dir-locals.el file.  Should the package cater for the possibility
>>> that a project's git is on instance 1 but the tracker on instance 2?
>>> Or should there just be a way to define all instances I want to
>>> interact with and then have an convenient switch-command?  Or should
>>> the instance be a mandatory argument to all functions (which would
>>> also be ok if it's just a library providing access to the srht API)
>>> and packages using srht should handle the "which instance" aspect?
>>
>> Not to say that srht is a library that simply binds the Sourcehut REST
>> API. There are also several commands to interact with. As a solution, I
>> chose the latter by adding an extra mandatory argument for the
>> functions. The available commands use srht-domains (list of instance
>> domain names), where users can specify all the instances they want to
>> interact with. When the command is invoked, it offers instance selection
>> if srht-domains contains more than one. When used in conjunction with
>> .dir-locals.el there is little change.
>
> Sounds good.
>
> I've just wanted to give it a try.  The docs of srht-username don't say
> wether it is with the ~ or without.

Will work either way, but yes it's worth clarifying.

> I've generated a new OAuth 2.0 token and put a line in my
> ~/.authinfo.gpg as stated in the README, i.e.:
>
>   machine sr.ht password <my-oauth-token>
>
> However, when I try to use srht-paste-region I always get this error:
>
> --8<---------------cut here---------------start------------->8---
> error in process sentinel: Unkown error with status 400: #s(plz-error nil #s(plz-response 2 400 ((server . "nginx") (date . "Thu, 19 May 2022 20:00:32 GMT") (content-type . "application/json") (content-length . "58") (content-security-policy . "default-src 'none'; style-src 'self' 'unsafe-inline'; img-src * data:; script-src 'self' 'unsafe-inline'")) "{\"errors\": [{\"reason\": \"Invalid or expired OAuth token\"}]}") nil)
> --8<---------------cut here---------------end--------------->8---
>
> I've tried srht-username with and without tilde, I've tried using
>
>   machine sr.ht login <username> password <my-oauth-token>
>
> but always got the above error...
>
> Oh, I finally made it!  It seems you cannot use an OAuth 2.0 token but
> must use a legacy one.  I'm not sure whose fault that is.  I use a sr.ht
> OAuth 2.0 token in hut (the command line client for sr.ht) without
> issues.  I think that uses the same REST/GraphQL APIs.

Sourcehut REST API does not support OAuth2 [1], also worth clarifying.
I don't use hut, but after looking a bit, I can tell that only GraphQl
with API2.0 is used there. There is a GraphQl library for Emacs, but
unfortunately neither elpa nor non-gnu elpa has it. 

Thanks for feedback.

[1] https://sourcehut.org/blog/2020-09-25-api-2-updates/
-- 
Best regards,
Aleksandr Vityazev



  reply	other threads:[~2022-05-19 21:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 16:15 [ELPA] New package: srht Aleksandr Vityazev
2022-05-17 12:54 ` Alexander Adolf
2022-05-17 14:49   ` Aleksandr Vityazev
2022-05-18 11:15     ` Alexander Adolf
2022-05-18 12:49     ` Stefan Monnier
2022-05-18 13:13       ` Tassilo Horn
2022-05-17 16:03   ` Tassilo Horn
2022-05-17 18:42 ` Stefan Monnier
2022-05-17 19:07   ` Aleksandr Vityazev
2022-05-17 19:17     ` Stefan Monnier
2022-05-18 17:47       ` Aleksandr Vityazev
2022-05-19  4:56         ` Tassilo Horn
2022-05-19 19:10           ` Aleksandr Vityazev
2022-05-19 19:50             ` Tassilo Horn
2022-05-19 21:06               ` Aleksandr Vityazev [this message]
2022-05-20  6:05                 ` Tassilo Horn
2022-05-20 18:39                   ` Aleksandr Vityazev
2022-05-20 19:08                   ` Stefan Kangas
2022-05-21 22:30                     ` Jonas Bernoulli

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ilq1tep7.fsf@posteo.org \
    --to=avityazev@posteo.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).