Woke up early and started thinking after a morning coffee..

Coming from a HUB point of view these features would be welcome sometime in
the future. I'm open to debating pro's and con's but just throwing these
ideas out there for consideration / discussion etc.

#*# The ability to generate a %rescan action of selected/tagged echomail
bases for a specific echomail node(s)

Rationale: When connecting a new echomail node to the network the HUB operator could assist a new sysop by feeding a full digest of past echomail message
out to the node during the early stages of assisted setup. Another scenario
is helping with a new HUB getting setup by pushing a full echomail feed from one HUB to another to establish it's message bases. I know I can do this
using netmail between them, I'm just being lazy in my wish for a push button option :)

#*# The ability to tag selected files in a file base(s) and hatch them to a selected echomail node(s)

Rationale: Currently a HUB can push a file(s) from a file base to node that
are added to a file bases 'export to' list. This works for most scenarios but what if the HUB operator desired to hatch out previously hatched files to all nodes but just to a specific node such as a new member of the network? The current only option is hatch a file out again to all connected nodes. Not
ideal use of bandwidth.

#*# The ability to build a custom list(s) of files/bases to hatch to a nominated echomail node(s) when called by a menu command or mutil function.

Rationale: Extending on from the above idea. If a HUB wants to hatch out a selection of files from various file bases to a new node. Having the ability
to build a custom list(s) to semi-automate the hatch process would be
helpful. e.g. "I'm a new node and I would really like to get copies of the most recent Mystic installer files sent to my FSX_MYST file base along with the most recent three released art packs to FSX_ARTS and the specific Mystic utility/mpl I asked my HUB op to send me that does that cool message of the day login screen." ... in this case I'm suggesting almost a combo of feeding a node a turnkey list of files from assorted file bases plus adding a few selected
files requested by the node as well.

#*# The ability to create / customize templates used by the HUB when replying to Filefix / Areafix requests.

Rationale: Unlike many aspects of Mystic the current netmail replies for Areafix and Filefix (excluding the help files) are hard coded. Subject to
what additional future stats reporting is built in to Mystic and or/other features etc. that come along, I think it would be nice to be able to offer
the sysop the ability to add some customized text to those netmail replies along with the usual suspects of extra MCI codes that could be added to those templates.


#*# Export / Import functionality of echomail node data between HUBs.

Rationale: If an established HUB wants to spin off some nodes to a new HUB there's no easy way to get the individual echonode settings out of the old
HUB and in to the new one short of manually entering and retyping each node by hand. As a consequence of this.. to shift 20,30 nodes to a new HUB is a big undertaking.

#*# Tagging and global editing functionality for echomail nodes

Rationale: Assuming a migration of echomail node data was possible there
would still need to be some mass changes of some data for each echomail node imported. Most likely in the areas of file paths, network zone, net,
node or point... (in truth it would be mostly network net I expect). So having the ability to mass tag selected echomail nodes then set those changes using a global editor (such as the one used in message bases) would be very helpful
and a time saver as much as being able to import/export echomail node data would be in the first place.

I'm going to stop now :)

Best, Paul

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

On 27 Jan 2020, g00r00 said the following...

Also soliciting ideas or requests for A45 if anyone wants to nag me. I
am not sure what I plan to do for A45 yet. The time away sort of made
me forget my intentions.

Now you're really asking for it <g>

I was thinking (always a bad idea) earlier about hashtags (tags, flags, whatever) and how they could be used in this instance.

My file areas are always a mess. Mostly that is just me but it would be nice
to have file areas use "tags" as well as directories. For instance, Murder Mansion is in my Mystic File area currently because it's an MPL. Would be
nice to also have it included in a games file area as well without
duplicating the file.

Just a thought. I'm definitely just an end user so don't know how difficult something like that would be to implement but I could see tags being used
like ACS flags for more than just users.

-=>Richard Miles<=-
-=>Captain Obvious<=-
-=>bbs.shadowscope.com<=-

--- Mystic BBS v1.12 A44 2020/01/27 (Windows/32)
* Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (21:1/157)

Would be nice to also have it included in a games file area as well without duplicating the file.

Thanks I'll consider how this could best be handled and make a note on the TODO list. The file areas in general could use a complete revamp to be honest.

They've been mostly unchanged since the 1990s besides adding in the index file area thing and archive viewer.

--- Mystic BBS v1.12 A44 2020/01/27 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 27 Jan 2020, g00r00 said the following...

Would be nice to also have it included in a games file area as well without duplicating the file.

Thanks I'll consider how this could best be handled and make a note on
the TODO list. The file areas in general could use a complete revamp to be honest.

They've been mostly unchanged since the 1990s besides adding in the
index file area thing and archive viewer.

Ooh! I wanted to ask if you could jot down in the TODO about finishing file attachments to messages. I see it was *kind of* setup, but it's
non-functional.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: throwbackbbs.com -\- meriden, ct -\- (21:1/114)

Ooh! I wanted to ask if you could jot down in the TODO about finishing file attachments to messages. I see it was *kind of* setup, but it's non-functional.

The reason I haven't bothered with that is because no one uses local messages, and echomail doesn't allow file attachments.

--- Mystic BBS v1.12 A44 2020/01/28 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 28 Jan 2020, g00r00 said the following...

Ooh! I wanted to ask if you could jot down in the TODO about finishin file attachments to messages. I see it was *kind of* setup, but it's non-functional.

The reason I haven't bothered with that is because no one uses local messages, and echomail doesn't allow file attachments.

No worries man, was just an idea! =)

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: throwbackbbs.com -\- meriden, ct -\- (21:1/114)

On 27 Jan 2020, g00r00 said the following...

The file areas in general could use a complete revamp to be honest. They've been mostly unchanged since the 1990s besides adding in the
index file area thing and archive viewer.

I'd suggest a split window approach to the file lister if you decide to
revisit that, since the classic paging lister kind of gets overwhelmed on
file bases that can contain hundreds of entries with long descriptions.

For example you could have the file list on one side navigable by lightbar or type-ahead find while the currently selected file's description is on the
other side. That should make it more convenient to browse regardless of description length and give it a more similar feel to the existing indexed listers.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

The file areas in general could use a complete revamp to be honest. They've been mostly unchanged since the 1990s besides adding in the index file area thing and archive viewer.

I'd suggest a split window approach to the file lister if you decide to revisit that, since the classic paging lister kind of gets overwhelmed on file bases that can contain hundreds of entries with long descriptions.

I've planned to do that for a while now once I get around to rebuilding everything. But Gryphon made a MPL that does exactly that and I didn't want to step on his toes.

For example you could have the file list on one side navigable by
lightbar or type-ahead find while the currently selected file's description is on the other side. That should make it more convenient to browse regardless of description length and give it a more similar feel
to the existing indexed listers.

Yep this was along the lines of what I wanted to do too. Although I may not have the "type to search" that I usually put in places throughout Mystic just because it requires a lot of memory for large bases.

--- Mystic BBS v1.12 A44 2020/01/29 (Linux/64)
* Origin: Sector 7 (21:1/108)