From: Dave Taht <dave@taht.net>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: interop with leafnode
Date: Fri, 26 Oct 2018 17:33:20 -0700
Message-ID: <87efcc44a7.fsf@taht.net> (raw)
In-Reply-To: <20181027001054.dd7si5aukfwxuop4@dcvr> (Eric Wong's message of "Sat, 27 Oct 2018 00:10:54 +0000")
Eric Wong <e@80x24.org> writes:
> Dave Taht <dave@taht.net> wrote:
>> I excitedly accessed it directly from gnus. Oh, joy, bliss, rapture!
>> Blazing fast, useful at a glance.
>>
>> In a paroxysm of overenthusiasm for the the good ole days I then
>> setup a
>> leafnode real quick and pointed it at his instance so I could
>> replicate...
>>
>> For most (not all) traffic, leafnode does this:
>>
>> > Oct 16 22:08:01 spaceheater fetchnews[3045]: lwn.kernel.lkml:
>> > considering articles 200621 - 200643
>> > Oct 16 22:08:01 spaceheater fetchnews[3045]: Discarding article
>> > 200621
>> > - no Path: found
>
> I guess there's some bug or missing commands in public-inbox-nntpd
> which leafnode relies on. Sorry I haven't had time to investigate
> or do much with public-inbox, lately (but maybe you could :)
>
>> :(
>>
>> I'm really glad to hear of this project. It sounds like more of the
>> right way to do this is via a local git?
>
> Yes, git clone/fetch + running your own public-inbox-nntpd instance
> and using slrn/gnus/mutt(w/ nntp patch)/sylpheed/thunderbird all
> seem to work.
I will try to modernize.
next prev parent reply index
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 16:28 Dave Taht
2018-10-27 0:10 ` Eric Wong
2018-10-27 0:33 ` Dave Taht [this message]
2018-10-27 0:43 ` Eric Wong
2018-10-27 16:07 ` Dave Taht
2019-05-05 21:40 ` Eric Wong
2019-06-13 7:00 ` Eric Wong
2019-06-13 17:52 ` Dave Taht
2019-06-13 20:46 ` [PATCH] nntp: ensure Message-ID is not folded for leafnode Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efcc44a7.fsf@taht.net \
--to=dave@taht.net \
--cc=e@80x24.org \
--cc=meta@public-inbox.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
user/dev discussion of public-inbox itself
Archives are clonable:
git clone --mirror https://public-inbox.org/meta
git clone --mirror http://czquwvybam4bgbro.onion/meta
git clone --mirror http://hjrcffqmbrq6wope.onion/meta
git clone --mirror http://ou63pmih66umazou.onion/meta
Example config snippet for mirrors
Newsgroups are available over NNTP:
nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta
nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta
nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta
nntp://news.gmane.io/gmane.mail.public-inbox.general
note: .onion URLs require Tor: https://www.torproject.org/
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git