Maybe we can disconnect that node from the bot area until the sysop
there can
get a better handle on his bot?
Taking bets on what happens first... Avon waking up (surely he's in
bed sleeping now lol) or Robert noticing his bot gone crazy...
My bet is avon waking up... but maybe if it's a net 2 node solaris
could interveine?
be great. I think the next time I do maint on the msg base I am going
to be
left with a msgbase full of these posts and little else!
There is a bot gone rogue in the FSX_BOT area, posting 6 or so
messages a minute from 21:2/136.
Maybe we can disconnect that node from the bot area until the sysop
there can get a better handle on his bot?
Look at the traffic flowing through the network though! ;)
I'm guessing it has something to do with daylight savings... There is probably an event that is getting stuck due to the time change.
There is a bot gone rogue in the FSX_BOT area, posting 6 or so messages
a minute from 21:2/136.
Maybe we can disconnect that node from the bot area until the sysop
there can get a better handle on his bot?
There is a bot gone rogue in the FSX_BOT area, posting 6 or so messag a minute from 21:2/136.
Maybe we can disconnect that node from the bot area until the sysop there can get a better handle on his bot?
It's late Monday my time, just logged in and found this, working to
delink the node from the echo now. Wow that's a lot of bot action.. :)
--- Mystic BBS v1.12 A47 2021/09/29 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
It's late Monday my time, just logged in and found this, working
to delink the node from the echo now. Wow that's a lot of bot
action.. :)
OK delinked from 2/100 for the FSX_BOT echo, have dropped him a
netmail.
I make it 8570 messages sent while connected.. phew :)
I just saw about 1000 in fido's BBS_ADS area. I deleted them and hope
that will be the end of it.. but we'll see.
I make it 8570 messages sent while connected.. phew :)
I just saw about 1000 in fido's BBS_ADS area. I deleted them and hope
that will be the end of it.. but we'll see.
I hope you are doing well. :)
Those were from a different system, so it looks like the time change did cause a bug in a bot software as BP was saying..
I hope it won't catch to many OP's unaware..
Well I'm a tad tired as it's late here and too early to message Todd
given his local time (around 4am) but yeah doing OK thanks :)
Have posted to James in fido suggesting a rate limiting function for MUTIL. I'm not sure how others handle such things but it seems like a
good idea to me for when bots go wild.
Yep... so a shift to daylight time or away from it?
Yep, we used to get up around 4am to milk the cows.. but I don't know if Todd has any cows there.. :)
That's going to be a tough one to do. I don't know of any tosser that
can detect that kind of flooding and turn the link off.
Back to standard time yesterday morning at 2am. We are heading into
winter here.
So what time is it now? Half past cow or closer to rooster o'clock? :)
It would be interesting to see if some logic could be built into a
tosser to do something like that, but it would need to track messages
into a base over x time and then decide if the rule had been broken.
that explains why I keep having BBQs here now :)
OK delinked from 2/100 for the FSX_BOT echo, have dropped him a netmail.
I make it 8570 messages sent while connected.. phew :)
I'll look at doing something that I think Rob is doing in Synchronet -
I didnt see any of those dupes because they all had the same
text body.
I guess seeing the same text body more than once, in a
short time frame, should be considered a dupe and dropped?
Have posted to James in fido suggesting a rate limiting function for MUTIL. I'm not sure how others handle such things but it seems like a good idea to for when bots go wild.
And as both an FTN developer and Sysop of a busy Hub system I have
suggested to James to ignore such asinine requests.
"When bots go wild" has never been a prevalent problem, its the sole
problem
of one incompetent Sysop. It is not the responsibility of an author to
sit
at the console writing all sorts of code, wasting all sorts of
man-hours to
fix the incompetence of one Sysop.
How do I handle it here? I don't. I let the mail flow, use the "Next"
key
to skip crap I don't want to read and let others flame that
incompetent Sysop.
It might not happen very often, and the problem might be caused by one incompetent Sysop, but it's everyones problem, at least everyone who got ~8000 of the same message in their base.
It's not a hard thing to keep a file with a rolling log of message content hashes along with a time received, and acting accordingly.
Ok, so press next 8000 times. I don't think anyone is flaming that
"When bots go wild" has never been a prevalent problem, its the soleOr if the activity is wrecking mail flow and other systems, then the hub
problem
of one incompetent Sysop. It is not the responsibility of an author to
Or if the activity is wrecking mail flow and other systems, then the hub would likely need to silence that node until their system calms down.
Then Avon should be the one to pull the plug on that system if in fact
its
causing problems for everyone. You are not allowed to have a feed
until you
confirm you fixed your broken system. Harsh? Maybe... but an effective "fix".
I'm the author of a major mailer/tosser and had added this
functionality in
my product recently. It wasn't because of this incident but due to the stubbornness of some insisting on running software that strips Seen-By lines.
I wouldn't press Next 8000 times. I would just tell my BBS to mark the lastread pointer ahead 8000 messages. Its not a problem for me, is my
point.
But I'm not a fan of adding this level of checking for a few reasons
which
could morph into a whole other uninteresting topic altogether.
Every couple of years we seem to have someone rescan/dump old messages everywhere... often with new MSGID's, different header CRC, dates, you
name it... I'm actually used to it now.
Yes, but what if Avon is away?
Why didn't you just cut the feeds of Seen-By stripping nodes?
I certainly don't think it's an asinine suggestion.
I certainly do and I'm almost certain G00R00 feels the same, only he
may be
a bit more "nicer" than I am. Whats the saying... clean up your own
backyard
before commenting on your neighbours.
And as both an FTN developer and Sysop of a busy Hub system I have suggested to James to ignore such asinine requests.
On 09 Nov 21 08:58:18, Apam said the following to Atreyu:
It might not happen very often, and the problem might be caused by one incompetent Sysop, but it's everyones problem, at least everyone who go ~8000 of the same message in their base.
Then Avon should be the one to pull the plug on that system if in fact
its causing problems for everyone. You are not allowed to have a feed until you confirm you fixed your broken system. Harsh? Maybe... but an effective "fix".
On 09 Nov 21 13:05:14, Apam said the following to Atreyu:
Yes, but what if Avon is away?
Easy... its a silly hobby, not an enterprise-grade commercial network.
The sun rises and sets no matter if he's busy listening to whatever Abba is limping to the barn with or obsessing about dinner with Gillian Anderson.
Its a tad hard to cut the feeds of Seen-by stripping nodes when they are in-between the Paths of systems that have peered/meshed with others.
Even if that system got its feed from here, what good is a feed cut
when he's peered with 2 or 3 other systems? And one of them runs that crap Fastecho tosser where the Seen-by stripping is hardcoded?
I certainly don't think it's an asinine suggestion.
I certainly do and I'm almost certain G00R00 feels the same, only he may be a bit more "nicer" than I am. Whats the saying... clean up your own backyard before commenting on your neighbours.
prevent this amongst the Sysops participating. Whats a Sysop with a Bot doing posting in FSX in the first place? Was it deliberate or an
If you don't want 8000 identical messages, then Avon as a ZC should personally make sure as many precautions are in place in his network to prevent this amongst the Sysops participating. Whats a Sysop with a Bot
No peering/meshing, nobody stripping Seen-bys, no buggy tossers, no
buggy Bot programs, no circular paths, no rescans/dumps... do all this
and you would have a very clean running network with guaranteed "zero" problems with dupes.
I certainly don't think it's an asinine suggestion.
Respectfully, I disagree. If something can be added in programmatic terms to negate this kind of thing I can't see why it shouldn't be explored.
Your request is largely unworkable, impractical and at the very least would introduce a whole new level of complexity all because of the
actions of one system. A system whose actions you dealt with now, so its not worth exploring.
Avon wrote to Atreyu <=-
Is this some lyrics from a bathroom hit you wrote? ..and how did you
find out about my dinner with Gillian?
And as both an FTN developer and Sysop of a busy Hub system I have[snip]
suggested to James to ignore such asinine requests.
How do I handle it here? I don't. I let the mail flow, use the "Next"
key to skip crap I don't want to read and let others flame that
incompetent Sysop.
I'm the author of a major mailer/tosser and had added this
functionality in my product recently.
If you're ok with flaming sysops you see as "incompetent", are you ok
with flaming sysops who have a shitty attitude? I'm going to guess you're not the sort of person who does well when your own attitude is reflected back at you.
| Sysop: | altere |
|---|---|
| Location: | Houston, TX |
| Users: | 66 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 00:33:50 |
| Calls: | 643 |
| Files: | 7,638 |
| Messages: | 293,299 |