I'm going to be having a brief break from school shortly, I intend to add some privacy features thanks to a good suggestion in the forums, and then I'll make a realease. Hopefully I'll be able to get OSCAR to work reliably, and put that in there too. If I get both things working well, I'm going to upgrade the project status to Beta, as it seems to work :)
I've got some untested/expiremental support for using oscar rather than toc.
It's in the current cvs, run ./oscar.p instead of shear.p, works the same, mostly
I haven't tested it very much yet, it seems to work, but there are a few problems i know of, as well as probably some i don't.
Known issues: doesn't set info, has lots of log entries it shouldn't, etc.
When I get everything sorted out, I will make a release.
I just recently found out about a perl module that uses oscar rather than toc for the connection to aim.
There are some features with that module that promise to make the bot better, such as indicators of how many more messages can be sent in how much time, which (combined with programming adjustments) will make the bot much more responsive.
If you want shear to use something other than icq/aim and there is a perl module for it, let me know, and i'll figure something out :)... read more
linux x86 isn't the only platform that can run shear. In fact, Mike has it running on his imac running OS X, here are some tips he has for getting it to work: http://people.msoe.edu/~creuzerm/index.php3/Shear.htm
This release is reasonably stable. The database interface has been cleaned up, so it doesn't kill the box if the databsae goes down. And some makeshift fixes to memory leaks have been implemented.
Well, I decided to tar up everything and make a release. Please take a look and give me some feedback
toast