Hello All!

What is new in FidoMail Mobile 0.1.12+94:

Setup:

- The program can now work as a node, not only as a point. The
"Set up Fidonet" wizard asks "Point" or "Node"; for a node you
enter its address, and the program works with the uplink the same
way a point works with its boss. Echomail written from a node
address carries SEEN-BY and PATH lines, as FTS-0004 requires.

Reading:

- Geek Code support: if a message carries one (the GC kludge, a
"BEGIN GEEK CODE BLOCK" in the text, or a @GC: line), the message
header gets a "Geek:" line. Tap it to see what the code means.
- The message counter in the reader header: while the echo has
unread messages it shows unread/total, as before. Once everything
is read, it shows the number of the open message, "425 of 439".
- "Mark all read" now takes you to the newest message, so you no
longer have to scroll or press the jump button afterwards.

Writing:

- A new "Add greeting and signature" checkbox in the message editor.
Untick it and this one message goes out without the greeting and
the signature. Useful for AreaFix requests written by hand: some
robots read a signature line as one more command.
- On Android and iOS, the attach menu has "Choose from gallery...".
- Quoting a line that starts with ">" now gives ">>", as other
FidoNet editors do, not "??>>".

Compatibility:

- Fixes in the binkp implementation for better compatibility with
Synchronet and BeeMail.
- The jNode AreaFix robot is now recognised.

Download: https://fidomail.5001.ru
On Android: About -> Check for updates.

--- FidoMail v0.1.4-150-gcf791f6e
* Origin: Dmitry Protasoff (2:5001/100)

Hello, Dmitry!

Dmitry Protasoff wrote:

- The program can now work as a node, not only as a point.

Can it accept incoming calls? If not, it does not qualify for node status. IMNSHO....

Cheers, Michiel

--- FidoMailMobile/0.1.11+92 (iOS)
* Origin: Michiel's iPhone (2:280/5555.6)

Hey Michiel!

On Sun, Sep 27 2026 17:21:16 +0200, you wrote:

- The program can now work as a node, not only as a point.

Can it accept incoming calls? If not, it does not qualify for node
status. IMNSHO....

Wouldn't it just be a PVT node then?

What /is/ the difference between a PVT node and a point, besides usage of point addressing, and the fact that points aren't listed in the normal nodelist (legit question, I've always wondered the difference between the two)? Or was it just something done differently geographically?

- Both need a feed; one calls that feed a boss node, one doesn't.
- Both are not publicly accessible.

Is the only difference the fact that a PVT node /could/ technically be a publicly accessible node, but prefers to not list connection details?

Regards,
Nick

... Take my advice, I don't use it anyway.
--- AmberEdit/linux 0.9.0
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hello Michiel!

In a message of 27 Sep 26 17:21, Michiel wrote to Dmitry:

MvdV> Can it accept incoming calls? If not, it does not qualify for
MvdV> node status. IMNSHO....

It's already used by at least 1 node. It's actually impossible to make a program work 24/7 on modern Android/iOS — the only way is to create some server proxy, which will send a push notification to wake it up from sleep on every connection.

But it's still possible to have a node with email-only connection:

https://nodelist.fidonet.cc/analytics/email?only=email

And it's not even considered a Pvt node! That's gonna be implemented eventually.


See you,
dp.
--- FidoMail v0.1.4-158-g923dab08
* Origin: livin' on the edge (2:5001/100)

Hello Nick,

On 27 Sep 26 11:04, you wrote to me:

- The program can now work as a node, not only as a point.

Can it accept incoming calls? If not, it does not qualify for
node status. IMNSHO....

Wouldn't it just be a PVT node then?

Exactly!

