On 08/11/2020 5:29 p.m., Vitold Sedyshev : Richard Menedetter wrote:

I tried it out, and like the concept very much ;)

It's incredibly good to hear that.

[snip]

..This is a very interesting experience anyway. But I developed> it as toys point packet for first steps with FidoNet.

Any screenshots on what this golden baby looks like?

--- TB(Stealth)/Win7
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)

Any screenshots on what this golden baby looks like?

You may watch review video at https://www.youtube.com/watch?v=EzgrGuEMzVY

But video over 1.2.10 version (i.e. 6 versions ago) and you may
change language of subtitles to English for understand what I talk about.

I received a lot of abuse comment about the video reviews. I actually found short video review to be very helpful, but most people prefer to see text documents, so I get small pause with recording video reviews.

If the video review found its own conumers, then I will resume recording reviews.
But now it directly depends on the feedbacks.

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

FSC-0048 is mostly useless nowadays and only adds complexity.

You right. Using auxNet and check magic value 65535 and check origPoint != 0
it look like some kind of data hacks.

Practically every tosser supports FSC-0039

I start write source code with idea about implementing PKTv3 packets but no nodes with supports in Russia zone as I know.

I debugging GP source code with make checks with "Parma Tosser" and review Parma source code I make compatible GP with my BOSS node. I assume Parma Tosser compatible with
FSC-0001, FSC-0048 and FSC-0045 bases on my source code vision.

I also have another one point address on 5030/1081 node. Here an extremely strange case with crash Husky Tosser (HPT) on the 39th proposal occurred and we research with BOSS this incendent and did not understand what it was refered with, so for now I am switch on using the 48th proposals.

So it is at now very difficult to understand and there is a danger of losing data about the zone and point by returning back on FSC-0001 compatible mode.

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 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.

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

Vitold wrote (2020-11-08):

I managed to send a test message from the point to the boss node.
But at first it did not receive anything.

We are now discussing the default standard and it becomes FTS-0048 since 1.2.16 Also most people want to manual mailer manage instead auto 5 min. dialing. In any case in settings in 1.2.16 it already implemented.

FSC-0048 is mostly useless nowadays and only adds complexity. Practically every tosser supports FSC-0039, the compatibility thing is a non-issue. And there are only very few tossers that support FSC-0048. FSC-0045 would make more sense, because it supports domains too (but it's also not really an issue).

Btw, it's an FSC not an FTS.

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

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)

Hi Vitold!

09 Nov 2020 00:39, from Vitold Sedyshev -> Richard Menedetter:

When I go to Filebox settings I get a 404 error.

Hmm... Could you please see *debug.log* about error? I may assume that wrong directory but you may wait 1.2.16. Since 1.2.16 no more
directory setup and use smart directory searching.

1.2.16 works

PS: Could you change this "Mailer interval".
Either add (minutes) or even better change to "Polling interval in minutes"

Also I would like to be able to delete files in Fileboxes.

Works in 1.2.16

Tree view if echomail seems not to work.
I had a look at this echo, and it shows all messages on the same level.

When I try to view a file from a filebox, I get this error:
Fail on open source C:\Users\ricsi\Fido\Files\Z2PNT\Z2PNT.Z18
turns out the correct directory would be FileBox instead of Files. (Files exists but is empty.)

PS: You could make Golden Point on the home screen a link to the Github project.

CU, Ricsi

... Patience is the ability to put up with people you'd like to put down.
--- GoldED+/LNX
* Origin: Question authority ... ask me anything. (2:310/31)

Richard wrote:

Could you change this "Mailer interval".
Either add (minutes) or even better change to "Polling interval in minutes"

Fixed. You may get it in the nightly version or in the next build 1.2.17

Tree view if echomail seems not to work.
I had a look at this echo, and it shows all messages on the same level.

Hmmm... Do you use last night's version or 1.2.16 release?
My UTF-8 message trees at https://imgur.com/a/lZwMagv

Fail on open source C:\Users\ricsi\Fido\Files\Z2PNT\Z2PNT.Z18
turns out the correct directory would be FileBox instead of Files. (Files exists but is empty.)

Hmmm. It looks like a bug. At 1.2.15 I create in database path for FileBox on the variable name FileBox and use it for FileEcho now I use "Files" instead.

Could you please rename (move all file inside) "FileBox" into "Files".

I have no plan right now to implement FileBox.

You could make Golden Point on the home screen a link to the Github project.

Great idea. Why not. I do it in 1.2.17 version.

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

Hi Vitold!

15 Nov 2020 01:39, from Vitold Sedyshev -> Richard Menedetter:

Tree view if echomail seems not to work.
I had a look at this echo, and it shows all messages on the same
level.

Hmmm... Do you use last night's version or 1.2.16 release?
My UTF-8 message trees at https://imgur.com/a/lZwMagv

Yes ... I was using it.
Now it DOES work.
Before it was completely flar, now it is a tree.
Maybe I used it before the first new toss with 1.2.16??
Anyway, works now, thanx!

CU, Ricsi

... I have a lot of faith in the sterilizing effect of deep frying.
--- GoldED+/LNX
* Origin: It's not hard to meet expenses, they're everywhere. (2:310/31)

Hi Vitold!

15 Nov 2020 01:39, from Vitold Sedyshev -> Richard Menedetter:

Forgot something:

Could you please rename (move all file inside) "FileBox" into "Files".

Works now.
You might rename the menu entry from filebox to files too.

Also it would be nice if there were 2 new setup options.
1 for the default charset (that can be overwritten later per echo)
and 1 for the TZUTC kludge.

CU, Ricsi

... You're not making any sense; is it time for your medication or mine?
--- GoldED+/LNX
* Origin: Go to bed. You have done enough damage today. (2:310/31)

Richard wrote:

Tree view if echomail seems not to work.

My UTF-8 message trees at https://imgur.com/a/lZwMagv

Maybe I used it before the first new toss with 1.2.16?

Yep. It looks like your database populate by pre-release 1.2.16
without msgReply parsing. Since some commit in 1.2.16 it starts
processing and populating.

Anyway, works now, thanx!

Good.

--- Golden/Windows-amd64 1.2.17 2020-11-15 01:46 MSK (master)
* Origin: Самый надежный друг - это мое любимое дело (2:5030/1081.102)

Could you please rename (move all file inside) "FileBox" into "Files".

Works now.

Good.

You might rename the menu entry from filebox to files too.

Oh, exactly. Renamed right now.

Also it would be nice if there were 2 new setup options.

1 for the default charset (that can be overwritten later per echo)
and 1 for the TZUTC kludge.

1. https://github.com/vit1251/golden/issues/113
2. https://github.com/vit1251/golden/issues/114


--- Golden/Windows-amd64 1.2.17 2020-11-15 01:46 MSK (master)
* Origin: Самый надежный друг - это мое любимое дело (2:5030/1081.102)

Hello Vitold,

orig.message to echo UTF-8 on 02 Nov 20 20:52:58

Если удалось прочитать это сообщение, то напишите в ответ ✌ ✍

Тэг UUID это шикарно, а то мало мусора в тэгах. Ограничение MSGID 4 миллиарда сообщений в эхе от 1 адреса жмёт? Если его инкрементировать, а не использовать seconds since epoch

Sergey

... vim
--- PyFTN
* Origin: fluid.fidoman.ru (2:5020/12000)