ahh, I rember that old time I wanted to make a “your mom bot” for discord, one of the function was saying “No, your mom” when someone said in a phrase “your mom”, little did I know that discord bots read their own messages if you don’t check it
I broke my brother’s exchange beta 4 install by telnetting into SMTP port and sending an email with an accidentally typo’d recipient. The bounce bounced, that bounce bounced and it continued until priv.edb was full and the service crashed. After a morning on the phone with Microsoft support he asked me if I did it. They made a hotfix for the bug.
Screenshot of what’s happening for the uninitiated. Bot keeps posting YouTube links and then replying to itself because it detects a YouTube link.
You’ve fallen for one of the classic blunders! Never let a bot reply to itself!
ahh, I rember that old time I wanted to make a “your mom bot” for discord, one of the function was saying “No, your mom” when someone said in a phrase “your mom”, little did I know that discord bots read their own messages if you don’t check it
Just thinking of this makes me laugh
Reminds me of back when it was possible for two out-of-office message services to get stuck in an endless loop
I killed an old exchange server with an auto reply to a coworker who had an auto reply to me.
Those were the good old days.
I broke my brother’s exchange beta 4 install by telnetting into SMTP port and sending an email with an accidentally typo’d recipient. The bounce bounced, that bounce bounced and it continued until priv.edb was full and the service crashed. After a morning on the phone with Microsoft support he asked me if I did it. They made a hotfix for the bug.
“Stop replying all!! Can you take me off this email thread please?!”
The people who got pissed off were the best. And the whole company would see it. Those were the days.
Someone needs to make a PR to add a check for the username of the commenter that they’re replying to. Should be a simple conditional check.