* Originally in fidotest
* Crossposted in fidosoft.husky
Hello, Nicholas!

01 Oct 24 16:47, from Nicholas Boel -> Nil Alexandrov:

| + 2:154/10
| | + 2:3634/12
| | | + 2:135/115
| | | | + 2:135/205
| | | | L 2:135/366
| | | L 2:123/160
| | + 2:2320/105
| | | L 2:2320/107
| | + 2:226/44
| | L 2:226/18

Except yours thinks everyone is in zone 2....

Very true. I have zero FTN peering with Z3, so my view of world
is limited but still a bit wider than the original post.

Or Z1, apparently, since all of the above quoted links are Z1..
starting with my own. :(

Actually, you are right again. There is a bug in husky hpttree utility. It treats 2D PATH addresses as if they were belonging to your default/home zone number. The improvement could be that hpttree would parse out the real zone number from the origin line.

Best Regards, Nil
--- GoldED+/LNX 1.1.5-b20240306
* Origin: FidoNet member since 1995 (2:5015/46)

Hi Nil.

02 Oct 24 02:39, you wrote to Nicholas Boel:

Except yours thinks everyone is in zone 2....

Very true. I have zero FTN peering with Z3, so my view of world
is limited but still a bit wider than the original post.

Or Z1, apparently, since all of the above quoted links are Z1..
starting with my own. :(

Actually, you are right again. There is a bug in husky hpttree
utility. It treats 2D PATH addresses as if they were belonging to your default/home zone number. The improvement could be that hpttree would parse out the real zone number from the origin line.

I proposed a long time ago that hpttree should also check the nodelist. :)

'Tommi

--- GoldED+/LNX 1.1.5-b20240309
* Origin: rbb.fidonet.fi (2:221/360)

Hello, Tommi!

02 Oct 24 10:23, from Tommi Koivula -> Nil Alexandrov:

There is a bug in husky hpttree utility. It treats 2D PATH addresses
as if they were belonging to your default/home zone number. The
improvement could be that hpttree would parse out the real zone
number from the origin line.

I proposed a long time ago that hpttree should also check the
nodelist. :)

I did not follow that discussion. What would be the benefit of the nodelist knowledge for hpttree?

I proposed a long time ago the way how hpttree can create a graph using SEENBYs and not just PATH. Collect all nodes from SEENBY for all PATHs with depth one - those are direct links. Collect all nodes from SEENBY with PATH depth two and subtract list of nodes known at PATH depth one. Repeat for longer paths.

Best Regards, Nil
--- GoldED+/LNX 1.1.5-b20240306
* Origin: FidoNet member since 1995 (2:5015/46)

Hello Tommi!

02 Oct 24, Tommi Koivula wrote to Nil Alexandrov:

Actually, you are right again. There is a bug in husky hpttree
utility. It treats 2D PATH addresses as if they were belonging to
your default/home zone number. The improvement could be that
hpttree would parse out the real zone number from the origin
line.

I proposed a long time ago that hpttree should also check the
nodelist. :)

If the tool is designed to create a tree from the PATH kludges and there are no zones in the PATH kludges then the tool should not display zones at all.

A seperate tool to verify a 2D aka against the nodelist may be usefull in this and other cases.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai,

On Wed, Oct 02 2024 12:05:22 -0500, you wrote:

If the tool is designed to create a tree from the PATH kludges and there are no zones in the PATH kludges then the tool should not display zones at all.

Agreed. If the zones weren't there nobody would have said anything. However, if zones are going to be displayed, they should be displayed correctly.

Regards,
Nick

... He who laughs last, thinks slowest.
--- slrn/pre1.0.4-9 (Linux)
* Origin: The Pharcyde ~ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

On 2.10.2024 20.05, Kai Richter wrote:

If the tool is designed to create a tree from the PATH kludges and there
are no zones in the PATH kludges then the tool should not display zones at all.

Yes. That is why I filter the output of hpttree with sed before posting. 🙂

'Tommi

---
* Origin: smapinntpd/lnx (2:221/1.0)