From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Adam Sjøgren" <asjo@koldfront.dk>
Cc: ding@gnus.org
Subject: Re: Gnus backend for GitHub/GitLab?
Date: Wed, 20 Nov 2019 12:33:56 +0100 [thread overview]
Message-ID: <87v9reixy3.fsf@gnus.org> (raw)
In-Reply-To: <8736ejsehi.fsf@tullinup.koldfront.dk> ("Adam =?utf-8?Q?Sj?= =?utf-8?Q?=C3=B8gren=22's?= message of "Tue, 19 Nov 2019 23:11:53 +0100")
Adam Sjøgren <asjo@koldfront.dk> writes:
> It hit me that accessing comments on GitHub/GitLab seems like an obvious
> candidate for a Gnus backend.
>
> * GitHub/GitLab-instance: a Gnus server
> * Each project you're interested in: a subscribed group
> * Each issue: a top-level article
> * Each comment: replies to issues/other comments
> * Label, State ...: headers that can be edited
That would indeed be nice, but the main problem with the APIs that
Gitlab provides is that... they're very chatty and aren't geared
towards "show me what's changed since <foo>" (which is what Gnus thrives
on).
This means that you have to issue a whole bunch of API requests just to
get the basic info, which means that things get very s-l-o-w.
But I've just skimmed the Gitlab API documentation; perhaps it has
what's needed to make things go fast.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-11-20 11:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 22:11 Adam Sjøgren
2019-11-20 3:31 ` Eric Abrahamsen
2019-11-20 4:12 ` dick.r.chiang
2019-11-20 11:33 ` Lars Ingebrigtsen [this message]
2019-11-20 12:38 ` Adam Sjøgren
[not found] ` <87h82ywu6i.fsf@gmx.de>
2019-11-20 15:01 ` Adam Sjøgren
[not found] ` <87h82yvb7r.fsf@gmx.de>
2019-11-20 15:35 ` Adam Sjøgren
2019-11-21 12:31 ` Lars Ingebrigtsen
2020-01-14 20:42 ` Adam Sjøgren
2020-01-14 21:23 ` dick
2020-01-14 22:03 ` Adam Sjøgren
2020-01-14 22:18 ` dick
2020-01-14 22:45 ` Adam Sjøgren
2020-01-15 4:47 ` dick
2020-03-17 11:03 ` dick.r.chiang
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=87v9reixy3.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=asjo@koldfront.dk \
--cc=ding@gnus.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).