Hello,
TL;DR - looking for a peering setup for a single user instance of Inn2. In time my kids and wife may join me on Usenet, but that is not yet.
I am located in Sweden and the server is running Debian 12 and Inn2
version 2.7.1.
Running Inn2 stems from my work where I want/need to keep up with a dozen
or so linux kernel mailing lists which so happens are available via NNTP
to read at nntp.lore.kernel.org. But reading them remote was very slow, so
as any self-respecting geek, the answer was naturally to spin up Inn2 and mirror down the lists I wanted so I have them locally with a year worth of articles for history.
I would like to be able to get a backlog from the groups using nntpget and a date, so that I have some light reading until they start to fill up naturally.
Hello,
TL;DR - looking for a peering setup for a single user instance of
Inn2. In time my kids and wife may join me on Usenet, but that is
not yet.
Hello,
TL;DR - looking for a peering setup for a single user instance of Inn2. In time my kids and wife may join me on Usenet, but that is not yet.
Longer version;
I learned about and used Usenet some 30 years ago, alongside Fidonet. I am getting _very_ tired of the 'modern' interwebs and I want to get back into Usenet. And yes, once I figure out why my router is so reluctant
forwarding port 70, I will be running a Gopher server as well.
Running Inn2 stems from my work where I want/need to keep up with a dozen
or so linux kernel mailing lists which so happens are available via NNTP
to read at nntp.lore.kernel.org. But reading them remote was very slow, so
as any self-respecting geek, the answer was naturally to spin up Inn2 and mirror down the lists I wanted so I have them locally with a year worth of articles for history.
Now I would like to get peering so that I have most of the Big8 locally as well and I can post locally and have it funnel out. I have not set up
peering before so I may need an extra pointer or two. I can guarantee that there will be no spam as the only user is me and maybe my immediate family (wife and kids) should they become interested which I am not counting on.
I do not want any binary groups, just the text ones, and if possible, I
would like to be able to get a backlog from the groups using nntpget and a date, so that I have some light reading until they start to fill up naturally.
I am located in Sweden and the server is running Debian 12 and Inn2
version 2.7.1.
Hi Sirius,
I would like to be able to get a backlog from the groups using nntpget and a
date, so that I have some light reading until they start to fill up naturally.
I would recommend the use of pullnews, which is more configurable and probably more used than nntpget:
https://www.eyrie.org/~eagle/software/inn/docs/pullnews.html
Also, nntpget relies on the NEWNEWS command, which is not always enabled
on upstream news servers.
So, you're just going to set up a server on the local net of your
router?
Well, I'm glad you're so "sirius" about getting into the space!! I wish
you the best of luck.
Hi Sirius,
Running Inn2 stems from my work where I want/need to keep up
with a dozen or so linux kernel mailing lists which so happens
are available via NNTP to read at nntp.lore.kernel.org. But
reading them remote was very slow, so as any self-respecting
geek, the answer was naturally to spin up Inn2 and mirror down
the lists I wanted so I have them locally with a year worth of
articles for history.
Nice!
I would like to be able to get a backlog from the groups using
nntpget and a date, so that I have some light reading until
they start to fill up naturally.
I would recommend the use of pullnews, which is more
configurable and probably more used than nntpget:
https://www.eyrie.org/~eagle/software/inn/docs/pullnews.html
On tor, 2024/06/13 at 06:25:04 GMT, candycanearter07 wrote:
So, you're just going to set up a server on the local net of your
router?
Past tense - it is already running. :)
My spam-filter is apparently too good for certain mailing list software
and some of them will unsubscribe you silently (linux-mm@kvack.org -
looking at you) if you do not accept all messages from the list.
So I figured, wth, in for a penny, in for a pound. Few weeks later, it is chugging along quite nicely and peering was kind of the last item on the
list to do. :)
Well, I'm glad you're so "sirius" about getting into the space!! I wish
you the best of luck.
Thank you. It has been a few years since I last was tinkering with Usenet, but I have never forgotten it. Hopefully I can contribute something from
now on.
Hello,
TL;DR - looking for a peering setup for a single user instance of
Inn2. In time my kids and wife may join me on Usenet, but that is not
yet.
Longer version;
I learned about and used Usenet some 30 years ago, alongside Fidonet.
I am getting _very_ tired of the 'modern' interwebs and I want to get
back into Usenet. And yes, once I figure out why my router is so
reluctant forwarding port 70, I will be running a Gopher server as
well.
Running Inn2 stems from my work where I want/need to keep up with a
dozen or so linux kernel mailing lists which so happens are available
via NNTP to read at nntp.lore.kernel.org. But reading them remote was
very slow, so as any self-respecting geek, the answer was naturally
to spin up Inn2 and mirror down the lists I wanted so I have them
locally with a year worth of articles for history.
Now I would like to get peering so that I have most of the Big8
locally as well and I can post locally and have it funnel out. I have
not set up peering before so I may need an extra pointer or two. I
can guarantee that there will be no spam as the only user is me and
maybe my immediate family (wife and kids) should they become
interested which I am not counting on.
I do not want any binary groups, just the text ones, and if possible,
I would like to be able to get a backlog from the groups using
nntpget and a date, so that I have some light reading until they
start to fill up naturally.
I am located in Sweden and the server is running Debian 12 and Inn2
version 2.7.1.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 360 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 129:19:51 |
| Calls: | 7,686 |
| Files: | 12,828 |
| Messages: | 5,711,155 |