Vitold wrote (2020-11-09):

I do not exclude the possibility of using the 39th version of the
proposal in the future, but I need to make sure that this will work with my nodes.

In any case, increasing count requests about support some feature is increase chance of select one specific implementation in favor of another.

Btw, it's an FSC not an FTS.

You right. It would be convenient to have a standard that would support every tosser to support one single same coding scheme.

I compiled a list of the supported packet formats for popular tossers 4 years ago. I don't know if anything has changed since then and it might be not 100% accurate, but it looks like FSC-0039 is the standard that most tossers use for outbound packets and that every tosser can read.

| Name | Read | Write | |-------------------|------------|--------|
| Crashmail (Amiga) | 39, 45, 48 | 39 |
| Crashmail II | 39, 45, 48 | 39 |
| Daydream BBS | 39, 48 | 48 |
| FastEcho | 39, 45, 48 | 39 |
| Fidogate | 39 | 39 |
| FMail | 39, 48 | 39 |
| GEcho | 39, 45, 48 | 39 |
| Husky hpt | 39, 48 | 39 |
| ifmail | 39 | 39 |
| LoraBBS | 39, 45 | 39 |
| MBSE | 39 | 39 |
| Mystic | 39, 48 | 39 |
| OpenXP | 39 | 39 |
| SBBSecho | 39, 45, 48 | 45, 48 |
| Soupgate | 39 | 39 |
| Squish | 39 | 39 |
| Watergate | 39, 48 | 39 |
| WWIV BBS v5 | 39 | 39 |

I review ASCII version of PKTv3 format with the text data representation, since there is less bit field hacks, but as far as I understand today, there are no tossers with this coding scheme support.

I don't know any tosser that support PKTv3. If there is a need for a better packet format, I would start with a new proposal for a sane binary format. ASCII formats are usually harder to parse than a clean binary format.

I guess it would be better to discuss stuff like this in NET_DEV.

---
* Origin: (2:280/464.47)

Oli wrote:

I compiled a list of the supported packet formats for popular tossers 4 years ago.
I don't know if anything has changed since then and it might be not 100% accurate,
but it looks like FSC-0039 is the standard that most tossers use for outbound
packets and that every tosser can read.

| Name | Read | Write | |-------------------|------------|--------|
| Crashmail (Amiga) | 39, 45, 48 | 39 |
| Crashmail II | 39, 45, 48 | 39 |
| Daydream BBS | 39, 48 | 48 |
| FastEcho | 39, 45, 48 | 39 |
| Fidogate | 39 | 39 |
| FMail | 39, 48 | 39 |
| GEcho | 39, 45, 48 | 39 |
| Husky hpt | 39, 48 | 39 |
| ifmail | 39 | 39 |
| LoraBBS | 39, 45 | 39 |
| MBSE | 39 | 39 |
| Mystic | 39, 48 | 39 |
| OpenXP | 39 | 39 |
| SBBSecho | 39, 45, 48 | 45, 48 |
| Soupgate | 39 | 39 |
| Squish | 39 | 39 |
| Watergate | 39, 48 | 39 |
| WWIV BBS v5 | 39 | 39 |

It look like 39-th proposal most popular than each other.
I think that I should come back on 39-th proposal.

But it may take a few days or even week to revert code back
and perform "Parma Tosser" compatibility checks.

Also I will check with HPT. If some one can help me with
checks on another one tossers it will be awsome.

I don't know any tosser that support PKTv3.
ASCII formats are usually harder to parse than a clean binary format.

Right now I complete TIC build/parse in 1.2.16 and found it well debugging
and well human readable. It good advantage on debugging of course ;)

I think ASCII format may by well designed and does not harder than binary.
I assume binary provide speed and memory advantages.

I guess it would be better to discuss stuff like this in NET_DEV.

I already got caught up in the poisonous debate at RU.FIDONET.TODAY

I propose make screencast video reviews on GP instead write documentation and announced idea replace UUE image in place. As a result, I lost my home time, review thausend reasons use or avoid to use this features and ruined my mood.

I am sure many people will find hundreds of reasons to use or escape use various
feature and packing structure scheme and I want to avoid participating in such debates. I does not see essential complexity for consumers and see increase accidental complexity instead.

I see in your statistics report that most tosser system already use 39-th proposal and by compatible reason I will implement it.

P.S. May I mention your name “Oli” in the Golden Point contributors list
as thanks for clarification of the most popular standards for me?

--- Golden/Windows-amd64 1.2.16 2020-11-03 23:07 MSK (master)
* Origin: Если дружишь с хромым, сам начинаешь прихрамывать (2:5030/1081.102)

I compiled a list of the supported packet formats for popular tossers ...

| Name | Read | Write | |-------------------|------------|--------|
| Crashmail (Amiga) | 39, 45, 48 | 39 |
| Crashmail II | 39, 45, 48 | 39 |
| Daydream BBS | 39, 48 | 48 |
| FastEcho | 39, 45, 48 | 39 |
| Fidogate | 39 | 39 |
| FMail | 39, 48 | 39 |
| GEcho | 39, 45, 48 | 39 |
| Husky hpt | 39, 48 | 39 |
| ifmail | 39 | 39 |
| LoraBBS | 39, 45 | 39 |
| MBSE | 39 | 39 |
| Mystic | 39, 48 | 39 |
| OpenXP | 39 | 39 |
| SBBSecho | 39, 45, 48 | 45, 48 |
| Soupgate | 39 | 39 |
| Squish | 39 | 39 |
| Watergate | 39, 48 | 39 |
| WWIV BBS v5 | 39 | 39 |

Night version of Golden Point switch back on FTS-0039.

I check complete on Partoss and HPT.

Thanks.

--- Golden/Windows-amd64 1.2.16 2020-11-03 23:07 MSK (master)
* Origin: Если дружишь с хромым, сам начинаешь прихрамывать (2:5030/1081.102)