What /is/ the difference between a PVT node and a point, besides usage
of point addressing, and the fact that points aren't listed in the
normal nodelist (legit question, I've always wondered the difference between the two)? Or was it just something done differently geographically?

The difference is in status. The status of the operator of a point system is clear. He/she is not a fidonet sysop. He/she is a user om the system of the Boss node.

From a PVT node the status is less clear. I say Fidonet is a peer to peer network, so the ability to accept incoming calls is an essential part. You can not maintain a network without systems that accept incoming calls. Nodes that can or will not not accept incoming calls, are taking a free ride on those that can and do.

In the past there were justifications for such systems. Such as "sponsored" nodes that were behind a private branch exchanges. They could make outgoing calls, and distribute mail, to the benefit of the network, while diverting the cost... With the side note that ever so often the one paying the cost was not made aware of it.

That does not hold in the age of FOIP any more. The coast of distributing mail is praticall zero, so there no longer is any benefit to the network from such PVT nodes.

- Both need a feed; one calls that feed a boss node, one doesn't.
- Both are not publicly accessible.

Ever so often they are not privatly accesable either these days. In the old days, points used the same mail software as nodes, but they didn't have a dedicated phone line for it. Later we got special point software that could only make outgoing calls. Such as Winpoint.

One of the problems with systems that do not accept incoming calls is that there is no way to verify if they actually exist. Does a PVT node really exist or is it just nodelist stuffing? It can and has been abused in the past.

Anyway, my POV is that in the age of FOIP, we should no longer have PVT nodes. Systems that can or will not accept incoming calls should be points.


Cheers, Michiel

--- GoldED+/W32-MINGW 2.0.0-b20260917
* Origin: Nieuw Schoord (2:280/5555)

Hello Dmitry,

On 27 Sep 26 18:17, you wrote to me:

MvdV>> Can it accept incoming calls? If not, it does not qualify for
MvdV>> node status. IMNSHO....

It's already used by at least 1 node.

I know and I don't like it.

It's actually impossible to make a program work 24/7 on modern
Android/iOS — the only way is to create some server proxy, which will send a push notification to wake it up from sleep on every connection.

I know. And even it it were possible to run a true server on an iPhone or android phone, there would still be the problem of mobile providers putting clients behind CGNAT for IPv4 and blocking IPv6 on incoming. So it would only work when the "node" is connected to the home network and that would go against being "mobile".

But it's still possible to have a node with email-only connection:

https://nodelist.fidonet.cc/analytics/email?only=email

I know and I don'like it either. With binkd you have at least confirmation that the mail package was accepted by the system. With e-mail you mostly have not.

And it's not even considered a Pvt node! That's gonna be implemented eventually.

I say, systems that can not or will not accept incoming calls should be points, not nodes.


Cheers, Michiel

--- GoldED+/W32-MINGW 2.0.0-b20260917
* Origin: Nieuw Schoord (2:280/5555)

Hello Michiel!

In a message of 28 Sep 26 22:02, Michiel wrote to Dmitry:

It's already used by at least 1 node.

MvdV> I know and I don't like it.

It's a coordinator's job to prevent such cases, I can't stop people from doing so, but just I have to ensure that software correctly handles kludges.

MvdV> I know and I don'like it either. With binkd you have at least
MvdV> confirmation that the mail package was accepted by the system.
MvdV> With e-mail you mostly have not.

It should have delivery receipt support, but again — it's not in my power to force anyone to do anything ;)

And it's not even considered a Pvt node! That's gonna be
implemented eventually.

MvdV> I say, systems that can not or will not accept incoming calls
MvdV> should be points, not nodes.

see above ;)

See you,
dp.
--- FidoMail v0.1.4-166-geba1145b
* Origin: livin' on the edge (2:5001/100)

Hey Michiel!

On Mon, Sep 28 2026 21:38:40 +0200, you wrote:

Anyway, my POV is that in the age of FOIP, we should no longer have PVT nodes. Systems that can or will not accept incoming calls should be points.

Thanks for your point of view (pun intended). I suppose it kind of gave me perspective, but.. it still seems they're basically the same thing with small differences. The "status" part is definitely an actual difference, though.

In my case, I run a full functioning hub that does all the FTN related stuff separate of my BBS. Then, I have my BBS which is a PVT node that runs on the same server. I never wanted two mailers running on the same machine, so I set it up to poll my hub for mail. It's easily reachable via just about any other method besides an FTN mailer.

I suppose I could change it to be a point, but why?

Regards,
Nick

... I don't suffer from insanity; I enjoy every minute of it.
--- AmberEdit/linux 0.9.0
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hello, Dmitry!

Dmitry Protasoff wrote:

- On Android and iOS, the attach menu has "Choose from gallery...".

In the Dutch version: I suggest to replace "Kiezen uit galerij" by "Fotobibliotheek".

That is the term used bij iOS in other mail apps.

Cheers, Michiel

--- FidoMailMobile/0.1.12+94 (iOS)
* Origin: Michiel's iPhone (2:280/5555.6)

Hello Michiel!

In a message of 29 Sep 26 08:19, Michiel wrote to Dmitry:

MvdV> In the Dutch version: I suggest to replace "Kiezen uit galerij"
MvdV> by "Fotobibliotheek".

Noted!

See you,
dp.
--- FidoMail v0.1.4-169-g4ad55619
* Origin: livin' on the edge (2:5001/100)

Hello Nick,

On 28 Sep 26 17:40, you wrote to me:

Anyway, my POV is that in the age of FOIP, we should no longer
have PVT nodes. Systems that can or will not accept incoming
calls should be points.

Sorry for the late response. Real life got in the way...

Thanks for your point of view (pun intended). I suppose it kind of
gave me perspective, but.. it still seems they're basically the same
thing with small differences. The "status" part is definitely an
actual difference, though.

Noted.

In my case, I run a full functioning hub that does all the FTN related stuff separate of my BBS. Then, I have my BBS which is a PVT node that runs on the same server. I never wanted two mailers running on the
same machine, so I set it up to poll my hub for mail. It's easily reachable via just about any other method besides an FTN mailer.

I suppose I could change it to be a point, but why?

I can't help you with that question because I do not understand your setup. You say you have a full functioning hub. I guess you refer to 1:154/10. But there is no hub keyword there. So what is it hubbing for?

In the old DOS/POTS age (single uer/single task) I could imagine the need for running the mail system and the BBS as different systems. But in the age of multi-user multi-tasking there in no longer such a need. The BBS can run in parallel with the mailer on the same system and the sysop can edit his own messages while the BBS and the mailer keep running.

So why the need/want for 154/700 in the first place? Why a sperate node number for the BBS? And if so why Pvt? A BBS that is not publically reachable, what is the idea behind that? I don't get it.

If you want to let it rest, that's fine with me. It is getting a bit off-topic anyway...


Cheers, Michiel

--- GoldED+/W32-MINGW 2.0.0-b20260917
* Origin: Nieuw Schoord (2:280/5555)