How exactly does the hatch feature work on mystic? Once file is marked for hatching it automatically gets sent to the nodes on the network? Thanks

--- Mystic BBS v1.12 A34 (Windows/64)
* Origin: Necronomicon BBS - necrobbs.strangled.net (21:1/122)

How exactly does the hatch feature work on mystic? Once file is marked for hatching it automatically gets sent to the nodes on the network? Thanks

When you mark a file to be hatched, it will be flagged by Mystic, and the next time you run MUTIL's [FileToss] function to process incoming TIC files, it will also "hatch" anything flagged. This will create a .TIC and copy the file to each node's filebox that is "linked" to the file area where the file was hatched.

When you speak with the node next (either they call you or you call them) it will send the contents of their filebox - thus sending the .TIC and the file. The exception to this is if the node's filebox is set to "Hold" then it will only send the files when they connect to you.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

So , let's say I have a nodelist to send for
My network. I would hatch that file and it would send to all downlinks? Is
that basically what hatching is for.

Mystic already auto tic/toss incoming tic and files for networks you are connected to right? So hatching would have nothing to do with that?

On 04:40 25/06 , g00r00 wrote:

How exactly does the hatch feature work on mystic? Once file is marked for hatching it automatically gets sent to the nodes on the network? Thanks

When you mark a file to be hatched, it will be flagged by Mystic, and the next >time you run MUTIL's [FileToss] function to process incoming TIC files, it will
also "hatch" anything flagged. This will create a .TIC and copy the file to >each node's filebox that is "linked" to the file area where the file was >hatched.

When you speak with the node next (either they call you or you call them) it >will send the contents of their filebox - thus sending the .TIC and the file. >The exception to this is if the node's filebox is set to "Hold" then it will >only send the files when they connect to you.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A33 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

When you mark a file to be hatched, it will be flagged by Mystic, and
the next time you run MUTIL's [FileToss] function to process incoming
TIC files, it will also "hatch" anything flagged. This will create a
.TIC and copy the file to each node's filebox that is "linked" to the
file area where the file was hatched.

Thanks for your response g00r00

--- Mystic BBS v1.12 A34 (Windows/64)
* Origin: Necronomicon BBS - necrobbs.strangled.net (21:1/122)

So , let's say I have a nodelist to send for
My network. I would hatch that file and it would send to all downlinks?
Is that basically what hatching is for.

Mystic already auto tic/toss incoming tic and files for networks you are connected to right? So hatching would have nothing to do with that?

They are both parts of a functioning file-network:

Incoming files with their .TIC are processed and added to your file bases,
and if there are any systems connected to that file base then those systems will be sent the a .TIC and the file.

What hatching does is it allows you to send files from your BBS to all of the systems linked to that file base. So yes, if you had a nodelist in that file base and you wanted to send it to every system linked to that file base, you would hatch that file...

Once that file is marked to be hatched, MUTIL's TIC processor will create the TIC and send the file to all of the systems the next time it's ran.

Keep in mind that for file networks to work, each configured "echomail node" that connects to you (or you connect to) has to have their "filebox" enabled in the settings...

This is basically a temporary "holding" directory for files that need to be sent to those systems. Mystic will offer to generate the directory for you when you set "Use Filebox" to either "Yes" or "Hold" in the node's configuration, if the filebox directory is blanked out.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Got it

On 08:59 25/06 , g00r00 wrote:

So , let's say I have a nodelist to send for
My network. I would hatch that file and it would send to all downlinks? Is that basically what hatching is for.

Mystic already auto tic/toss incoming tic and files for networks you are connected to right? So hatching would have nothing to do with that?

They are both parts of a functioning file-network:

Incoming files with their .TIC are processed and added to your file bases, >and if there are any systems connected to that file base then those systems >will be sent the a .TIC and the file.

What hatching does is it allows you to send files from your BBS to all of the >systems linked to that file base. So yes, if you had a nodelist in that file >base and you wanted to send it to every system linked to that file base, you >would hatch that file...

Once that file is marked to be hatched, MUTIL's TIC processor will create the >TIC and send the file to all of the systems the next time it's ran.

Keep in mind that for file networks to work, each configured "echomail node" >that connects to you (or you connect to) has to have their "filebox" enabled in
the settings...

This is basically a temporary "holding" directory for files that need to be >sent to those systems. Mystic will offer to generate the directory for you >when you set "Use Filebox" to either "Yes" or "Hold" in the node's >configuration, if the filebox directory is blanked out.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A33 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

