Can you look to add ACS options to allow a sysop to specify the ID of a
message base and/or a file base

So much like we can currently do with message groups and file groups but
taking things down a level to something even more granular?

Best, Paul

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Can you look to add ACS options to allow a sysop to specify the ID of a message base and/or a file base

So much like we can currently do with message groups and file groups but taking things down a level to something even more granular?

Can you give me an example of how this might be used? This is something I could add, but I do have a limited number of "letters" left for the ACS
system, so I want to feel like its a good usage.

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

On 10/22/17, g00r00 pondered and said...

So much like we can currently do with message groups and file groups taking things down a level to something even more granular?

Can you give me an example of how this might be used? This is something
I could add, but I do have a limited number of "letters" left for the ACS system, so I want to feel like its a good usage.

Darn it, it was ages ago when I wrote this, when I recall why I'll post a follow up :)

Best, Paul

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 10/22/17, g00r00 pondered and said...

Can you look to add ACS options to allow a sysop to specify the ID of message base and/or a file base

So much like we can currently do with message groups and file groups taking things down a level to something even more granular?

Can you give me an example of how this might be used? This is something
I could add, but I do have a limited number of "letters" left for the ACS system, so I want to feel like its a good usage.

I recall now.

The situation I am trying to navigate is to be able to give someone on my BBS the ability to upload and hatch a file but only to a specific file base. I
can state the user ID via ACS and file group e.g. z6 but not restrict it down to a given file base(s).

I confess the combination of trying to decide what ACS to set where to
achieve such a goal is also a tad confusing for my muddled 'morning time'
brain :)

As I look at it I need to consider the Hatch ACS and Sysop ACS in a given
file base and then because the only place in Mystic that I can find 'Hatch' functionality is in the Sysop File List Editor then I need to also drill down to that commands ACS and set something there. And assuming I do it correctly
I can only lock things down to a file group not the specific file bases.

So far I have net been able to get that working correctly either. But have
not spent too much time on it as yet. Probably my ACS coding is wonky. I'm using settings like s255|u777z6

With respect to message bases I concede the use of flags would likely do the trick without the need to specify message base ID. But I personally would prefer to specify by ID for both files and messages... it feels far more targeted than assigning flags that may mean differing things over time vs an base ID # that remains fixed.

Best, Paul

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Can you give me an example of how this might be used? This is someth I could add, but I do have a limited number of "letters" left for the system, so I want to feel like its a good usage.

Darn it, it was ages ago when I wrote this, when I recall why I'll post a follow up :)

Hah, sorry about that. I've been weeks behind! I just got caught up tonight.

I also think I fixed the two echomail related issues you found, and you can test it if you'd like by downloading the updates for Windows at:

www.mysticbbs.com/downloads/prealpha

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

As I look at it I need to consider the Hatch ACS and Sysop ACS in a given file base and then because the only place in Mystic that I can find 'Hatch' functionality is in the Sysop File List Editor then I need to
also drill down to that commands ACS and set something there. And

The idea behind Hatch ACS is that users who meet that requirement will be able to (H)atch a file right from within the file listing so that will solve your issue once that is implemented.

So far I've only added it into the file listing editor, but it will be also added directly into the listings.

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

On 10/22/17, g00r00 pondered and said...

The idea behind Hatch ACS is that users who meet that requirement will
be able to (H)atch a file right from within the file listing so that
will solve your issue once that is implemented.

So far I've only added it into the file listing editor, but it will be also added directly into the listings.

OK gotcha... well that would be a good thing to sneak in to the upcoming releases when you're able :) I'd like to devolve some of the network hatching to some trusted souls so they can send out their work when they want to. :)

Best, Paul

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 10/23/17, Avon pondered and said...

The idea behind Hatch ACS is that users who meet that requirement wil be able to (H)atch a file right from within the file listing so that will solve your issue once that is implemented.

So far I've only added it into the file listing editor, but it will b also added directly into the listings.

OK gotcha... well that would be a good thing to sneak in to the upcoming releases when you're able :) I'd like to devolve some of the network hatching to some trusted souls so they can send out their work when they want to. :)

Oh and if possible a way to call the hatching function via MUTIL so HUBs can automate weekly hatching of nodelists etc. I'm sure we've touched on that before but I just put it up for consideration now as well - thanks :)

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)