On 1/14/24 11:13, Colin Macleod wrote:
> So I'm coming back to option 3 - run my own news server.
:-)
> I don't want the complexity of running INN,
Please elaborate on what complexity you think there is in running INN.
Other than initial setup, which isn't bad, INN is mostly set it and
forget it like almost all other Internet services.
I have multiple INN servers and I spend less than 5 minutes a month on
all of them combined (as in news service, OS updates are independent).
I do not consider leafnode to be a real NNTP server.
Yes it is a server that speaks NNTP. But my understanding is that
leafnode /reactively/ adds a group /after/ someone tries to make use of
it. Additionally I believe it will stop carrying a group after no use
for a long enough time.
I think that this will manifest itself in a few primary problems:
1) Users will have to access a newsgroup before leafnode will start
putting articles in it.
2) You will not have history in a newsgroup past the first time someone
showed any interest in the newsgroup.
3) People will likely end up with a false sense of lack of content
because the newsgroup will not have articles in it because of #1 & #2.
> So I'm thinking I could set that up and connect my web interface to it.
Probably. You would be creating a new two party system; your news
server + your web gateway and the end user.
> I would have to take on the hassle of managing user registrations
> myself, which I was hoping to avoid, but maybe that's the only way
> forward.
Such are the price for doing what you want to do.
Does leafnode have a concept of multiple user accounts connecting to it
as a server? Do you have a framework to put end user accounts into?
> Of course I would also need to get one or two upstream servers to
> peer with - any chance of that Ray?
I wasn't aware that leafnode supported multiple upstreams.
Does leafnode support traditional peering in any way? Either sending or
receiving articles? If it doesn't how do you send articles from
leafnode? Do those articles become associated with the account that you
are having leafnode point to the upstream?
There's a lot I don't know about leafnode. But given my experience with
INN, I seriously question if INN is the amount of work you think it will
be. What's more is I question if INN will be /more/ work than leafnode
or not. Especially if you have to get creative to support multiple
upstreams and / or down stream end user accounts.
My money is on a proper NNTP server, which I consider leafnode to not be.