Gnus development mailing list
 help / color / mirror / Atom feed
From: dick.r.chiang@gmail.com
To: "Adam Sjøgren" <asjo@koldfront.dk>
Cc: ding@gnus.org
Subject: Re: Gnus backend for GitHub/GitLab?
Date: Tue, 19 Nov 2019 23:12:37 -0500	[thread overview]
Message-ID: <87r223uqx6.fsf@dick> (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")

I have some experience in this area.  Nearly everything we consume on the
internet fits the threaded message queue model.  Lars et al saw this fairly
early on.  The key though is an API that admits a sequence-numbered stream per
group to track "new messages since last visited."  A quick glance at
gitlab's API doesn't suggest it's on offer, and inferring such a record by
scanning html would be fragile and unwieldy.

There are also code-citation and push-button functionalities (merging PRs,
etc.) that are better served by point-and-click ui's.



  parent reply	other threads:[~2019-11-20  4:12 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 [this message]
2019-11-20 11:33 ` Lars Ingebrigtsen
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=87r223uqx6.fsf@dick \
    --to=dick.r.chiang@gmail.com \
    --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).