On 19 Nov 2021 at 09:55a, g00r00 pondered and said...
 
 g0> Its probably going to be a bit time consuming to do so I have to get
 g0> some time aside to experiment with how it might work. I've barely been
 g0> touching any code lately unfortunately (just little touch ups mostly).
 g0> Almost all of my time is spent just responding to stuff. :(
 g0> It might not be until the new year before things ease up for me.  I hope
 
Hey there :)

It's all good, no stress regarding looking at this one, if you find time in 2022 then that would be great. I think it would be something worth exploring so that at some high level there was logic that could negate such issues if Mystic was tossing such stuff from other nodes.

I accept the comments from others about how a node should be the main area of focus to fix any issue if it's the one generating the problem. My perspective was simply that if a HUB aka tosser could have some logic built in to it such that it could assist in negating echomail area flooding onwards to others, then that would be a useful thing to implement as well.

 g0> I can get more time before that to see what could be done.  First goal
 g0> will be to get A47 out the door before I add anything new to the tosser.
 g0> For now I am trying to handle support issues/reported issues as much as
 g0> I can so I can accomplish that goal.

I'm looking forward to seeing A47 in the public domain, I'll have some videos to work on / update when it does :)

Best, Paul

--- Mystic BBS v1.12 A47 2021/11/06 (Linux/64)