| |
N1URO > PACKET 09.01.19 08:58l 23 Lines 969 Bytes #999 (0) @ WW
BID : 15461_N1URO
Read: GUEST
Subj: Re: GM4UPX > Number of nodes
Path: IW8PGT<IR2UBX<F1OYP<ON0AR<GB7CIP<N1URO
Sent: 190109/0647Z @:N1URO.#CCT.CT.USA.NOAM #:15461 [Unionville] $:15461_N1URO
From: N1URO@N1URO.#CCT.CT.USA.NOAM
To : PACKET@WW
Ian (et al);
You're correct, properly setting qualities with your neighbors AND obs
counts helps a lot. The issues become bad when another node to one of
your neighbors sets their link a LOT higher than yours so then (s)he
then hijacks the path to you and you appear unconnectable when you know
that's not true.
I noticed on GB7CIP earlier today he had over 1,000 nodes! Imagine a user
on HF trying to view the list! They'd time out after approximately 100 nodes
never mind seeing the full listing! One thing to consider on your system is
what would be the slowest possible speed a remote user may possibly use. This
is one of the reasons I made a J and a JL command for the just heard list.
J will list the last 20, while JL (just heard long list) will list whatever
mheardd has in it's database.
It's good to see some positive discussions going on! Now to get non-sysops
involved in some banter :)
73 de N1URO
Read previous mail | Read next mail
| |
