Re: Retrieve thread URL from Gnus

[TRS-80]

Adam Sjøgren  writes:

> If you need a web-URL your best bet is the mailing list archives on
> lists.sourceforge.net.

In this case, I would agree, as (looking at the email) those are the
official project resources.  Which I would think should make a more
stable archival URL to link to.  Probably whatever the official project
archives are, generally, I would say should be your best bet.

For other cases (and future reference), I learned recently there are
actually several websites where you can search/link to URLs by
Message-ID, listed on that Wikipedia page:

https://en.wikipedia.org/wiki/Message-ID

Then there are also some public-inbox instances around, I know of at
least one private one with pretty good coverage of a few lists I care
about (including this one).  And Org Mode have an official one (maybe
some other projects, too).

Cheers,
TRS-80

Re: Retrieve thread URL from Gnus

[Byung-Hee HWANG]

André A. Gomes  writes:

> Adam Sjøgren  writes:
>
>> André writes:
>>
>>> Is it possible to retrieve a URL associated with it?  Thank you.
>>
>> No, Gmane no longer provides web-access to articles.
>>
>> You can fetch it via nntp, however:
>>
>> $ telnet news.gmane.io nntp
>
> [...]
>
> I didn't know that.  Thank you!

+1; Thanks Adam ^^^

Sincerely, Gnus fan Byung-Hee

-- 
^고맙습니다 _白衣從軍_ 감사합니다_^))//

Re: Retrieve thread URL from Gnus

[Roland Winkler]

On Wed, Mar 23 2022, Adam Sjøgren wrote:
> The equivalent is:
>
>  a) Open the news.gmane.io server: in the Group buffer press B RET (for
> nntp) and enter news.gmane.io
>  b) Find the group gmane.lisp.clisp.devel and enter it (press RET with
> point on the line)
>  c) Jump to article number: press j and enter the article number
>
> If you want to see the entire thread, you can press A T to have the
> other articles in the thread inserted into the *Summary* buffer.
>
> If you find it convenient to read news (i.e. mailing lists) via gmane,
> you can set it up as a permanent server in your Gnus configuration
> (gnus-secondary-methods) and subscribe to the groups you like to read.

Thanks, yes, I just realized that yesterday I fooled myself.  I am
already reading news via gnus, but yesterday I messed up from which
group I was looking for an old article.  Then I got confused that gnus
article numbers did not match what I was expecting to get and what I did
get as expected in the telnet session.  Entirely my fault!

But you are right: sometimes it is fun to go back to the basics and live
like a caveman!

Re: Retrieve thread URL from Gnus

[Adam Sjøgren]

Roland writes:

> I am fairly new to Gnus and your caveman-like approach came very handy
> when yesterday I needed to look at an old message for which I only knew
> the article number on the gmane server (the line "article 20429" in your
> example telnet session).

It is very handy to know a couple of nntp commands in a pinch! :-)

> What is the equivalent command in Gnus?

The equivalent is:

 a) Open the news.gmane.io server: in the Group buffer press B RET (for
nntp) and enter news.gmane.io
 b) Find the group gmane.lisp.clisp.devel and enter it (press RET with
point on the line)
 c) Jump to article number: press j and enter the article number

If you want to see the entire thread, you can press A T to have the
other articles in the thread inserted into the *Summary* buffer.

If you find it convenient to read news (i.e. mailing lists) via gmane,
you can set it up as a permanent server in your Gnus configuration
(gnus-secondary-methods) and subscribe to the groups you like to read.


  Best regards,

Adam


-- 
 "Archbishop of anarchy"Adam Sjøgren
   a...@koldfront.dk

Re: Retrieve thread URL from Gnus

[Roland Winkler]

On Tue, Mar 22 2022, Adam Sjøgren wrote:
> You're welcome. With Gnus you can skip all the telnetting-like-a-caveman
> stuff, of course :-)

I am fairly new to Gnus and your caveman-like approach came very handy
when yesterday I needed to look at an old message for which I only knew
the article number on the gmane server (the line "article 20429" in your
example telnet session).  What is the equivalent command in Gnus?

Thanks!

Re: Retrieve thread URL from Gnus

[Adam Sjøgren]

André writes:

>> You can fetch it via nntp, however:
>>
>> $ telnet news.gmane.io nntp
>
> [...]
>
> I didn't know that.  Thank you!

You're welcome. With Gnus you can skip all the telnetting-like-a-caveman
stuff, of course :-)


  Best regards,

Adam

-- 
 "I don't know! There's never a wrong idea in the   Adam Sjøgren
  brainstorming phase."a...@koldfront.dk

Re: Retrieve thread URL from Gnus

[André A . Gomes]

Adam Sjøgren  writes:

> André writes:
>
>> Is it possible to retrieve a URL associated with it?  Thank you.
>
> No, Gmane no longer provides web-access to articles.
>
> You can fetch it via nntp, however:
>
> $ telnet news.gmane.io nntp

