After a nice break followed by tons of hard work by all of our developers, the first beta of Shrike has been released.
You can download this file from the sf.net project page at SourceForge.
This release has completed all major aspects of Shrike, including channel and username registration and management. This release is still missing some "little things" that will be implemented before the 1.0 release.... read more
Thanks to VehoWave's design services, the official Shrike Website has been launched.
The site is up and running, but it's far from complete. Expect to see new features and new pages pop up regularly. Hopefully, some documentation will be up soon as well.
Visit the Website at http://shrike.malkier.net/
Please ignore the mailing lists on sf.net, we do not use them.
If you wish to subscribe to the (low traffic) Shrike mailing list, send an email to email@example.com.
The sf.net CVS servers are having severe issues, and as such, we have decided to host Shrike's CVS on a machine owned by one of the developers.
Anonymous CVS for shrike is avaliable with:
cvs -d:pserver:firstname.lastname@example.org:/usr/local/cvsroot login
[empty password, press enter]
cvs -d:pserver:email@example.com:/usr/local/cvsroot checkout shrike
There is also a bzip2 tarball generated each night at midnight, CST. This file can be found: ftp://ftp.malkier.net/pub/shrike/CVS/... read more
The first alpha of Shrike has been released.
You can download this file from the sf.net project page at http://sourceforge.net/project/showfiles.php?group_id=95176&package_id=101389&release_id=208611
This release actively connects to an IRC network and maintains a sync with the
network. This release does not actually contain any useful tools for an IRC
This is not production code.
Work on Shrike is progressing. As I'm writing this the code understands IRC (basically), links, introduces the configured client (via shrike.conf) and joins a configured channel. The code also has an autoconf script, and a setup script.
Within the next few weeks we'll be working mostly on the network syncing code... once the syncing is done, we have all of our data to work with and work should progress quickly.
Due to the needs of my IRC network, Shrike is going to be a services program instead of the originally intended channel management bot.
This is still channel management in a way, though. ;)
The http://shrike.malkier.net/ site is under construction and should be available shortly. The site will feature information, documentation, version information, author information, and more. All, of course, hosted by sf.net.
In related news, planning continues in the many stages of C++ program design. It's become my realization that the design is going to take longer than actually writting the code. I'm not joking, either.
The initial planning phase for the Shrike IRC Bot has begun.
Shrike is the evolution of the Avalon (aircb) bot that I had originally intended to be a port of the Perl dgbot. This time I've decided to go with channel management.
Although planning has begun, I have no idea when I'll actuall start writing the code. I just wanted to get some news on the project page, so here it is.