• A44 prealpha

    From Oli@21:1/151 to g00r00 on Fri Jan 24 22:08:08 2020
    24 Jan 20 11:24, you wrote to me:

    Mystics BBS interpretation isn't accepted by the linux date
    command. I think it was a missing + or space character. Some
    tiny detail was wrong.

    You'll need to be more specific than that.

    just compare it with the date format that binkd is using. the difference is at the end of the string. i don't think it's important. i only looked into this, because i thought that was the reason for the wrong file timestamps (but it's not).

    the line breaking at 80 chars is much more problematic ...


    * Origin: 🌈 (21:1/151)
  • From Avon@21:1/101 to g00r00 on Sat Jan 25 10:33:33 2020
    On 24 Jan 2020 at 11:13a, g00r00 pondered and said...

    I just noticed that the FSX mail doesn't seem to be getting to the BBS I was using (not sure if my replies have gone out either) so I am a bit behind.

    My hunch is that MIS on Gryphon's system has auto IP blocked the 1/100 HUB :( Dan aka Black Panther had (at my request) logged in to leave him a message about this to see if that was the case. I can't telnet in as I use the same
    IP. (219.89.83.33 and 2001:470:d:123::50)

    The reason will be because for a while I have been using BinkD as the mailer for the HUB.. and for about a month also HPT do do the tossing to try and negate SEEN-BY issues (and some others I have posted about to you) but when
    you resurfaced I switched 1/100 back to Mystic but help BinkD.

    I have a hunch there may be some issues with the inbuilt BinkP server or
    MUTIL or a combo of both leading to some packets not being sent to nodes. I have seen occasions whereby nodes report missing packets. Some checks at
    1/100 seem to suggest that .HLO files and others sometimes seem to be missing links to compressed packets waiting for a node. This leads to compressed
    files sitting in echomail\out not being sent even when a node polls in.

    I has switched to BinkD initially to try and see if missing packets sent to a NET 1 node (Oli was very good at reporting these to me - thanks Oli :)) were resolved by just switching out the mailer... and it seemed to be the case.
    Oli was reporting all packets coming in to him (he was comparing them to a
    feed he was getting from 3/100 HUB also) but there were the other soft CR and wrapping issues also being seen as well.. that I think are more related to MUTIL and not the issue I'm waffling on about now :)

    Anywhoo... thanks for the reply. I thought this may be the case with your
    pause in responses. Unless you post at Cyberia my hunch is no outbound
    polling of 1/100 would take place and with inbound polling of 1/100 being blocked it's a PITA

    FIDOPOLL Version 1.12 A44 2020/01/16

    Looking up address "21:1/120" in nodelist
    Scanning 21:1/120
    Queued 9 files (818243 bytes) to 21:1/120
    Polling BINKP node 21:1/120 (Darryl Perry) by IPV4
    Connecting to cyberiabbs.zapto.org
    Connected IPV4 to 54.193.66.229
    Error receiving data (Msg= Size=0/6336)
    Connection lost
    Authorization failed

    Sigh...

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to g00r00 on Sat Jan 25 12:29:33 2020
    On 24 Jan 2020 at 11:13a, g00r00 pondered and said...

    I just fixed up the SEEN-BY again and I will make another build shortly, So there should be a build dated Jan 24th shortly that has the fix.

    I tested the following and we're getting there but there is still an issue I think with the logic being applied.

    Most lines were fine now in this test but the last line where the first NET 2 address happened to fall was messed up with an additional 2/

    Take a look

    [snip]

    From: Paul Hayton
    To: All
    Subj: NET 1 HUB
    Date: 01/25/20 12:22
    Base: General Chat

    @TID: Mystic BBS 1.12 A44
    @MSGID: 21:1/100 f9576c79
    @TZUTC: 1300
    @SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 @SEEN-BY: 1/116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 133 @SEEN-BY: 1/134 136 137 138 139 140 141 143 144 145 146 147 148 149 150 152 153 @SEEN-BY: 1/154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 171 @SEEN-BY: 1/172 173 174 175 176 177 178 180 181 182 183 184 185 186 187 188 189 @SEEN-BY: 1/190 191 192 193 194 195 197 199 200 201 202 203 204 205 995 999 @SEEN-BY: 2/2/100 3/100 4/100 5/100
    @PATH: 1/100
    Has been updated to v1.12 A44 Windows/32 Compiled 2020/01/24 15:22:51

    --- Mystic BBS v1.12 A44 2020/01/24 (Windows/32)
    * Origin: fsxNet HUB (21:1/100)

    [snip]

    Hope that helps :)

    Thanks for working on this one.

    Best, Paul

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From g00r00@21:1/163 to Oli on Fri Jan 24 15:14:34 2020
    just compare it with the date format that binkd is using. the difference is at the end of the string. i don't think it's important. i only looked into this, because i thought that was the reason for the wrong file timestamps (but it's not).

    The string for my timezone is identical to that of binkd, which is I thought what I had already said but maybe I didn't. I literally looked at the binkd code back in the day because the standard wasn't always clear.

    I am willing to bet you saw a + on non-biased time zones (which I wouldn't see where I live because I am not in Asia/Austrialia).

    BinkP references that RFC like I already mentioned, but then the example they give directly after that doesn't even follow the RFC format (lol). The Fidonet standard for TZ specifically says NOT to include a + but that software should be prepared to handle it if it does.

    So which one do I follow? Mystic can follow the shoddy BinkP specification tha contradicts itself, or the FidoNet standard for supplying the TZ bias? Right now it follows the TZ FidoNet standard and doesn't include the + but I can change it to show the + just for BinkP TIME frame if that is what BINKD does.

    the line breaking at 80 chars is much more problematic ...

    Its not breaking, its word wrapping text. It was a requested feature both at the echomail and NNTP levels because of content getting lost.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)
  • From g00r00@21:1/163 to Avon on Fri Jan 24 15:59:12 2020
    I tested the following and we're getting there but there is still an
    issue I think with the logic being applied.

    Thanks for the update. This is challenging to test because I don't have any system capable of reproducing the situation at the moment.

    Along the echomail lines, I saw your message about potential issues with FLO files so I have introduced FLO.TXT! We got rid of the BUSYLOG and now we get another one ;)

    I made a special build for you (anyone really) who wants to help locate any issues with FLO logs. The builds below will create a "flo.txt" in the same directory anytime one of the flow files are modified in any way. If there is some sort of error or issue with FLO it should be captured in that .txt file.

    www.mysticbbs.com/downloads/prealpha/FLO

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)
  • From Avon@21:1/101 to g00r00 on Sat Jan 25 19:48:04 2020
    On 24 Jan 2020 at 03:59p, g00r00 pondered and said...
    Thanks for the update. This is challenging to test because I don't have any system capable of reproducing the situation at the moment.

    It's all good, just keep tweaking and I'll keep testing :)

    Along the echomail lines, I saw your message about potential issues with FLO files so I have introduced FLO.TXT! We got rid of the BUSYLOG and
    now we get another one ;)

    I made a special build for you (anyone really) who wants to help locate any issues with FLO logs. The builds below will create a "flo.txt" in
    the same directory anytime one of the flow files are modified in any
    way. If there is some sort of error or issue with FLO it should be captured in that .txt file.

    OK ta... so to clarify this build looks at files created by MUTIL for a BSO mailer weather it be Mystic's inbuilt BinkP server or the one I am currently using to send traffic around (BinkD)? Am I understanding that right?

    I need to ensure SEEN-BY's are sorted before I drop it into NET 1 HUB
    though.. else I create more issues for nodes while trying to test for this
    next thing. Make sense?

    Gotta say the one thing that I really like that BinkD offers over the inbuilt combo of Mystic BinkP server and Fidopoll is that when calling out to nodes BinkD can poll many at once and the delivery of CRASH packets to nodes is lightning fast vs the sequential one node polled at a time manner of Fidopoll...

    All of which is a roundabout way of asking do you think Fidopoll will ever be enabled to allow for multiple outgoing concurrent sessions like BinkD offers?
    I think also the plan was to move the fidopoll code into the BinkP server at some stage?? Does that sound right or am I way off?

    Anywhoo I'll sit tight for now but will pull down the software and wait to
    read your replies :)

    Thanks James..

    Best, Paul

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Oli@21:1/151 to g00r00 on Sat Jan 25 12:05:52 2020
    24 Jan 20 15:14, you wrote to me:

    just compare it with the date format that binkd is using. the
    difference is at the end of the string. i don't think it's
    important. i only looked into this, because i thought that was
    the reason for the wrong file timestamps (but it's not).

    The string for my timezone is identical to that of binkd, which is I thought what I had already said but maybe I didn't. I literally
    looked at the binkd code back in the day because the standard wasn't always clear.

    I am willing to bet you saw a + on non-biased time zones (which I
    wouldn't see where I live because I am not in Asia/Austrialia).

    yes, I discovered it with Avon's node. binkd and mystic do use a different format in the TIME field.

    call to 21:1/101@fsxnet
    TIME Sat, 25 Jan 2020 23:12:07 1300
    VER Mystic/1.12A43 binkp/1.0

    vs.

    call to 21:1/100@fsxnet
    TIME Sat, 25 Jan 2020 23:12:38 +1300
    VER binkd/1.1a-99/Win32 binkp/1.1

    $ date -d "Sat, 25 Jan 2020 23:12:07 1300"
    date: invalid date 'Sat, 25 Jan 2020 23:12:07 1300'

    vs.

    $ date -d "Sat, 25 Jan 2020 23:12:38 +1300"
    Sat 25 Jan 2020 11:12:38 AM CET

    BinkP references that RFC like I already mentioned, but then the
    example they give directly after that doesn't even follow the RFC
    format (lol).

    Bullshit. Quote from the binkp 1.0 spec:

    Example of valid date_time is:
    Sun, 06 Nov 1994 08:49:37 GMT

    This is correctly formatted according to RFC 822: https://www.rfc-editor.org/rfc/rfc822.html#section-5.1

    The Fidonet standard for TZ specifically says NOT to
    include a + but that software should be prepared to handle it if it
    does.

    the TZUTC kludge is irrelevant here.

    So which one do I follow? Mystic can follow the shoddy BinkP specification tha contradicts itself, or the FidoNet standard for supplying the TZ bias? Right now it follows the TZ FidoNet standard
    and doesn't include the + but I can change it to show the + just for
    BinkP TIME frame if that is what BINKD does.

    Just follow the RFC 822 standard as binkd does and binkp requires.

    the line breaking at 80 chars is much more problematic ...

    Its not breaking, its word wrapping text.

    Whatever you call it, a tosser shouldn't modify the mail's text body at all.

    It was a requested feature
    both at the echomail and NNTP levels because of content getting lost.

    And it's really annoying. Just because it happens to have some advantages for Mystic BBS users on a 80x25 terminal doesn't mean everyone else profits from it. It prevents dynamic word wrapping for other ftn editors and format=flowed aware nntp readers. It breaks dupe detection which some software.

    There is also not one technical reason to add <CR> characters for exported mail
    or to mails imported to the JAM base. Word wrapping can be dynamically applied
    in the message reader or the NNTP server.

    Please disable it ASAP. It introduces unnecessary problems and we wasted quite some time in figuring out what is going on and trying to work around the problems (without much success).

    Please respect FTS-0001 that states:

    A 'hard' carriage return, 0DH, marks the end of a paragraph, and must
    be preserved.

    It marks the end of a _paragraph_ not the end of a line in a pre-wrapped paragraph. And also

    Systems which display message text should wrap long lines to suit their application.

    It has been always like this in Fidonet and it works very well.




    * Origin: 🌈 (21:1/151)
  • From g00r00@21:1/163 to Avon on Sat Jan 25 11:05:20 2020
    OK ta... so to clarify this build looks at files created by MUTIL for a BSO mailer weather it be Mystic's inbuilt BinkP server or the one I am currently using to send traffic around (BinkD)? Am I understanding that right?

    No, whenever MIS or MUTIL or FidoPoll touches a ?lo file it just logs in
    detail what its doing and if there was any issues. So if you're saying file references are getting removed from flo files, this should show us when/how that is happening.

    I could be misunderstanding the issue too, I've been trying to do a lot
    quickly lately.

    I need to ensure SEEN-BY's are sorted before I drop it into NET 1 HUB though.. else I create more issues for nodes while trying to test for
    this next thing. Make sense?

    Yep makes sense. Unfortunately I was not able to get my laptop yesterday so I could test it and make sure its fixed. I'll try to figure something out
    today. I do have the Pi3 that I use to compile Mystic maybe I can set my BBS up on that too for testing, but testing on a Pi is very very time consuming.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)
  • From g00r00@21:1/163 to Oli on Sat Jan 25 11:21:57 2020
    Just follow the RFC 822 standard as binkd does and binkp requires.

    As I've already pointed out to you, none of them are actually following the RFC 882. My TIME string is identical from BINKD or Mystic which is why I am asking you what was wrong. I've already added the + into the later versions.

    And it's really annoying. Just because it happens to have some
    advantages for Mystic BBS users on a 80x25 terminal doesn't mean

    It has nothing to do with Mystic BBS. It was requested by people who saw problems with legacy software that can't handle text longer than 80 characters, offline readers, the mess NNTP was making (there was a huge push for NNTP gatin back in the day).

    You seem to have almost no context in history or the reason things are done the way they are.

    There is also not one technical reason to add <CR> characters for
    exported mail or to mails imported to the JAM base. Word wrapping can be dynamically applied in the message reader or the NNTP server.

    Sure they can. Now go back and tell the 50,000 DOS, Atari, Commodore, etc packages that haven't had updates in 25-30 years so they can release new version that can handle it. :)

    Please disable it ASAP. It introduces unnecessary problems and we wasted

    Its such a huge problem that no one has brought it up in a decade. The "problems" it introduced was that message content doesn't get lost at the expense of a line being wrapped. One is horrible, and one is a visual line wra that is hardly a big deal given how few people are using more than 80 column displays.

    The latter was universally agreed to be the best approach by people actually using software.

    Its interesting you're pushing so hard on this but (for example) you don't seem to care about software using things like MSGID that are not compatible with old software despite the FTN people themselves saying its not intended to be used that way.

    I agree its time to revisit it, but you seem to have a knack at trying to paint every little issue as the end of the world. Its not.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)
  • From Avon@21:1/101 to g00r00 on Sun Jan 26 17:05:19 2020
    On 25 Jan 2020 at 11:05a, g00r00 pondered and said...

    No, whenever MIS or MUTIL or FidoPoll touches a ?lo file it just logs in detail what its doing and if there was any issues. So if you're saying file references are getting removed from flo files, this should show us when/how that is happening.

    OK that I get and it makes sense to me - thanks :)

    I could be misunderstanding the issue too, I've been trying to do a lot quickly lately.

    To be fair I am not that on top of it either and with you away I was
    resorting to using both HPT and BinkD to eliminate issues...

    I think (from memory) just swapping out to BinkD sorted the issues Oli was reporting.. now I am back to using MUTIL for tossing but still BinkD at this stage.

    I need to ensure SEEN-BY's are sorted before I drop it into NET 1 HUB though.. else I create more issues for nodes while trying to test for this next thing. Make sense?

    Yep makes sense. Unfortunately I was not able to get my laptop
    yesterday so I could test it and make sure its fixed. I'll try to
    figure something out today. I do have the Pi3 that I use to compile

    Don't rush on my account... but yeah I think best that SEEN-BY is sorted
    first before try to debug if there is anything amiss with MIS, MUTIL or FIDOPOLL with ?lo files.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Alterego@21:2/116 to g00r00 on Mon Jan 27 00:18:11 2020
    Re: A44 prealpha
    By: g00r00 to Avon on Sat Jan 25 2020 11:05 am

    out today. I do have the Pi3 that I use to compile Mystic maybe I can set my BBS up on that too for testing, but testing on a Pi is very very time consuming.

    So testing on any platform shouldnt be time consuming - and if you are up for it, I'd be willing to help you make it easier.

    I develop a bit, and use gitlab as my developer toolset - its probably very similar to github. My gitlab is private, only because I also develop private code (that I dont share) - and I wanted everything in one place.

    With my development I use CI, and have it automating the builds of apps, app testing and docker images. EG: When I commit code that is building a docker container, CI automates the build of that container - that I can then use a few
    mins later. As an example, my mystic container build is here: https://dev.leenooks.net/leenooks/mysticbbs/pipelines. (This is why I asked in
    the past for improvements to automate an install, and changes to data layouts.)

    After this CI runs, I can instantiate a new mystic environment relatively quickly (mins) on a config that I know works - and on X86 and ARM (I dont use windows...).

    So, it might be able to help you, ie:
    * You update some code and commit it.
    * The commit automates a build on ARM, X86 (linux) and possibly even windows. This results in the package you make available on your website.
    * A second CI job, then takes that install package and then creates a docker container - which you can instantiate with a "docker run" (to test to make sure
    things work as expected)...

    It might mean a little bit of investment in learning git/docker, perhaps a new way of doing some things, or even automating an install (assuming you can automate the compile in the first place - I have no experience with freepascal), but it would mean, when you pushed code to the repository, automated builds result in a runtime that you can instantiate very quickly...

    A bit more info on my docker implementation is here: https://chinwag.static.leenooks.net/2018/09/01/mysticbbs/ - it may give you an idea of how quickly you can run up a test environment. On my docker Pi, I had 3
    instances of Mystic running at one point, while I was playing with it (each using their own (same) telnet/ssh/binkp/nntp ports, but mapped to unique ports on the docker host.

    ...deon
    ...deon


    ... Ketterling's Law: Logic is an organized way of going wrong with confidenc --- SBBSecho 3.10-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Analog@21:2/123 to Alterego on Sun Jan 26 08:15:25 2020
    With my development I use CI, and have it automating the builds of apps, app testing and docker images. EG: When I commit code that is building a docker container, CI automates the build of that container - that I can then use a few mins later. As an example, my mystic container build is

    ^^^ This.

    Though I can't say exactly where I work, this is the way I automate our dev CI pipelines. Could wrap some tests here to check for functionality too.

    Great job and I second this apprach.

    |19|15┌─|16|07┤ |08De|07ad|15be|07a|08tz b|07b|15s
    |07└─┘├─┐ |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
    |11■ |07└|19|15─|16|07┘ |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
    |12≡|15A|07n|08al|07o|15g|12≡ |08:>.|13F|05dn |131|08:|13305|08/|132|08.
    |08:>.|15S|08ci |1577|08:|151|08/|15131|08.
    |08:>.|11T|03qw |111337|08:|113|08/|1113|08.

    --- Mystic BBS v1.12 A44 2020/01/24 (Linux/64)
    * Origin: deadbeatz.org (21:2/123)
  • From g00r00@21:1/163 to Alterego on Sun Jan 26 16:58:47 2020
    out today. I do have the Pi3 that I use to compile Mystic maybe I ca my BBS up on that too for testing, but testing on a Pi is very very t consuming.

    So testing on any platform shouldnt be time consuming - and if you are
    up for it, I'd be willing to help you make it easier.

    Well in this case we are talking about me specifically being able to test packets on my BBS to fix a SEEN-BY issue so its something I need to do myself.

    But you are more than welcome to help test stuff. I put things up in the pre-alpha area for anyone to help!

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)
  • From Oli@21:1/151 to g00r00 on Mon Jan 27 09:30:57 2020
    25 Jan 20 11:21, you wrote to me:

    And it's really annoying. Just because it happens to have
    some advantages for Mystic BBS users on a 80x25 terminal
    doesn't mean

    It has nothing to do with Mystic BBS. It was requested by
    people who saw problems with legacy software that can't
    handle text longer than 80 characters, offline readers,
    the mess NNTP was making (there was a huge push for NNTP
    gatin back in the day).

    NNTP gating and offline readers are seperate issues. They are not fidonet technology. Nobody said you should not prewrap messages exported for offline reading (QWK).

    You seem to have almost no context in history or the
    reason things are done the way they are.

    I don't know about what history you are refering to. I joined Fidonet in 1993, first as a point than as node running a BBS and serving several points. Long lines that can be dynamically wrapped were always the norm not the exception. There is also a strong agreement that you must not alter mails passing through your system.

    There is also not one technical reason to add <CR>
    characters for exported mail or to mails imported to the
    JAM base. Word wrapping can be dynamically applied in the
    message reader or the NNTP server.

    Sure they can. Now go back and tell the 50,000 DOS,
    Atari, Commodore, etc packages that haven't had updates in
    25-30 years so they can release new version that can
    handle it. :)

    Can you (or someone else provide) some real world examples instead of some imaginary number? I wonder how these programs handled fidonet messages with long lines 25 to 30 years ago. Don't you think there was plenty of time to fix this obscure software that maybe nobody uses anymore. Let's face it, closed source communication software that doesn't evolve with the ecosystem will wither away at some point.

    Please disable it ASAP. It introduces unnecessary
    problems and we wasted

    Its such a huge problem that no one has brought it up in a
    decade. The "problems" it introduced was that message
    content doesn't get lost at the expense of a line being
    wrapped. One is horrible,

    don't be a drama queen.

    and one is a visual line wra
    that is hardly a big deal given how few people are using
    more than 80 column displays.

    how about less than 80 columns? how about adding quoting characters in front?

    and you are still ignoring the real dupes it produces in fsxnet.

    The latter was universally agreed to be the best approach
    by people actually using software.

    You obviously live in another bubble. I discovered all the bugs I reported by actually using common FTN software. Were are the people and voices that universally agreed on this? I didn't hear any in the last couple of weeks and months

    Its interesting you're pushing so hard on this but (for
    example) you don't seem to care about software using
    things like MSGID that are not compatible with old
    software despite the FTN people themselves saying its not
    intended to be used that way.

    It looks m like a proper fido address to me. Please file a bug report to the golded developers. Their might be a chance that it gets fixed.

    Even if it was not intended to be used with 5D addresses no software should choke on it. It should expect an address in any format, there is no promise that the address is an FTN address.

    I agree its time to revisit it, but you seem to have a
    knack at trying to paint every little issue as the end of
    the world. Its not.

    GOTO FIDONEWS

    for discussions about climate change, it's a hot topic there ;)



    * Origin: 🌈 (21:1/151)
  • From g00r00@21:1/108 to Oli on Mon Jan 27 15:38:12 2020
    NNTP gating and offline readers are seperate issues. They are not fidonet technology. Nobody said you should not prewrap messages exported for offline reading (QWK).

    And neither is posting from outside BBS using clients and websites on columns greater than 80, something almost zero people ever did until the last couple of years.

    NNTP gating and old software have historically been a much more relevant topic than the single obscure use-case you have. Its not hard for most people to see why I might make moves that better supported the former.

    I don't know about what history you are refering to. I joined Fidonet in 1993, first as a point than as node running a BBS and serving several

    I don't know who you are, and if your post history is any indication you just showed up a few months ago. Lets not pretend you have some decades long history with this stuff just because you used a BBS in the 90s and decided to come back 25 years later.

    anymore. Let's face it, closed source communication software that
    doesn't evolve with the ecosystem will wither away at some point.

    I agree with this, which is why I said I think its time to revisit it. But for some reason you just can't let it go at that, and you're going to push this to the point where I just ignore it next alpha and twit filter you.

    don't be a drama queen.

    A non-drama queen would have came here and let the problem be known and then let it go when I explained why it is that way while agreeing to look into it.

    I think you could benefit from gaining a little self-awareness.

    and you are still ignoring the real dupes it produces in fsxnet.

    I have not had Avon come to me once in all of fsxNet existence to talk to me about the large dupe problem in fsxNet created by the wrapping feature. And unlike you, I've been involved since its beginning.

    Gee, its almost like you're being overly dramatic about it. :)

    (You're also ignoring network topology, circular path checking and all of the reasons why its less of a problem in a real world scenario.)

    Can you (or someone else provide) some real world examples instead of
    some imaginary number? I wonder how these programs handled fidonet

    Sure! Renegade BBS software at one time one of the most widely used BBS software in the world is one. Here's some code from Renemail to illustrate:

    "until ((nos = #13) or (c in [#13,#141]) or ((length(msgtxt) > 79)"

    Its almost like the person whose been doing this for 25 years knows more than the person who just popped up a few months ago! Who knew?

    You obviously live in another bubble. I discovered all the bugs I
    reported by actually using common FTN software. Were are the people and voices that universally agreed on this? I didn't hear any in the last couple of weeks and months

    I think its obvious which one of us has the knowledge and which one of us has an obscure use-case that they can't let go. I've already agreed to look at it, so I can't imagine what you're trying at accomplish here.

    The only actual bug I fixed recently was the SEEN-BY bug, and that went unnoticed for probably 10 years because it was so un-impactful.

    If you were actually around, you'd know that the MYSTIC echo used to be the most popular echo in FidoNet during the time I was adding in native echomail functionality. There was hardly a bubble and things were widely discussed
    (and still are when people bring it up).

    I am open to constructive feedback and if you can't see that from the discussion here, then its only because you're continuing to ignore the stuff right in front of you.

    --- Mystic BBS v1.12 A44 2020/01/27 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Phoobar@21:2/147 to g00r00 on Mon Jan 27 14:09:31 2020
    Not a programmer or know the specifics of how this works the way it does...but is there a way to add being able to validate a new user while they are online without needing them to log off & back on?

    Thank you.

    Phoobar/ACME BBS-Member of fsxNet/WWIVNet/SciNet/SpookNet.

    --- Mystic BBS v1.12 A44 2020/01/27 (Windows/32)
    * Origin: ACME BBS-I am Wile E Ki-oh-tay, super genius (21:2/147)
  • From Bucko@21:4/131 to Phoobar on Mon Jan 27 19:10:01 2020
    On 27 Jan 2020, Phoobar said the following...

    Not a programmer or know the specifics of how this works the way it does...but is there a way to add being able to validate a new user while they are online without needing them to log off & back on?

    Thank you.

    You can do a Email Validation for them, they get a code sent to their email address and enter the code and the BBS ups their access to a access level of your choice.. I do believe it gives them the new access immediately. If you go back a month or so I explained in detail how I do it.. IT works great. If you can't find it let me know and I will repost how I do it..

    --- Mystic BBS v1.12 A44 2020/01/24 (Windows/32)
    * Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)
  • From g00r00@21:1/108 to Phoobar on Mon Jan 27 19:08:41 2020
    Not a programmer or know the specifics of how this works the way it does...but is there a way to add being able to validate a new user while they are online without needing them to log off & back on?

    --- Mystic BBS v1.12 A44 2020/01/27 (Windows/32)

    If you are using Windows then you can go into their node window where the
    user is logged in and use Alt-E to open the user editor

    --- Mystic BBS v1.12 A44 2020/01/27 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Captain Obvious@21:1/157 to Bucko on Mon Jan 27 21:42:41 2020
    On 27 Jan 2020, Bucko said the following...

    email address and enter the code and the BBS ups their access to a
    access level of your choice.. I do believe it gives them the new access immediately. If you go back a month or so I explained in detail how I do

    I'm using it as well. I'm not 100% sure if it bumps them up immediately
    though. Will have to test that out.

    -=>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)
  • From maskreet@21:1/114 to Phoobar on Mon Jan 27 21:56:17 2020
    On 27 Jan 2020, Phoobar said the following...

    Not a programmer or know the specifics of how this works the way it does...but is there a way to add being able to validate a new user while they are online without needing them to log off & back on?

    There's the email verification that's in there, and I *think* you don't have
    to be logged off and back on to work it. Or you could just set everyone's access to normal user access on signup. =)

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: throwbackbbs.com -\- meriden, ct -\- (21:1/114)
  • From Analog@21:2/123 to phoobar on Mon Jan 27 21:07:07 2020
    Not a programmer or know the specifics of how this works the way it does...but is there a way to add being able to validate a new user wh they are online without needing them to log off & back on?

    There's the email verification that's in there, and I *think* you don't have to be logged off and back on to work it. Or you could just set everyone's access to normal user access on signup. =)

    I have a fun little auto validator script I found somewhere that just kind of makes it look it's doing something and then flips their access level to a higher level. This isn't a proper Mystic Validator email routine but I had it for 8 years and it was cool. No logoff and back on.

    If you want the script, hit me up and I'll get it to you.

    |19|15┌─|16|07┤ |08De|07ad|15be|07a|08tz b|07b|15s
    |07└─┘├─┐ |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
    |11■ |07└|19|15─|16|07┘ |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
    |12≡|15A|07n|08al|07o|15g|12≡ |08:>.|13F|05dn |131|08:|13305|08/|132|08.
    |08:>.|15S|08ci |1577|08:|151|08/|15131|08.
    |08:>.|11T|03qw |111337|08:|113|08/|1113|08.

    --- Mystic BBS v1.12 A44 2020/01/24 (Linux/64)
    * Origin: deadbeatz.org (21:2/123)
  • From Phoobar@21:2/147 to Bucko on Tue Jan 28 00:32:31 2020
    You can do a Email Validation for them, they get a code sent to their email address and enter the code and the BBS ups their access to a
    access level of your choice.. I do believe it gives them the new access immediately. If you go back a month or so I explained in detail how I do it.. IT works great. If you can't find it let me know and I will repost how I do it..

    Don't remember it...but please repost it. Will certainly do it.

    Thank you again!!!

    ACME BBS-Member of fsxNet/WWIVNet/SciNet/SpookNet/FidoNet/MicroNet.

    --- Mystic BBS v1.12 A44 2020/01/27 (Windows/32)
    * Origin: ACME BBS-I am Wile E Ki-oh-tay, super genius (21:2/147)
  • From Phoobar@21:2/147 to g00r00 on Tue Jan 28 00:35:11 2020
    If you are using Windows then you can go into their node window where the user is logged in and use Alt-E to open the user editor

    HOT DOG! Will be doing that with some local folks from work...so they don't have to log in twice.

    Thanks again!

    ACME BBS-Member of fsxNet/WWIVNet/SciNet/SpookNet/FidoNet/MicroNet.

    --- Mystic BBS v1.12 A44 2020/01/27 (Windows/32)
    * Origin: ACME BBS-I am Wile E Ki-oh-tay, super genius (21:2/147)
  • From Phoobar@21:2/147 to maskreet on Tue Jan 28 00:43:57 2020
    There's the email verification that's in there, and I *think* you don't have to be logged off and back on to work it. Or you could just set everyone's access to normal user access on signup. =)

    Darn it...having to learn something again. ;) Was something I had read which mentioned it...but with wanting to get everything running...just put it in
    the back of my mind. Now that I know what it is...gonna be using it.

    ACME BBS-Member of fsxNet/WWIVNet/SciNet/SpookNet/FidoNet/MicroNet.

    --- Mystic BBS v1.12 A44 2020/01/27 (Windows/32)
    * Origin: ACME BBS-I am Wile E Ki-oh-tay, super genius (21:2/147)
  • From Phoobar@21:2/147 to Analog on Tue Jan 28 00:46:42 2020
    I have a fun little auto validator script I found somewhere that just
    kind of makes it look it's doing something and then flips their access level to a higher level. This isn't a proper Mystic Validator email routine but I had it for 8 years and it was cool. No logoff and back on.

    Fantastic! Kick it up here or over here & will get it running.

    ACME BBS-Member of fsxNet/WWIVNet/SciNet/SpookNet/FidoNet/MicroNet.

    --- Mystic BBS v1.12 A44 2020/01/27 (Windows/32)
    * Origin: ACME BBS-I am Wile E Ki-oh-tay, super genius (21:2/147)
  • From g00r00@21:1/108 to Captain Obvious on Tue Jan 28 13:00:26 2020
    email address and enter the code and the BBS ups their access to a access level of your choice.. I do believe it gives them the new acce immediately. If you go back a month or so I explained in detail how I

    I'm using it as well. I'm not 100% sure if it bumps them up immediately though. Will have to test that out.

    Its an option to have it upgrade your access, and it should happen
    immediately.

    --- Mystic BBS v1.12 A44 2020/01/28 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From g00r00@21:1/108 to maskreet on Tue Jan 28 13:01:47 2020
    There's the email verification that's in there, and I *think* you don't have to be logged off and back on to work it. Or you could just set everyone's access to normal user access on signup. =)

    There was a bug at some point but its fixed in A44 pre-alphas.

    --- Mystic BBS v1.12 A44 2020/01/28 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From g00r00@21:1/108 to Phoobar on Tue Jan 28 13:44:18 2020
    I have a fun little auto validator script I found somewhere that just kind of makes it look it's doing something and then flips their acces level to a higher level. This isn't a proper Mystic Validator email routine but I had it for 8 years and it was cool. No logoff and back

    Fantastic! Kick it up here or over here & will get it running.

    Mystic already does e-mail auto-validation. You can also automatically
    upgrade users using a menu command too.

    --- Mystic BBS v1.12 A44 2020/01/28 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Phoobar@21:2/147 to g00r00 on Tue Jan 28 13:04:06 2020
    I have a fun little auto validator script I found somewhere that
    Fantastic! Kick it up here or over here & will get it running.
    Mystic already does e-mail auto-validation. You can also automatically upgrade users using a menu command too.

    Have today off...so off to the dox I go.

    Thank you again!

    ACME BBS-Member of fsxNet/WWIVNet/SciNet/SpookNet/FidoNet/MicroNet.

    --- Mystic BBS v1.12 A44 2020/01/28 (Windows/32)
    * Origin: ACME BBS-I am Wile E Ki-oh-tay, super genius (21:2/147)
  • From Oli@21:1/151 to p00p on Tue Jan 28 22:03:34 2020
    I think its obvious which one of us has the knowledge and which
    one of us has an obscure use-case that they can't let go.

    let's pour "experimental" down the drain


    --- Garbage v1.12💩A44
    * Origin: đŸĻ„ 🌈 (21:1/151)
  • From Captain Obvious@21:1/157 to g00r00 on Tue Jan 28 17:30:14 2020
    On 28 Jan 2020, g00r00 said the following...

    Its an option to have it upgrade your access, and it should happen immediately.

    Ok, cool. I've only had a couple of new users since I added it and I wasn't around when they went through the process so wasn't sure if it had been immediate or not.

    -=>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)
  • From Bucko@21:4/131 to Phoobar on Tue Jan 28 18:28:01 2020
    On 28 Jan 2020, Phoobar said the following...


    Don't remember it...but please repost it. Will certainly do it.

    Thank you again!!!


    No problem I will do it later tonight when i get into my "cave"...

    --- Mystic BBS v1.12 A44 2020/01/27 (Windows/32)
    * Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)
  • From g00r00@21:1/108 to Captain Obvious on Tue Jan 28 18:26:28 2020
    Its an option to have it upgrade your access, and it should happen immediately.

    Ok, cool. I've only had a couple of new users since I added it and I wasn't around when they went through the process so wasn't sure if it
    had been immediate or not.

    Well its supposed to be, but that doesn't mean it works :)

    I have yet to test it since I made the last round of changes to that stuff,
    but I plan to get it set up on my BBS soon (ish).

    --- Mystic BBS v1.12 A44 2020/01/28 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From g00r00@21:1/108 to Phoobar on Tue Jan 28 18:45:30 2020
    Mystic already does e-mail auto-validation. You can also automatical upgrade users using a menu command too.

    Have today off...so off to the dox I go.

    Thank you again!

    If you have troubles let me know, the documentation on some areas is bad or
    at least not well organized.

    --- Mystic BBS v1.12 A44 2020/01/28 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Phoobar@21:2/147 to Bucko on Tue Jan 28 23:03:14 2020
    Don't remember it...but please repost it. Will certainly do it.
    No problem I will do it later tonight when i get into my "cave"...

    No problem. Gotta do 2 more LONG days in the mine...then 3 days off. ;)

    ACME BBS-Member of fsxNet/WWIVNet/SciNet/SpookNet/FidoNet/MicroNet.

    --- Mystic BBS v1.12 A44 2020/01/28 (Windows/32)
    * Origin: ACME BBS-I am Wile E Ki-oh-tay, super genius (21:2/147)
  • From Phoobar@21:2/147 to g00r00 on Tue Jan 28 23:10:09 2020
    Mystic already does e-mail auto-validation. You can also automa upgrade users using a menu command too.
    If you have troubles let me know, the documentation on some areas is bad or at least not well organized.

    Several months ago while looking around to get back into it...Mystic & other modern BBS software documentation is a dream compared to some of the stuff
    out there in the "golden" age.

    I appreciate the encouragement. Made me smile that there are those out there more than willing to help. Thank you!

    ACME BBS-Member of fsxNet/WWIVNet/SciNet/SpookNet/FidoNet/MicroNet.

    --- Mystic BBS v1.12 A44 2020/01/28 (Windows/32)
    * Origin: ACME BBS-I am Wile E Ki-oh-tay, super genius (21:2/147)
  • From g00r00@21:1/120 to apam on Tue Jan 21 08:05:29 2020
    I only noticed because I've been hex editing packets to / from mystic. Trying to figure out why mystic won't route my netmails, yet both HPT
    and crashmail do. Mystic routes other netmails fine, but I can't for the life of me figure out what I am doing wrong.

    If you want to send me over an example PKT I can take a look at it when I get some time (probably this weekend). You can e-mail to mysticbbs@gmail.com

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)
  • From Pequito@21:1/120 to g00r00 on Tue Jan 21 15:32:03 2020
    On 20 Jan 2020 &4, g00r00 said the following...

    Found one item seems to be limited on the path for the theme location example say I wanted to do:

    /mystic/data/theme/ansi/menu instead of menus, this could be me or i there a short way to do that from the fallbacks provided?

    You don't have separate paths for those anymore. You have a root theme directory and all themes go in there. So there is only one path now
    that is configurable and thats where your themes go (in system paths).

    I still would like to be able to customize the names of the folders
    regardless if possible as a request :)

    Cheers!
    Pequito

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)
  • From g00r00@21:1/120 to Pequito on Tue Jan 21 16:55:27 2020
    I still would like to be able to customize the names of the folders regardless if possible as a request :)

    You can customize the theme root and theme folder name, and that is it for now.

    I might put in the ability to change 'text', 'menus', and 'scripts' someday but it just adds a bunch of complexity to the system just to change "menus" to "menu" so for now I am going to focus on getting other things theme-related finished like the editor. I can go back and revisit and see what should be added afterwards!

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)