Subj : oxp locks up, again
To   : mark lewis
From : August Abolins
Date : Sat Feb 01 2020 23:17:33

On 01/02/2020 3:22 p.m., mark lewis : August Abolins wrote:

 ml> NOTE: i was specifically trying to steer away from diffs... they
 ml> really are not necessary in this day in time and one can easily
 ml> get a full nodelist every day that is as up to date as possible
 ml> with current processing...

Hi mark!

My bad. I erroneously referred to your "daily" solution as diffs.

I rather like the idea of just implementing a daily full nodelist.  But
it is rather cool to witness a program to chug away and construct an
update locally from the diffs.  ;)

Sadly (or maybe to the benefit of oxp), in my case, I have uncovered
something that should be fixed.

From a user POV, a daily updated nodelist is probably overkill. A "full
daily" makes sense for a sysop who relies heavily on contacting other
systems every day. As an ex-sysop I like the notion of a nearly
real-time updated nodelist.  But I would imagine that users (for which
something like oxp was designed for) may not be online every day, and/or
don't really need to contact other systems very much.

As for oxp actually processing a full daily updated list automatically,
I don't understand why that can't be so.  Is oxp hardcoded to expect the
full nodelist to be exactly 7 days from a previous one before it
overrides the old one?  If so, THEN a full daily wouldn't work, I guess.


-- 
Quoted with Reformator/Quoter. Info = https://tinyurl.com/sxnhuxc

--- TB68/Win7 (just keeping things short!)
 * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)

.