• Sorry for being so silent for the past couple of months.

    From Ozz Nixon@1:275/301 to Ozz Nixon on Mon Nov 20 19:27:34 2017
    Hello Ozz.

    29 May 17 17:08, I wrote to mark lewis:

    Re: Sorry for being so silent for the past couple of months.
    By: mark lewis to Ozz Nixon on Mon May 29 2017 10:51 am

    On 2017 May 29 08:46:52, you wrote to All:

    Why? Because I can, Because I want to, therefore, I am.
    :)

    to Fidonet has given me the ability to see too many tossers are
    not implementing REPLY: correctly or at all.
    strictly speaking, that is the message editor's responsibility...
    when it

    Not really meaning to talk to myself, just saw this and it triggered a question. My /301 system at the house is currently running POP.OZZ (ie. I recompiled it and started cleaning up the code) in a DOS Box and my USB 56k Modem. It is running Windows 10/32bit Host - running Husky and GoldED+/W32 so I
    can communicate to the world instead of having to telnet into Carol's system. And then back in the DOS Box is QuickBBS v2.81-GA2 (ie. I recompiled QuickBBS to use Squish to co-exist with (A) all years messages and (B) GoldED and Husky).

    * So that is the environment of 301, the question(s) are:
    1. I want to have the correct FLAGS, and not bloviate - so on this list:
    [ ] V21 ITU-T V21 300 bps full duplex
    [ ] V22 ITU-T V22 1200 bps full duplex
    [ ] V29 ITU-T V29 9600 bps half duplex
    [ ] V32 ITU-T V32 9600 bps full duplex
    [ ] V32b ITU-T V32bis 14400 bps full duplex
    [ ] V33 ITU-T V33
    [ ] V34 ITU-T V34 28800 bps full duplex
    [ ] H96 Hayes V9600
    [ ] HST USR Courier HST up to 9600
    [ ] H14 USR Courier HST up to 14400
    [ ] H16 USR Courier HST up to 16800
    [ ] MAX Microcom AX/96xx series
    [ ] PEP Packet Ensemble Protocol
    [ ] CSP Compucom Speedmodem
    [ ] ZYX Zyxel series
    [ ] VFC V.Fast Class
    [ ] V32T V.32 Terbo
    [ ] V42 ITU-T LAP-M error correction w/fallback to MNP 1-4
    [ ] V42b ITU-T V.42 LAP-M plus V.42bis BTLZ data compression
    [ ] MNP Microcom Networking Protocol error correction

    Which ones inherit other once... like I assume V22 for example implies V21? I am trying to make a simple matrix form for others - but need the first round for myself ;-)

    2. Right now, I picked up mail from 275/100 addressed to my first BBS system as
    275/362 w/ AKA 275/300. To get it to my 301 BBS at home, up until today I just bounced the PKTs over and ran 362 as my AKA. As of tonight, since I am posting replies to everyone, I has set everything back to /301 destination /300, which should send that to /100. The question is (to make sure I do not foobar)... Is /301 support to put in the seen-by /301 and /300 only? And then my /300 support
    to append /362 and /100 and push to 100? I am not 100% sure I have HUSKY setup correctly, and want to make sure my tosser (I wrote) on /300 catches anything from me that is incorrect.

    * And since I took the tie to describe /301's setup... anyone familiar with Rick's GameSvr, or some other solution that will allow me to run DOS games under 32bit Windows/DOSBox environment? (Eventually Rhenium goes back online, my 32bit/64bit FTN Mailer) but I want to support some of the old DOS BBS doros - like Chess, for my father who loves to play... and the old Chess DOOR I found
    is dead 16bit Fossil only.

    Thanks for ANY/ALL *positive* feedback ;-)
    Ozz

    --- GoldED+/W32 1.1.4.7
    * Origin: Because I can! (1:275/301)
  • From Ozz Nixon@1:275/301 to mark lewis on Mon Nov 20 19:49:24 2017
    Hello mark.

    29 May 17 19:05, you wrote to me:


    i'm not aware of a FTN spec concerning RE:... some software may strip
    it off on importation into the local message bases... some drop it on replies... it isn't that critical and software really shouldn't be
    linking on subject lines these days anyway... especially considering
    how the subject rarely ever gets changed when the topic drifts from
    one thing to another... then there are some users that specifically
    change the subject so as to try to ensure that their posts are fully distributed and not caught as dupes by older brain dead software...

    Okay, my counter point to this is some environemnts are not posting the msgid of their reply to as "REPLY". This is where my re-threading code is failing over to "by subject", "by RE:" and "by timestamp" to try to keep the integrity / sanity of the reader.

    I have kept the PKTs for the this whole year to help me stress test my tosser and message base classes for performance. And I have noticed certain (keeping the names private for now) systems are posting replies with either NEWMSGID in the REPLY instead of the original (like it was renumbered somewhere along the way to them or durring their system's TOSS phase), and I happen to fail to by subject/re/timestamp and do not find re on the subject - so I fail to "must be a new thread same subject".

    Am I missing something??

    Ozz

    --- GoldED+/W32 1.1.4.7
    * Origin: Because I can! (1:275/301)
  • From Ozz Nixon@1:275/301 to Ozz Nixon on Mon Nov 20 19:56:58 2017
    Hello Ozz.

    02 Jun 17 21:25, I wrote to Nancy Backus:

    Cafe celebrated it's 30day open day today - going well.

    7 Months open (almost 8) and we had our first Inspection from the Helath department since go-live, and passed. This state does not give you a 100 or less score, or A+ to F... just "passed/failed".

    Projects wise:
    ExchangeBBS - getting closer to being open.
    Tosser - Done/Working fine.
    BinkP - Poller is finished, Listener not finished.
    FTSC001 - Poller is finished, Listener not finished.
    WaZoo and YooHoo - R&D/Testing phase right ow.
    Ansi FSE (Full Screen Editor) working on UTF-8 then BBS goes public.

    Now the sad thing, none of the above has changed ... ARG! I got myself so distracted on getting a 16bit Modem based environment setup and working at the house - to finally (Yesterday 11/19, deciding WHO CARES about 16bit?!). So, now
    I am back to my original goals of porting QuickBBS source to 32bit and expanding to support Squish and JAM message bases. Even Steve's GoldBase has limitations that I have exceeded.

    So, anyone else realize they have wasted 6 months? ;-)


    Ozz

    --- GoldED+/W32 1.1.4.7
    * Origin: Because I can! (1:275/301)
  • From mark lewis@1:3634/12.73 to Ozz Nixon on Tue Nov 21 03:28:46 2017
    On 2017 Nov 20 19:27:34, you wrote to you:

    * So that is the environment of 301, the question(s) are:
    1. I want to have the correct FLAGS, and not bloviate - so on this list:
    [... trim modem flags list ...]
    Which ones inherit other once... like I assume V22 for example implies V21?

    see section 5.11 of this document http://ftsc.org/docs/fts-5001.006

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... A man with an erection is in no need of advice.
    ---
    * Origin: (1:3634/12.73)
  • From mark lewis@1:3634/12.73 to Ozz Nixon on Tue Nov 21 03:32:58 2017
    On 2017 Nov 20 19:49:24, you wrote to me:

    i'm not aware of a FTN spec concerning RE:... some software may strip
    it off on importation into the local message bases... some drop it on
    replies... it isn't that critical and software really shouldn't be
    linking on subject lines these days anyway... especially considering
    how the subject rarely ever gets changed when the topic drifts from
    one thing to another... then there are some users that specifically
    change the subject so as to try to ensure that their posts are fully
    distributed and not caught as dupes by older brain dead software...

    Okay, my counter point to this is some environemnts are not posting
    the msgid of their reply to as "REPLY". This is where my re-threading
    code is failing over to "by subject", "by RE:" and "by timestamp" to
    try to keep the integrity / sanity of the reader.

    make it simple... if it has RE: import it but ignore it during thread linking... but wait... i thought you said you were using SQUish message base? it has several limits that you might want to know of... message time stamps are
    limited to 2 second imcrements (because of using DOS file time stamp format)...
    a max of ten messages linked to one... in this age of dupes flying about to try
    to ensure full distribution of a message, the time stamp may result in false negatives... maybe someone rescanned a message and sent it back out into the network... if it came from a SQUish base, the time stamp will be even and may very well not be the same as the original time stamp... that means that two copies of the message may be identical in every way except the time stamp... at
    least one BBS package had this problem... when it was discovered and the search
    ended, that package was fixed... so it is possible that you have some of those messages that you're trying to work with in your archives...

    I have kept the PKTs for the this whole year to help me stress test my tosser and message base classes for performance. And I have noticed
    certain
    (keeping the names private for now) systems are posting replies with
    either
    NEWMSGID in the REPLY instead of the original (like it was renumbered somewhere along the way to them or durring their system's TOSS phase), and I happen to fail to by subject/re/timestamp and do not find re on the subject - so I fail to "must be a new thread same subject".

    Am I missing something??

    no, you're seeing the schtuff... some of those without REPLY lines are QWK offline mail uploads... QWK doesn't know about FTN control lines so it is possible that the door adds the MSGID but it may not know which message a new post is a reply to so it can't/doesn't created a REPLY line... not much you can
    do about that... linking on subject is just bad... sorting on time is also bad... you can't really tell if the time in a message is the originator's local
    time or UTC or what... you can try to figure it out and possibly use the TZUTC control line to help but it is still rough... back when the HMB was all the rage, we decided to not worry about sorting the messages... just toss them as they arrive... it isn't that big a deal anyway... we read from the first unread
    message to the last in whatever order they arrive...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Poor Mexico, so far from God and so near the United States - P Diaz
    ---
    * Origin: (1:3634/12.73)
  • From Nancy Backus@1:229/452 to Ozz Nixon on Fri Nov 24 00:44:42 2017
    Quoting Ozz Nixon to Ozz Nixon on 20-Nov-2017 19:56 <=-

    02 Jun 17 21:25, I wrote to Nancy Backus:
    Cafe celebrated it's 30day open day today - going well.

    I see you mention me.... ;)

    7 Months open (almost 8) and we had our first Inspection from the
    Helath department since go-live, and passed. This state does not give
    you a 100 or less score, or A+ to F... just "passed/failed".

    Congratulations on the pass... Definitely a good sign... :) I trust
    you are having reasonably steady business at the cafe....?

    Projects wise:
    ExchangeBBS - getting closer to being open.
    Tosser - Done/Working fine.
    BinkP - Poller is finished, Listener not finished.
    FTSC001 - Poller is finished, Listener not finished.
    WaZoo and YooHoo - R&D/Testing phase right ow.
    Ansi FSE (Full Screen Editor) working on UTF-8 then BBS goes public.

    Now the sad thing, none of the above has changed ... ARG! I got myself
    so distracted on getting a 16bit Modem based environment setup and
    working at the house - to finally (Yesterday 11/19, deciding WHO CARES about 16bit?!). So, now I am back to my original goals of porting
    QuickBBS source to 32bit and expanding to support Squish and JAM
    message bases. Even Steve's GoldBase has limitations that I have
    exceeded.
    So, anyone else realize they have wasted 6 months? ;-)

    I'm sure they weren't totally wasted... just not spent on the above projects.... and kept you busy... ;)

    ttyl neb

    ... Cannibal Tip #102: First listen to sermon, THEN eat missionary.

    --- EzyBlueWave V3.00 01FB001F
    * Origin: Tiny's BBS - http://www.tinysbbs.com (1:229/452)