[...]

I didn't know that.  Thank you!


-- 
André A. Gomes
"Free Thought, Free World"

Re: Retrieve thread URL from Gnus

[Adam Sjøgren]

André writes:

> Is it possible to retrieve a URL associated with it?  Thank you.

No, Gmane no longer provides web-access to articles.

You can fetch it via nntp, however:

$ telnet news.gmane.io nntp
Trying 116.202.254.214...
Connected to ciao.gmane.io.
Escape character is '^]'.
200 news.gmane.io InterNetNews NNRP server INN 2.6.3 ready (posting ok)
mode reader
200 news.gmane.io InterNetNews NNRP server INN 2.6.3 ready (posting ok)
group gmane.lisp.clisp.devel
211 22174 2047 24229 gmane.lisp.clisp.devel
article 20429
220 20429 <874otj5tlq@freebits.de> article
Path: news.gmane.org!not-for-mail
From: "Tobias C. Rittweiler" 
Newsgroups: gmane.lisp.clisp.devel
Subject: Thread issues
Date: Sat, 11 Jul 2009 13:47:45 +0200
Lines: 61
Approved: n...@gmane.org
Message-ID: <874otj5tlq@freebits.de>
NNTP-Posting-Host: lo.gmane.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Trace: ger.gmane.org 1247321126 20644 80.91.229.12 (11 Jul 2009 14:05:26 
GMT)
X-Complaints-To: use...@ger.gmane.org
NNTP-Posting-Date: Sat, 11 Jul 2009 14:05:26 + (UTC)
To: clisp-de...@lists.sourceforge.net
Original-X-From: clisp-devel-boun...@lists.sourceforge.net Sat Jul 11 
16:05:19 2009
Return-path: 
Envelope-to: lisp-clisp-de...@m.gmane.org
Original-Received: from lists.sourceforge.net ([216.34.181.88])
by lo.gmane.org with esmtp (Exim 4.50)
id 1MPdCY-000497-G6
for lisp-clisp-de...@m.gmane.org; Sat, 11 Jul 2009 16:05:18 +0200
Original-Received: from localhost ([127.0.0.1] 
helo=sfs-ml-3.v29.ch3.sourceforge.com)
by h25xhf1.ch3.sourceforge.com with esmtp (Exim 4.69)
(envelope-from )
id 1MPdCU-0007VD-Lk; Sat, 11 Jul 2009 14:05:14 +
Original-Received: from sfi-mx-4.v28.ch3.sourceforge.com ([172.29.28.124]
helo=mx.sourceforge.net)
by h25xhf1.ch3.sourceforge.com with esmtp (Exim 4.69)
(envelope-from ) id 1MPdCT-0007V6-98
for clisp-de...@lists.sourceforge.net; Sat, 11 Jul 2009 14:05:13 
+
Received-SPF: pass (1b2kzd1.ch3.sourceforge.com: domain of m.gmane.org
designates 80.91.229.2 as permitted sender)
client-ip=80.91.229.2;
envelope-from=lisp-clisp-de...@m.gmane.org; helo=ciao.gmane.org;
Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org)
by 1b2kzd1.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.69) id 1MPdCL-0007UO-OK
for clisp-de...@lists.sourceforge.net; Sat, 11 Jul 2009 14:05:13 
+
Original-Received: from root by ciao.gmane.org with local (Exim 4.43)
id 1MPdCJ-0006tR-2h
for clisp-de...@lists.sourceforge.net; Sat, 11 Jul 2009 14:05:03 
+
Original-Received: from host145.natpool.mwn.de ([138.246.7.145])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for ; Sat, 11 Jul 2009 14:05:03 
+
Original-Received: from tcr by host145.natpool.mwn.de with local (Gmexim 
0.1 (Debian))
id 1AlnuQ-0007hv-00
for ; Sat, 11 Jul 2009 14:05:03 
+
X-Injected-Via-Gmane: http://gmane.org/
Original-Lines: 48
Original-X-Complaints-To: use...@ger.gmane.org
X-Gmane-NNTP-Posting-Host: host145.natpool.mwn.de
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/23.0.60 (gnu/linux)
Cancel-Lock: sha1:4BI12f1ika5wiRWv82e8gR66hSA=
X-Spam-Score: -1.9 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.0 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/,
low trust [80.91.229.2 listed in list.dnswl.org]
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_HELO_PASS  SPF: HELO matches SPF record
-0.0 SPF_PASS   SPF: sender matches SPF record
0.6 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1MPdCL-0007UO-OK
X-BeenThere: clisp-de...@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: CLISP developers 
List-Unsubscribe: 
, 


List-Archive: 

List-Post: 
List-Help: 
List-Subscribe: ,

Errors-To: clisp-devel-boun...@lists.sourceforge.net