tosser

RM> tell me, does it make sense to sculpt a real hub tosser for the zx? I've actually been on the
RM> point system for a month now. do you need a node? I
RM> I’m only talking about the tosser-scanner-editor.

It wouldn’t hurt to complete the picture and sensations.

RM> thoughts are as follows: download mail from the terminal in the form of unpacked pkt.

Better, after all, IMHO:

RM> then life becomes even simpler for the boss. from his point of view point on the spec
RM> will look completely adequate, it will just use
RM> a non-standard archiver.

RM> and that’s it. Does anyone need all this?...

Judging by the fact that several groups in different
parts of the country are now trying to do this, it is necessary.

Andrew
P.S. Actually, postal technology personally doesn’t interest me much at the moment, since the question of what it should “sit on” has not been really resolved. IsDOS would be good, but it has problems with memory and Java. TR-DOS has problems with access and volume, CP/M has problems with subdirectories and with Scorpio hardware/software.
In short, the more the better...

It is this cheerful trinity that is extremely lacking in our SpbZxNet..

RM> and in general, it would be interesting to discuss the problem with the transport of live Fido
RM> to
RM> zx. My zed works with standard pkt, both at the input and at the
RM> output. When dragging mail from your own site at work on floppy disks
RM> problems do not arise at all. but This is probably not accessible to everyone.

RM> thoughts are as follows: download mail from the terminal in the form of unpacked pkt. advantages -
RM> minimum body movements. received - read - wrote - sent. cons -
RM> some strain for the boss. he will have to 1) hold for the point
RM> an unpacked archmail,

change 1 point in the fast....

RM> 2) send the outbound to a place accessible to the terminal,

how to send two bytes..

RM> 3) push the inbound that came from the point into accessible for tosser
RM> place.

see above

RM> if the boss is not lazy, everything can be solved Elementarily and automatically.

Now I have a much more crap
system working automatically: a fictitious link has been created for the gate, a home-made converter from RCT to text is attached as a packer to the fast format adopted by SpbZxNet,
which also shifts the outbound to a place accessible to
the synclerist-gateway operator. Return mail is processed about the same...

RM> second thought. ftn mailer even on zx'48 is a completely real thing. more

This, of course, is also necessary, but IMHO the tosser-scanner-editor is first and foremost...

[skipped]

RM> the last thought, not a fun one. use vehicles
RM> of all kinds of zx-net, and gate in Fido en masse. not fun because
RM> Fido will remain inaccessible to those who sit where these zx-net "s
RM> do not exist.

But! if they already exist (as we have in St. Petersburg, for example), then it is even
more convenient, because access to FIDO is given even to those who do not even have a modem, but only one
transformer....

RM> for zx?

of course!

RM> I’ve been on the point system for a month, actually
RM>. do you need a node?

and was silent... :(
listen, are you writing programs for yourself? :(

RM> I'm only talking about
RM> tosser-scanner-editor.

but this is rulez forever in one word!!!!
you'll throw it? ;)

RM> zx-nets do not exist.

So you seem to have thought of everything... But the first two methods are suitable for owners of
Hayes, while on Spectrum modems incompatible with the
mentioned ones are more widespread... Therefore, I personally “like” the latter more, compatible
with the existing situation of zxnets. But it’s not clear why gate
en masse... It’s like - through one node, or what? Moreover, sometimes Fido is the “vehicle
of all kinds of zxnet” ;)

It is necessary!

RA> It is extremely necessary!!! Personally, for me, the method of transmission and data format in
RA> SpbZxNet causes alternately laughter and tears (no offense
RA> SpbZxNet-sheep
RA> will be said), and besides, a bunch of errors in the execution of correspondence,
RA> translation of SpbZxNet to a normal FTN-compatible The format would solve a lot of
RA> problems...

For me, the INTERNET is simpler: the user sends a text file, the first line
of which is the recipient's address. At the end of the same letter file, after the sign
"*" at the beginning of the line, application files are listed (if any. This is necessary for
the recipient).

All this, after completing the communication session with the Spectrum BBS via LPT
is automatically transferred to the PC. There the first line of the letter is analyzed, an archive
file is created and sent to the specified address. The separators between packages are
text files. Those. if there is text between the program files, an attempt will be made to analyze a new text file with the recipient's address.

Hemorrhoids begin when the user encircles the address part of the letter with a frame of pseudographics... You can, of course, correct it, but you need to educate ;) Otherwise there will be a
clever who will circle the address not with pseudographics, but with the letters "F", for example... I have two such letters on the Spectrum days are stuck: the machine does not recognize them, butI rarely look at disks...

Also a problem: text files are analyzed (we have ZXWord). If the software
is also accompanied by a description in a text file, in order to avoid misunderstandings
the user must change the file type to something other than “W”.

Sincerely, Alexey Ivanov