I think TuxReminder is one of my favorite bots thus far. Its a great way to just notify people right then and there once they return to the channel.
Unfortunately, the receiver is not in control of that function though.
When a user enters the channel, it seems that that is the trigger for the bot to burp up all the waiting messages. Or if the users simply says something.
It it not unusual for there to be several.
Splat! right in the middle of somebody's conversation.
It would be different if we could ask the user - in the is case, the receiver - to please not do that... to wait 'till a more appropriate time. But, as it is, the receiver cannot be blamed for it.
Memoserv is fine... but, not so much for people who dont register their nicknames
True.
and only check on every so often...
??
but, Memoserv is complex
Complex? ??
Actually, it is very easy to use. And reliable. And secure.
Like anything, once one becomes familiar with it, it becomes second nature that doesn't require much thought.
Personally, I use some scripts that I worked up, quite some time ago. It was a fun little project.
I've shared them with several people that also use mIRC. Makes the whole process point-n-click simple.
I assume that those that use other good client programs offer their own scripting language, and something similar could be done with them, too.
and really only good for somewhat sensitive confidential things.
huh? Why would it be good for only that??
Besides, using Memoserv reduces the clutter in the channel. Almost all the messages handled by TuxReminder are one-to-one messages. They are not contributing to a chat conversation, nor the subject of one.
So why is a chat channel being used for them in the first place? See what I mean?
I do see how the capability of something besides Memoserv can be a fun thing though. It should just be done without channel clutter... especially since Tux has said that it CAN be done that way.