• New Ideas For Mystic

    From The Millionaire@21:1/183 to All on Monday, July 27, 2020 20:34:34
    Does anyone have any new ideas for Mystic? Anything you’d like to see in the next version.

    $ The Millionaire $

    ..."Will we ever fear the ecstasy of free thought?" - Thinkman...
    --- SBBSecho 3.11-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)
  • From The Godfather@21:1/165 to The Millionaire on Tuesday, July 28, 2020 01:20:02
    Does anyone have any new ideas for Mystic? Anything you’d like to see
    in the next version.

    I'd like to see a more retro waiting for call .exe other then nodespy. One that has menu options such as the ability for SysOps to read mail, view
    todays callers, view where callers spent their time, and a fast login to
    avoid the normal login process when in local mode. Lastly on this topic would be menu options to read all logs from waiting for call.

    I'd also like to see js support.

    Complete documentation on the Wiki page, especially the more advanced
    functions / error correction not currently listed in more detail.

    A stock quick login option. However with the ability to customize with ANSI, BBS update / announcement option at login, as well as a configurable login for users, while being able to control what must be seen from the sysop such as announcements.

    More menu options within prelogin, as it appears it has it's limitations when attempting to insert new menu commands. Sometimes it's easier to use a DT command to clear a screen and/or pause, without impacting the ANSI displayed.

    Resetting file and message area ID's when one is deleted and replaced with a new. Messge areas globally assigned to the new, without having to rescan existing posts/files.

    The move file option does not appear to work well from uploads to other areas of the BBSs file section. A global move and delete option would be nice.

    Updating a users access while they are online as opposed to having to wait
    for them to logoff. Again, I don't know if this is just not working on my
    BBS, but it prompts I can not update a new user until they have logged off.

    Two factor email verification for instant access, with the option to disable.

    The option to use header feature with ansi based files, with x/y coordinates more easily done within menus to determine the cursor placement for pipe code placement, such as replacing the stock message read option.

    All prompt options within the menu command menu, to allow customization and light bar matrix/standard options.

    A more automated way of adding new networks via config, reducing the need for mutil .ini files.

    VGA file format .jpg, .gif, .png, etc. functionality to allow for posting and or menu/login/logoff usage within the BBS. Such as, posting a picture of a
    Pi setup, or landscape project, within message areas, or allowing hyperlink
    to webpages from within message/email read. Or to view graphic files within
    a file base, prior to download. Or posting social media links/photos within prelogin.

    More customization within the new user login process to add more ANSI, and to control the display of questions asked to be light bar compatible, from
    within menu options.

    One matrix login new user login process. Not a separate for the feature
    turned on versus off. For example, I use a startup script for login, and not the current matrix login. If I convert to matrix login, it'll take rather overhaul to re-due prompts and ansi files.

    Message area topics displayed by topic, with replies contained within, so
    that an entire chain of conversation can be skipped if no interest.

    Built in 16bit door support without requiring a virtual login.

    InterBBS league games using the same node address as already subscribed to a network, so that if a host takes necessary time off, a BBS's gaming users can immediatly enjoy the game league functionality.

    A manual on hosting a network, and or being a hub for anothers.

    Rescan option to acquire past network file uploads from the hub, similar to message area content rescans.

    Improved python support to include trouble shooting and instruction on
    getting scripts/mods working as long as the basic installation is correct within python. In otherwords, elaboration on wiki on getting python working correctly on OS versions.

    Built in social media connectivity to promote the BBS community and or allow users to post to social media platforms, with the goal to grow the BBS user base community and general presence.

    Improved intellectual analysis of fake versus factual new user input fields such as email address, city and state / country and?

    All .mps functions included within the stock BBS, such as automessage,
    allowing for an ANSI display file option, with $1 / $2, fields to determine data placement.

    An old school post/upload reward function customizable by theme, i.e dollars versus gold versus credits. With the ability of users to fight one another
    at login for their earned credits, to promote full use activity to each BBS, and one more way users can interact with one another.

    inter MRC standard within stock Mystic installs.

    Auto move feature within file areas to copy network file downloads to local file areas, reducing a users necessity to search each network for a mystic script/mod they want / ansi pack. Optional, conditional, etc...

    Pyton 3 support.

    Just to name a few. But I love mystic. Don't get me wrong, these are a few "like to haves." I think Mystic should continue to represent the SysOps
    desire to keep it "retro," compared to being able to offer more connectivity and functionality that creates a social media like environment without the downfalls and SysOp moderation control, to reduce and or eliminate cat memes, as an example.

    -tG -- you asked ... shrug.

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
    * Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)
  • From Zip@21:1/202 to The Godfather on Tuesday, July 28, 2020 10:09:17
    Hello The Godfather!

    On 28 Jul 2020, The Godfather said the following...
    More menu options within prelogin, as it appears it has it's limitations when attempting to insert new menu commands. Sometimes it's easier to

    If you're hitting the action limit (20 actions?), you can add multiple
    FIRSTCMD "hotkey entries" after each other:

    Ûßßßßßßßßßßßßßßßßß Menu Options: scbbs_en.prelogin ßßßßßßßßßßßßßßßßßßÜ
    Û HotKey Text ID Exe Û
    Û ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Û
    ÜÜ Û FIRSTCMD CUSTOM: Prelogin menu #1 1 4²²gj!
    ÛÛÜÜÛ FIRSTCMD CUSTOM: Prelogin menu #2: E-mail address verif 2 20°ÛÜÜ
    °ÛÛÛÛ FIRSTCMD CUSTOM: Prelogin menu #3 3 11°ÛÛ±þ

    They are executed in the order they are listed, I think.

    Hope this helps. :)

    Best regards
    Zip

    --- Mystic BBS v1.12 A46 2020/06/11 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From The Godfather@21:1/165 to Zip on Tuesday, July 28, 2020 07:23:21
    More menu options within prelogin, as it appears it has it's limitati when attempting to insert new menu commands. Sometimes it's easier t

    If you're hitting the action limit (20 actions?), you can add multiple FIRSTCMD "hotkey entries" after each other:

    Ûßßßßßßßßßßßßßßßßß Menu Options: scbbs_en.prelogin ßßßßßßßßßßßßßßßßßßÜ Û HotKey Text

    Very nice! Thank you!

    -tG

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
    * Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)
  • From paulie420@21:2/150 to The Godfather on Tuesday, July 28, 2020 16:46:42
    On 28 Jul 2020, The Godfather said the following...

    Does anyone have any new ideas for Mystic? Anything you’d like to s in the next version.

    I'd like to see a more retro waiting for call .exe other then nodespy. One that has menu options such as the ability for SysOps to read mail, view todays callers, view where callers spent their time, and a fast
    login to avoid the normal login process when in local mode. Lastly on
    this topic would be menu options to read all logs from waiting for call.

    I'd also like to see js support.

    Complete documentation on the Wiki page, especially the more advanced functions / error correction not currently listed in more detail.

    A stock quick login option. However with the ability to customize with ANSI, BBS update / announcement option at login, as well as a configurable login for users, while being able to control what must be seen from the sysop such as announcements.

    More menu options within prelogin, as it appears it has it's limitations when attempting to insert new menu commands. Sometimes it's easier to
    use a DT command to clear a screen and/or pause, without impacting the ANSI displayed.

    Resetting file and message area ID's when one is deleted and replaced
    with a new. Messge areas globally assigned to the new, without having
    to rescan existing posts/files.

    The move file option does not appear to work well from uploads to other areas of the BBSs file section. A global move and delete option would
    be nice.

    Updating a users access while they are online as opposed to having to
    wait for them to logoff. Again, I don't know if this is just not working on my BBS, but it prompts I can not update a new user until they have logged off.

    Two factor email verification for instant access, with the option to disable.

    The option to use header feature with ansi based files, with x/y coordinates more easily done within menus to determine the cursor placement for pipe code placement, such as replacing the stock message read option.

    All prompt options within the menu command menu, to allow customization and light bar matrix/standard options.

    A more automated way of adding new networks via config, reducing the
    need for mutil .ini files.

    VGA file format .jpg, .gif, .png, etc. functionality to allow for
    posting and or menu/login/logoff usage within the BBS. Such as, posting
    a picture of a Pi setup, or landscape project, within message areas, or allowing hyperlink to webpages from within message/email read. Or to
    view graphic files within a file base, prior to download. Or posting social media links/photos within prelogin.

    More customization within the new user login process to add more ANSI,
    and to control the display of questions asked to be light bar
    compatible, from within menu options.

    One matrix login new user login process. Not a separate for the feature turned on versus off. For example, I use a startup script for login,
    and not the current matrix login. If I convert to matrix login, it'll take rather overhaul to re-due prompts and ansi files.

    Message area topics displayed by topic, with replies contained within, so that an entire chain of conversation can be skipped if no interest.

    Built in 16bit door support without requiring a virtual login.

    InterBBS league games using the same node address as already subscribed
    to a network, so that if a host takes necessary time off, a BBS's gaming users can immediatly enjoy the game league functionality.

    A manual on hosting a network, and or being a hub for anothers.

    Rescan option to acquire past network file uploads from the hub, similar to message area content rescans.

    Improved python support to include trouble shooting and instruction on getting scripts/mods working as long as the basic installation is correct within python. In otherwords, elaboration on wiki on getting python working correctly on OS versions.

    Built in social media connectivity to promote the BBS community and or allow users to post to social media platforms, with the goal to grow the BBS user base community and general presence.

    Improved intellectual analysis of fake versus factual new user input fields such as email address, city and state / country and?

    All .mps functions included within the stock BBS, such as automessage, allowing for an ANSI display file option, with $1 / $2, fields to determine data placement.

    An old school post/upload reward function customizable by theme, i.e dollars versus gold versus credits. With the ability of users to fight one another at login for their earned credits, to promote full use activity to each BBS, and one more way users can interact with one another.

    inter MRC standard within stock Mystic installs.

    Auto move feature within file areas to copy network file downloads to local file areas, reducing a users necessity to search each network for
    a mystic script/mod they want / ansi pack. Optional, conditional,
    etc...

    Pyton 3 support.

    Just to name a few. But I love mystic. Don't get me wrong, these are
    a few "like to haves." I think Mystic should continue to represent the SysOps desire to keep it "retro," compared to being able to offer more connectivity and functionality that creates a social media like environment without the downfalls and SysOp moderation control, to
    reduce and or eliminate cat memes, as an example.

    -tG -- you asked ... shrug.


    Yes, I quoted it all. Because... those are some rad ideas; a few I don't need/care about, but many good ones...

    I suggested in NULL007 that we, as a group, create a way that this type of
    work could actually happen:

    g00r00, from what I gather, works on Mystic as a side gig and because he
    loves it... I think that [all] those of us who use and love Mystic should
    pony up... $300 was a normal price for BBS softwares, when we were 18! Synchronet, TBBS, Mustang Wildcat! and more cost 3 beans on the low end. I
    bet we could even get away with $100 - point being... theres got to be 1000 instances of Mystic running.

    $100-300k would REALLY get a programmers interest for a solid year. And then
    we could write these (and more) want lists and actually expect to get most of the ones that can work.

    Anyway... I will at any time pony up; hell, I might even work to make this happen, if theres interest... however, if we all simply USE [and love]
    Mystic, we are correctly at the mercy of the designer.

    Lastly; I'm going to go ahead and make the statement right now. Regardless,
    I'm going to donate a hundo to g00r00 for Mystic. I don't think its for the future; its for the past. :P

    Quick interest gauge: Would ya'll be interested in collectively supporting the software that we love [and USE]?



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
    * Origin: American Pi BBS (21:2/150)
  • From paulie420@21:2/150 to The Godfather on Tuesday, July 28, 2020 16:49:26
    More menu options within prelogin, as it appears it has it's lim when attempting to insert new menu commands. Sometimes it's eas

    If you're hitting the action limit (20 actions?), you can add multipl FIRSTCMD "hotkey entries" after each other:

    Ûßßßßßßßßßßßßßßßßß Menu Options: scbbs_en.prelogin ßßßßßßßßßßßßßßßßßßÜ Û HotKey Text

    Very nice! Thank you!

    -tG

    Zip always has the best Mystic suggestions. Need to checkout his/her board.



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
    * Origin: American Pi BBS (21:2/150)
  • From Adept@21:2/108 to paulie420 on Wednesday, July 29, 2020 06:06:00
    Quick interest gauge: Would ya'll be interested in collectively
    supporting the software that we love [and USE]?

    Money is tight, but I'd be happy to throw at least a couple bucks a month at
    a Patreon thing or something like it.

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
    * Origin: Storm BBS (21:2/108)
  • From Andre@21:3/117 to paulie420 on Wednesday, July 29, 2020 08:28:25
    On 28 Jul 2020, paulie420 said the following...

    Yes, I quoted it all. Because... those are some rad ideas; a few I don't

    Makes it hard to read and hard to quote.


    pony up... $300 was a normal price for BBS softwares, when we were 18!

    $100-300k would REALLY get a programmers interest for a solid year. And

    Not really. WWIV was $50 with the source. Wildcat was $130 for one node or
    $250 for ten nodes.

    Let's say we said everyone would pay $100 from every BBS currently out there. There are 2000 FidoNet nodes by 1000 sysops. So your math works out at $200,000.

    But if it cost $100 to run it, would those 2000 BBS exist? I'd say no. Even half of those seems like a stretch.


    Quick interest gauge: Would ya'll be interested in collectively
    supporting the software that we love [and USE]?

    $100 for Mystic? No. It's just not that important to me amongst my other hobbies, despite that I really enjoy it and like the software. $50? Maybe. Probably.

    Or would I just to work with Enigma1/2 and contibute to the project for free? More likely.

    This is simply being done for nostalgia and so my son can learn a little
    about the history of it all. Learning history for him isn't worth $100 to me one time, much less for subscription or for uprgades. And for nostalgia, I'd just go to someone else's existing board.

    So now we're back to the 80s. It was cost prohibitive, which is why you only saw a one or two boards in a town if you were lucky.


    Andre

    --- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
    * Origin: Runaan BBS (21:3/117)