• Stats

    From Avon@21:1/101 to All on Wednesday, March 11, 2020 22:22:42
    I've been working on one of the stats programs tonight and found a workaround to get things running again for it. Hence the test posts.

    I set things up to post stats to some higher traffic echos along with everything to the BOT echo also.

    All going to plan you should see these run weekly now late on a Sunday (my time).. let's see how we go :)

    --- Mystic BBS v1.12 A46 2020/03/09 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to All on Thursday, March 12, 2020 22:17:07
    Did some more work on some legacy stats tools I had been using tonight. I
    think for these ones I'll need to wait 7 days before I start using them as
    they look at the arrival date/time of the packet.. and with a rescan of a
    base I was testing against there were a lot of 'old' messages showing as
    'new' for the last 7 days :)

    --- Mystic BBS v1.12 A46 2020/03/12 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to All on Sunday, March 15, 2020 12:01:33
    After phaffing about with more settings I am going to also restore the second set of stats reporting to the echoareas starting this Sunday.

    The first week of data will be incorrect but in another 7 days I think it should be fine.

    The reports that will be wrong to start with look like this

    [snip]

    =================================================
    fsxNet - Weekly Message Statistics (FSX_NET)
    =================================================

    This report covers 104 messages that were received at fsxNet HUB (21:1/100) between the period of 2020-03-11 21:33:25 and 2020-03-15 08:17:05.

    If you spot errors or omissions please contact Paul Hayton (21:1/101)

    ============================================================================= Authors =============================================================================

    Rank Name Msgs Bytes Quoted

    1. Avon <21:1/101> 37 32722 11.30%
    2. Oli <21:1/151> 16 14651 44.89%
    3. alter ego <21:2/116> 15 13298 20.84%
    4. Black Panther <21:1/186> 9 5957 31.64%
    5. Al <21:4/106> 7 8190 45.68%
    6. alterego <21:3/100> 3 2307 10.01%
    g00r00 <21:1/108> 3 1492 18.90%
    8. Vk3jed <21:1/109> 2 1459 75.60%
    Joacim Melin <21:2/130.0> 2 1219 56.93%
    Phoobar <21:2/147> 2 564 63.83%
    Spectre <21:3/101> 2 209 28.23%
    12. fsxNet HUB <21:1/100> 1 4035
    Embalmed <21:4/166> 1 299 32.44%
    pokeswithastick <21:2/159> 1 200 38.50%
    x1pepe <21:1/150> 1 125

    A total of 20 people were identified (senders and recipients).

    ============================================================================= Sent / Received =============================================================================

    [snip]

    The issue is that the tool I am using looks at the arrival time stamp of the messages in a JAM base. Because I am using a fresh JAM base populated by contents that include a dump of posts loaded because of a rescan the reports will show far more messages posted in the first report run than there were.

    But this *should* resolve in 7 days time when then next run occurs.

    I've opted to run this reporting this week to check I have posting
    permissions set up correctly and I figure there's still some interesting
    stuff to be found in the data posted :)

    --- Mystic BBS v1.12 A46 2020/03/12 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)