The FAQ says:

HotdogEd supports as many AKAs (servers) as you wish with the only remark: you can't have multiple points on one ftn node. This is a limitation of ftn provider.

However I've found that you can have 2 points of the same bossnode. The trick is using point .0 for the uplink of the second one.

- First point, uplink 2:345/678
- Second point, uplink 2:345/678.0

--
Carlos
--- Hotdoged/2.13.5/Android
* Origin: cyberiada (2:341/234.12)

On 10.06.2023 13:05, Carlos Navarro wrote:

The FAQ says:

HotdogEd supports as many AKAs (servers) as you wish with the only
remark: you can't have multiple points on one ftn node. This is a
limitation of ftn provider.

However I've found that you can have 2 points of the same bossnode. The trick is using point .0 for the uplink of the second one.

- First point, uplink 2:345/678
- Second point, uplink 2:345/678.0

And if you for some strange reason need more than two, you can have "a point of a point". (The boss node in hotdoged can be a point address, even if it says boss 3D ftn address in setup). Just set up as many point aka's to the main boss as you want. :)

'Tommi

---
* Origin: rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)

11 Jun 2023 08:43, you wrote to me:

However I've found that you can have 2 points of the same
bossnode. The trick is using point .0 for the uplink of the
second one.

- First point, uplink 2:345/678
- Second point, uplink 2:345/678.0

And if you for some strange reason need more than two, you can have
"a point of a point". (The boss node in hotdoged can be a point
address, even if it says boss 3D ftn address in setup). Just set up as many point aka's to the main boss as you want. :)

I see. Nice to know :-)

A reason for having several points in a HotdogEd instance would be being able to use different encodings for receiving echos. For example, CP866 for RU areas on point A, and CP437, UTF-8 or other on point B for the rest of areas.

HotdogEd allows you to set a specific charset (codepage) for each area (group), but it only works for exporting echomail. For incoming messages, it uses the global Codepage in the point's Server settings.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

Hello, Carlos Navarro.
On 10.06.23 12:05 PM you wrote:

The FAQ says: However I've found that you can have 2 points of the same bossnode. The trick is
using point .0 for the uplink of the second one. - First point, uplink 2:345/678 - Second
point, uplink 2:345/678.0

But it only works from different devices :)
Personally from one device I have this setting takes out node completely and no mail goes :)

--
� ������訬� ��������ﬨ! Virtual HotDog
--- ��℮�/2.14.5/Android
* Origin: Android device, Milky Way (2:50/700)

Hello, Oleg Nazaroff.
On 12/10/23 14:37 you wrote:

The FAQ says: However I've found that you can have 2 points of
the same bossnode. The trick is using point .0 for the uplink of
the second one. - First point, uplink 2:345/678 - Second point,
uplink 2:345/678.0

But it only works from different devices :)

It works for me. This is the second point in my phone, with uplink 2:341/234.0

I've tested a bit more and found that this only works if both points have the same password - when polling the bossnode, it seems it uses the one defined in the main point.

Another issue is, if you use Manage subscription on the second point, the netmails to areafix that it generates are stored in the first point's Outgoing folder, and they are sent via that one. (But it works.)

Personally from one device I have this setting takes out node completely and no mail goes :)

Oh, I hope it didn't break too much and you could restore it... I haven't tried using node addresses.

--
С наилучшими пожеланиями! Virtual HotDog --- ХотДог/2.14.5/Android
* Origin: Android device, Milky Way (2:50/700)

--
Best regards!
Posted using Hotdoged on Android
--- Hotdoged/2.13.5/Android
* Origin: Android device, Milky Way (2:341/234.123)

Hello, Carlos .
On 12.10.23 9:57 PM you wrote:

Hello, Oleg Nazaroff. On 12/10/23 14:37 you wrote: It works for me. This is the second point in
my phone, with uplink 2:341/234.0

Not two points simultaneously on same device, isn't it?

I've tested a bit more and found that this only works if both points have the same password -
when polling the bossnode, it seems it uses the one defined in the main point.

But if you receive mail from one point, what happens for another?

Another issue is, if you use Manage subscription on the second point, the netmails to areafix
that it generates are stored in the first point's Outgoing folder, and they are sent via that
one. (But it works.)

Don't understand again ;) this two points is on the one device? ;)

Oh, I hope it didn't break too much and you could restore it... I haven't tried using node
addresses.

I've just removed second "experimental" point ;)


--
� ������訬� ��������ﬨ! Virtual HotDog
--- ��℮�/2.14.5/Android
* Origin: Android device, Milky Way (2:50/700)

Hello, Oleg Nazaroff.
On 13/10/23 14:45 you wrote:

Hello, Oleg Nazaroff. On 12/10/23 14:37 you wrote: It works for
me. This is the second point in my phone, with uplink 2:341/234.0