So, to clarify, to send ANYTHINg, rather a tic processed and sent or
something I hatch, I have to configure file boxes?

Awesome work on auto creating the boxes too, man that saves time.



On 08:59 25/06 , g00r00 wrote:

So , let's say I have a nodelist to send for
My network. I would hatch that file and it would send to all downlinks? Is that basically what hatching is for.

Mystic already auto tic/toss incoming tic and files for networks you are connected to right? So hatching would have nothing to do with that?

They are both parts of a functioning file-network:

Incoming files with their .TIC are processed and added to your file bases, >and if there are any systems connected to that file base then those systems >will be sent the a .TIC and the file.

What hatching does is it allows you to send files from your BBS to all of the >systems linked to that file base. So yes, if you had a nodelist in that file >base and you wanted to send it to every system linked to that file base, you >would hatch that file...

Once that file is marked to be hatched, MUTIL's TIC processor will create the >TIC and send the file to all of the systems the next time it's ran.

Keep in mind that for file networks to work, each configured "echomail node" >that connects to you (or you connect to) has to have their "filebox" enabled in
the settings...

This is basically a temporary "holding" directory for files that need to be >sent to those systems. Mystic will offer to generate the directory for you >when you set "Use Filebox" to either "Yes" or "Hold" in the node's >configuration, if the filebox directory is blanked out.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A33 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

So, to clarify, to send ANYTHINg, rather a tic processed and sent or something I hatch, I have to configure file boxes?

Awesome work on auto creating the boxes too, man that saves time.

Yes every node has to have a "filebox" directory if you want to be able to send files to them in a file-network. When you have a filebox set up for an echomail link, any file you put into their filebox will be sent to them the next time your two systems speak.

Sort of like how your BBS requires an "incoming" directory for your echomail, each BBS you send to for files needs its own directory to store the data that needs to be sent to it.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

No wonder it wasn't working lol.

On 12:22 25/06 , g00r00 wrote:

So, to clarify, to send ANYTHINg, rather a tic processed and sent or something I hatch, I have to configure file boxes?

Awesome work on auto creating the boxes too, man that saves time.

Yes every node has to have a "filebox" directory if you want to be able to send
files to them in a file-network. When you have a filebox set up for an >echomail link, any file you put into their filebox will be sent to them the >next time your two systems speak.

Sort of like how your BBS requires an "incoming" directory for your echomail, >each BBS you send to for files needs its own directory to store the data that >needs to be sent to it.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A33 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

Nugax wrote to All <=-

So, to clarify, to send ANYTHINg, rather a tic processed and sent or something I hatch, I have to configure file boxes?

Yes.

Awesome work on auto creating the boxes too, man that saves time.

I didn't know that, is it a new feature g00r00? I do mine manually, but have a standard that is:

/mystic/filebox/domain/node, which makes finding my fileboxes easy. I don't have a need to put zone and net in my directory tree.


... Let the meek inherit the Earth, I want the stars.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

I didn't know that, is it a new feature g00r00? I do mine manually, but have a standard that is:

/mystic/filebox/domain/node, which makes finding my fileboxes easy. I don't have a need to put zone and net in my directory tree.

Yes, its in the whats new for A34. But its

/mystic/filebox/domain_z<zone>n<net>n<node>/ and p<point> if its a point

It doesn't automatically create them, but in the configuration when you
switch from "No" to either "Yes/Hold" for the filebox, it will offer to
assign and create the folder if one is not already set.

I am open to suggestions from everyone if anyone has anything to add to the
way it works. I didn't think to do them in a domain directory but maybe that is a better idea.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

g00r00 wrote to Vk3jed <=-

I am open to suggestions from everyone if anyone has anything to add to the way it works. I didn't think to do them in a domain directory but maybe that is a better idea.

What about letting the sysop define the template for the path. That way, I could keep my structure, but make use of the automatic path name generation.


... A visit to a strange place will bring fresh work.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

Or just give us a couple choices to choose from. I like his idea better.
Easier to read.

On 10:53 26/06 , Vk3jed wrote:

g00r00 wrote to Vk3jed <=-

I am open to suggestions from everyone if anyone has anything to add to the way it works. I didn't think to do them in a domain directory but maybe that is a better idea.

What about letting the sysop define the template for the path. That way, I >could keep my structure, but make use of the automatic path name generation.

... A visit to a strange place will bring fresh work.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A33 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)