Hi !

I am making a python script that runs with mystic -y miapp.mpy in a
separate process

Is it possible to use the NS command to send a message to an active
node, specifying the node number and the message as parameters?

example:

import mystic_bbs as bbs

node = 1
msg = "hello"
bbs.menucmd ("NS", node, msg)

thanks!
--- SBBSecho 3.14-Linux
* Origin: Dock Sud BBS - http://bbs.docksud.com.ar (4:902/26)

I am making a python script that runs with mystic -y miapp.mpy in a separate process

Is it possible to use the NS command to send a message to an active
node, specifying the node number and the message as parameters?

example:

import mystic_bbs as bbs

node = 1
msg = "hello"
bbs.menucmd ("NS", node, msg)

Yes. You send the node number and then the message separated by the semi-colon. Use 0 as the node number if you want to send a system-wide broadcast message. For example:

menucmd ("NS", "1;This message is for node 1")

or

menucmd("NS", "0;This is a broadcast to all users")

... Redundant book title: DOS For Dummies

--- Mystic BBS v1.12 A47 2021/09/23 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hi James

Will drop you an email. Have found something a little strange in the way a an incoming packet is being tossed. Will send you some pkt's to have a look at. This relates to the current Win/64 pre-alpha build.

Best, Paul

--- Mystic BBS v1.12 A47 2021/09/29 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Will drop you an email. Have found something a little strange in the way
a an incoming packet is being tossed. Will send you some pkt's to have a look at. This relates to the current Win/64 pre-alpha build.

Sounds good I'll try to take a look at it this weekend!

... I'm not a complete idiot... Several parts are missing!

--- Mystic BBS v1.12 A47 2021/09/23 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

On 23 Oct 2021 at 09:54a, Paul Hayton pondered and said...

On 22 Oct 2021 at 11:54a, g00r00 pondered and said...

Sounds good I'll try to take a look at it this weekend!

Thanks for having a look.

Just wondering if you spotted anything with the packets I sent you?

--- Mystic BBS v1.12 A47 2021/09/29 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Thanks for having a look.

Just wondering if you spotted anything with the packets I sent you?

I started to look at it but I only really got as far as unzipping and looking through the PKTs and information you sent. Nothing looked out of ordinary with the PKT itself so I have to set up the nodes the packet originated from, the downlink, and try to mimic the setup to see if I can reproduce the problem.
The other error sent regarding the crash when tossing was much quicker to test/fix so thats why I got that done first.

I ended up not being home at all this weekend and it looks like I will be away next weekend and possibly the weekend after that, so I didn't get to spend the time I wanted to on things. I hope to get some time tonight to look at it since Tues-Thurs I'll be unavailable + gone the weekend...

Busy times lately, unfortunately! I think I should be able to set aside an hour to see what I can come up with tonight though.

... "I am" is the shortest sentence in English. Is 'I do' the longest?

--- Mystic BBS v1.12 A47 2021/10/22 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Just wondering if you spotted anything with the packets I sent you?

Hey so good news. I had a meeting cancelled today when I normally eat lunch, so I was able to squeeze in an hour before work and an hour over lunch to get this resolved.

I'll build a new pre-alpha if you'd like to test it. One thing to note though is that this build requires you to reset the dupe database (delete echodupes.dat)

... Multitasking: Reading in the bathroom

--- Mystic BBS v1.12 A47 2021/10/25 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

On 25 Oct 2021, g00r00 said the following...

I'll build a new pre-alpha if you'd like to test it. One thing to note though is that this build requires you to reset the dupe database (delete echodupes.dat)

Thanks for this g00r00! I've updated and will test this out this my link with Tommi.

Appreciate all you do!


Jay

... Reality is for people who can't cope with their drugs.

--- Mystic BBS v1.12 A47 2021/10/25 (Raspberry Pi/32)
* Origin: Northern Realms (1:229/664)

On 25 Oct 2021 at 11:59a, g00r00 pondered and said...

Busy times lately, unfortunately! I think I should be able to set aside an hour to see what I can come up with tonight though.

It's all good, just whenever you're able to, I'm mindful we are all leading busy lives beyond BBS. Thanks again.

--- Mystic BBS v1.12 A47 2021/09/29 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 25 Oct 2021 at 02:25p, g00r00 pondered and said...

lunch, so I was able to squeeze in an hour before work and an hour over lunch to get this resolved.

I'll build a new pre-alpha if you'd like to test it. One thing to note though is that this build requires you to reset the dupe database (delete echodupes.dat)

OK cool, thanks for finding that time in your busy days and having a look. I'll update that HUB and re-run some tests with the node concerned and let you know how we got on.

--- Mystic BBS v1.12 A47 2021/09/29 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 25 Oct 21 14:25:39, G00R00 said the following to Paul Hayton:

I'll build a new pre-alpha if you'd like to test it. One thing to note thou is that this build requires you to reset the dupe database (delete echodupes.dat)

FYI, in the "I have a recipe for boiling water" catagory, I published a new version of D'Bridge which checks for duplicate MSGID's. It does this not by logging everything in one huge database but a seperate database per-system of message received, with the ability to place a cap on the number of entries to maintain. D'Bridge uses a Base36 formula for naming these tiny files.

I admit its still an overtly sloppy concept no matter what; I don't understand how MSGID came to be accepted as a "standard" for dupe-checking when CRC's of the header, Seen-by and circular Path detection works best. To me MSGID is just lazy programming. The vast majority of dupes over the years has been
from Sysops inadvertently rescanning their message-bases; which could be
nuked by just checking for dates X amount in the past.

I know about the Reply kludge and how it appeals to the obsessive-compulsive types to have threaded replies... but still... Ahh well. You get what I mean.

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

OK cool, thanks for finding that time in your busy days and having a
look. I'll update that HUB and re-run some tests with the node concerned and let you know how we got on.

Sounds great! Thanks.

I am guessing you will already see it but I also did that "flag1x" change too so it uses the lower cased letters for the flag now.

... Help! I can't find the "ANY" key.

--- Mystic BBS v1.12 A47 2021/10/25 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

On 26 Oct 2021 at 10:50a, g00r00 pondered and said...

OK cool, thanks for finding that time in your busy days and having a look. I'll update that HUB and re-run some tests with the node concer and let you know how we got on.

Sounds great! Thanks.

Yep that change you made seems to have fixed the issue the node was having getting their messages out. Thank you.

--- Mystic BBS v1.12 A47 2021/09/29 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)