Not two points simultaneously on same device, isn't it?

Yes, same device. See here:

http://www.cyberiada.org/fido/tmpfiles/hotdoged2points.jpg

I've tested a bit more and found that this only works if both
points have the same password - when polling the bossnode, it
seems it uses the one defined in the main point.

But if you receive mail from one point, what happens for another?

I can send/receive in both.

If I make a poll when I'm at HotdogEd's initial screen (see my capture above), it will make 2 polls to the boss sequentially, one for each point.

Another issue is, if you use Manage subscription on the second
point, the netmails to areafix that it generates are stored in
the first point's Outgoing folder, and they are sent via that
one. (But it works.)

Don't understand again ;) this two points is on the one device? ;)

Yes... on my phone :-)

I have described an issue I found when subscribing echos from the second point.

If I haven't explained this properly I can try to rephrase it.

Oh, I hope it didn't break too much and you could restore it... I
haven't tried using node addresses.

I've just removed second "experimental" point ;)

Glad to know ;-)


--
Best regards!
Posted using Hotdoged on Android
--- Hotdoged/2.13.5/Android
* Origin: Android device, Milky Way (2:341/234.123)

Hello, Carlos Navarro.
On 13.10.23 8:27 PM you wrote:

Hello, Oleg Nazaroff. On 13/10/23 14:45 you wrote: Yes, same device. See here:

May be this possible only to points ;) I'm node..


--
� ������訬� ��������ﬨ! Virtual HotDog
--- ��℮�/2.14.5/Android
* Origin: Android device, Milky Way (2:50/700)

Hello, Oleg Nazaroff.
On 13/10/2023 22.14 you wrote:

Hello, Carlos Navarro.
On 13.10.23 8:27 PM you wrote:

Hello, Oleg Nazaroff. On 13/10/23 14:45 you wrote: Yes, same device. See here:

May be this possible only to points ;) I'm node..

I think it doesn't matter. I have now this HotDogEd node connected to uplink 2:221/6.6. ;)

Tommi
--- Hotdoged/2.13.5/Android
* Origin: Android device, Milky Way (2:221/10)

Hello, Tommi Koivula.
On 14/10/23 9:57 you wrote:

Yes, same device. See here:

May be this possible only to points ;) I'm node..

I think it doesn't matter. I have now this HotDogEd node connected
to uplink 2:221/6.6. ;)

Oh, a bosspoint! :-)

But we were talking about having two downlinks of the same bossnode in one device, not with different uplinks...

--
--
Carlos
--- Hotdoged/2.13.5/Android
* Origin: cyberiada (2:341/234.12)

Hello, Oleg Nazaroff.
On 13/10/23 22:14 you wrote:

Yes, same device. See here:

May be this possible only to points ;) I'm node..

Could be. I've not tested that...

Is it common to use HotdogEd with node addresses in R50? More than points?

--
Best regards!
Posted using Hotdoged on Android
--- Hotdoged/2.13.5/Android
* Origin: Android device, Milky Way (2:341/234.123)

Hi Carlos.

14 Oct 23 09:56, you wrote to me:

May be this possible only to points ;) I'm node..

I think it doesn't matter. I have now this HotDogEd node connected
to uplink 2:221/6.6. ;)

Oh, a bosspoint! :-)

;-)

But we were talking about having two downlinks of the same bossnode in
one device, not with different uplinks...

The same bossnode may have multiple AKA's, like this:

2:221/6 -> point 2:221/6.123
2:221/6.1 -> point 2:221/360.8110
2:221/6.6 -> point 2:221/10.0

All these 'points' can be in the same hotdoged.

'Tommi

--- GoldED+/LNX 1.1.5-b20231008
* Origin: nntps://news.fidonet.fi (2:221/6)

14 Oct 2023 11:08, you wrote to me:

But we were talking about having two downlinks of the same
bossnode in one device, not with different uplinks...

The same bossnode may have multiple AKA's, like this:

2:221/6 -> point 2:221/6.123
2:221/6.1 -> point 2:221/360.8110
2:221/6.6 -> point 2:221/10.0

All these 'points' can be in the same hotdoged.

Yes, of course. As they are different uplinks, HotdogEd "officially" supports that.

The good thing about the "trick" of using .0 for the uplink of the second point is that a user can have two points of the same bossnode without requiring the sysop to add point AKAs to his/her system. (Of course if the user is the sysop, no problem ;-)

I currently have:

2:341/234 -> point 2:341/234.12
2:341/234.0 -> point 2:341/234.123

(As I commented before, both points must use the same password.)

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

Hello, Carlos Navarro.
On 14.10.23 9:55 AM you wrote:

Hello, Oleg Nazaroff. On 13/10/23 22:14 you wrote: Could be. I've not tested that... Is it
common to use HotdogEd with node addresses in R50? More than points?

