~edwargix

Recent activity

[PATCH git.sr.ht v2] Replace meta.sr.ht's /oauth endpoint with /oauth2 in comment 1 year, 2 months ago

From David Florness to ~sircmpwn/sr.ht-discuss

While there is a link to /oauth2 on the /oauth page, landing on /oauth2 right
away makes it obvious to server admins that /oauth2 is where they should be.

Discussion: <https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3C877cwnhpni.fsf%40florness.com%3E>
Signed-off-by: David Florness <david@florness.com>
---
v1 -> v2:
  - ignore /oauth in config.example.ini: <https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3C877cwnhpni.fsf%40florness.com%3E#%3CCQI5AI6ADO6H.39CESCLMYYHS5@taiga%3E>

 gitsrht/default_query.graphql | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gitsrht/default_query.graphql b/gitsrht/default_query.graphql
index 0ddaa07..630fffb 100644
[message trimmed]

[PATCH git.sr.ht v2] Replace meta.sr.ht's /oauth endpoint with /oauth2 in comment 1 year, 2 months ago

From David Florness to ~sircmpwn/sr.ht-dev

While there is a link to /oauth2 on the /oauth page, landing on /oauth2 right
away makes it obvious to server admins that /oauth2 is where they should be.

Discussion: <https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3C877cwnhpni.fsf%40florness.com%3E>
Signed-off-by: David Florness <david@florness.com>
---
v1 -> v2:
  - ignore /oauth in config.example.ini: <https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3C877cwnhpni.fsf%40florness.com%3E#%3CCQI5AI6ADO6H.39CESCLMYYHS5@taiga%3E>

 gitsrht/default_query.graphql | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gitsrht/default_query.graphql b/gitsrht/default_query.graphql
index 0ddaa07..630fffb 100644
[message trimmed]

Re: [PATCH git.sr.ht] Replace meta.sr.ht's /oauth endpoint with /oauth2 in comments 1 year, 2 months ago

From David Florness to ~sircmpwn/sr.ht-discuss

BTW, there are other repos that could also get a patch for this, but I
was gonna hold off on sending those until this one gets accepted (in
case folks disagree with the motivation).

-- 
David

Re: [PATCH git.sr.ht] Replace meta.sr.ht's /oauth endpoint with /oauth2 in comments 1 year, 2 months ago

From David Florness to ~sircmpwn/sr.ht-dev

BTW, there are other repos that could also get a patch for this, but I
was gonna hold off on sending those until this one gets accepted (in
case folks disagree with the motivation).

-- 
David

[PATCH git.sr.ht] Replace meta.sr.ht's /oauth endpoint with /oauth2 in comments 1 year, 2 months ago

From David Florness to ~sircmpwn/sr.ht-discuss

While there is a link to /oauth2 on the /oauth page, landing on /oauth2 right
away makes it obvious to server admins that /oauth2 is where they should be.

Discussion: <https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3C877cwnhpni.fsf%40florness.com%3E>
Signed-off-by: David Florness <david@florness.com>
---
 config.example.ini            | 2 +-
 gitsrht/default_query.graphql | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/config.example.ini b/config.example.ini
index 7c645e8..beface9 100644
--- a/config.example.ini
+++ b/config.example.ini
[message trimmed]

[PATCH git.sr.ht] Replace meta.sr.ht's /oauth endpoint with /oauth2 in comments 1 year, 2 months ago

From David Florness to ~sircmpwn/sr.ht-dev

While there is a link to /oauth2 on the /oauth page, landing on /oauth2 right
away makes it obvious to server admins that /oauth2 is where they should be.

Discussion: <https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3C877cwnhpni.fsf%40florness.com%3E>
Signed-off-by: David Florness <david@florness.com>
---
 config.example.ini            | 2 +-
 gitsrht/default_query.graphql | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/config.example.ini b/config.example.ini
index 7c645e8..beface9 100644
--- a/config.example.ini
+++ b/config.example.ini
[message trimmed]

Re: OAuth 2.0 for SourceHut services? 1 year, 2 months ago

From David Florness to ~sircmpwn/sr.ht-discuss

> But /oauth also links to /oauth2 and apart from those links I don't
> see what you would want to change.

just that.  I think it's less confusing because while you can get to
/oauth2 from /oauth, landing on /oauth2 right away makes it obvious that
that's where you should be.

-- 
David

OAuth 2.0 for SourceHut services? 1 year, 2 months ago

From David Florness to ~sircmpwn/sr.ht-discuss

Hi folks,

Is it possible to use OAuth 2.0 client tokens for sourcehut services
(git.sr.ht, todo.sr.ht, lists.sr.ht, etc)?

Each of the example config files currently points to the legacy OAuth
dashboard; the OAuth2.0 one ends in /oauth2 but these are /oauth:

- https://git.sr.ht/~sircmpwn/git.sr.ht/tree/0.81.3/item/config.example.ini#L115
- https://git.sr.ht/~sircmpwn/todo.sr.ht/tree/0.74.1/item/config.example.ini#L97
- https://git.sr.ht/~sircmpwn/lists.sr.ht/tree/0.55.1/item/config.example.ini#L108

Provided that OAuth2.0 is supported, would a patch to update the
config.example.ini files be accepted?

Re: GitHub Mirroring Tool? 1 year, 7 months ago

From David Florness to ~eliasnaur/gio

Elias Naur <mail@eliasnaur.com> writes:

> On Sun, 28 Aug 2022 at 01:54, David Florness <david@florness.com> wrote:
>>
>> P.S.: please "Reply All" to this email as I am not subscribed to this
>> list
>>
>> What tool, if any, is gioui using to mirror the sr.ht repo to GitHub?  I
>> have a repo where I would like to do this
>>
>> - https://git.sr.ht/~eliasnaur/gio
>> - https://github.com/gioui/gio
>>
>> I apologize if this question's been answered before and I couldn't find

Re: GitHub Mirroring Tool? 1 year, 7 months ago

From David Florness to ~eliasnaur/gio

Thanks for the reply, David!

David Vennik <david@cybriq.systems> writes:

> If you have both remotes attached to your version you can push up both
> remotes. When I do PRs on github I often have the original plus my fork with the
> branch so I can grab upstream updates, I usually call the upstream "upstream"
> but of course I don't have push access on the main/master. But if you did, you
> could easily do this and synchronise them both this way.

That makes sense; it just seems like it would be slightly annoying to
keep all branches constantly in sync between 2 or more remotes, so a
light wrapper script that handles that automatically would make life a
bit easier.