I've used my node on HotDog only, without points, just PVT. Haven't PC or notebook and haven't seen use for it in a long time ;)

--
� ������訬� ��������ﬨ! Virtual HotDog
--- ��℮�/2.14.5/Android
* Origin: Android device, Milky Way (2:50/700)

Hello, Tommi Koivula.
On 14.10.23 9:57 AM you wrote:

Hello, Oleg Nazaroff. On 13/10/2023 22.14 you wrote: I think it doesn't matter. I have now
this HotDogEd node connected to uplink 2:221/6.6. ;)

We'v told about multi connections. I've use HotDog node connected, but this is not multiconnect ;)

--
� ������訬� ��������ﬨ! Virtual HotDog
--- ��℮�/2.14.5/Android
* Origin: Android device, Milky Way (2:50/700)

Hello, Tommi Koivula.
On 14.10.23 11:08 AM you wrote:

Hi Carlos. 14 Oct 23 09:56, you wrote to me: ;-) The same bossnode may have multiple AKA's,
like this: 2:221/6 -> point 2:221/6.123 2:221/6.1 -> point 2:221/360.8110 2:221/6.6 ->
point 2:221/10.0 All these 'points' can be in the same hotdoged.

No one has canceled gray FTN networks either, I once had a poynt to subpoynts too ;)

--
� ������訬� ��������ﬨ! Virtual HotDog
--- ��℮�/2.14.5/Android
* Origin: Android device, Milky Way (2:50/700)

Hi Oleg.

14 Oct 23 14:16, you wrote to me:

Hello, Oleg Nazaroff. On 13/10/2023 22.14 you wrote: I think it doesn't matter. I have now
this HotDogEd node connected to uplink 2:221/6.6. ;)

We'v told about multi connections. I've use HotDog node connected, but this is not multiconnect ;)

Yeah, Hotdoged is just a software with one uplink only. Node or point address, no difference. ;)

'Tommi

--- GoldED+/LNX 1.1.5-b20231008
* Origin: nntps://news.fidonet.fi (2:221/6)

Hello, Tommi Koivula.
On 14.10.23 6:51 PM you wrote:

Hi Oleg. 14 Oct 23 14:16, you wrote to me: Yeah, Hotdoged is just a software with one uplink
only. Node or point address, no difference. ;)

On the contrary, it's Aftershock that is famous for such "quality", but HotDog works fine even with twenty uplinks for one same node.

--
� ������訬� ��������ﬨ! Virtual HotDog
--- ��℮�/2.14.5/Android
* Origin: Android device, Milky Way (2:50/700)

Hi Oleg.

15 Oct 23 17:19:44, you wrote to me:

Hi Oleg. 14 Oct 23 14:16, you wrote to me: Yeah, Hotdoged is
just a software with one uplink only. Node or point address, no
difference. ;)

On the contrary, it's Aftershock that is famous for such "quality",
but HotDog works fine even with twenty uplinks for one same node.

But HotDog cannot act as a hub, that's what I tried to say. It cannot forward echomail from a node to another node.

'Tommi

---
* Origin: - rbb.fidonet.fi - Finland - (2:221/6)

15 Oct 2023 17:19, you wrote to Tommi Koivula:

Yeah, Hotdoged is just a software with one uplink only. Node or point
address, no difference. ;)

On the contrary, it's Aftershock that is famous for such "quality",

What is AfterShock famous for? I don't understand what you mean.

but HotDog works fine even with twenty uplinks for one same node.

Interesting... Yes, I see you can add several entries with same point/node address, as long as they have different uplinks...

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

Hello, Tommi Koivula.
On 15.10.23 8:30 PM you wrote:

Hi Oleg. 15 Oct 23 17:19:44, you wrote to me: But HotDog cannot act as a hub, that's what I
tried to say. It cannot forward echomail from a node to another node.

Not evening yet ;) not yet it can't. But �an his part. It always has.


--
� ������訬� ��������ﬨ! Virtual HotDog
--- ��℮�/2.14.5/Android
* Origin: Android device, Milky Way (2:50/700)

Hello, Carlos Navarro.
On 15.10.23 9:13 PM you wrote:

15 Oct 2023 17:19, you wrote to Tommi Koivula: What is AfterShock famous for? I don't
understand what you mean.

Aftershock can use only one point or node connect.

Interesting... Yes, I see you can add several entries with same point/node address, as long as
they have different uplinks...

Today i'v use four uplinks. The only inconvenience is that I can't see the addresses of the uplinks, I have to memorize their order. But i'll fix that. When more important bugs will be fixed.
Now i have an empirical problem with provider killing on MIUI and not restart, somehow related to recursive error and free memory zeroing.

--
� ������訬� ��������ﬨ! Virtual HotDog
--- ��℮�/2.14.5/Android
* Origin: Android device, Milky Way (2:50/700)