2016

It looks like the Eggdrop community is getting an early (or perhaps very, very late) Christmas present- we are proud to announce the stable release of Eggdrop 1.8.0! This effort has taken years of hard work, and over 15,000 commits adding more than 50,000 lines of code; we can't express how much we appreciate your patience with us as we worked to shape this into a stable and functional product.

Among literally hundreds of smaller fixes, the biggest changes are SSL and IPv6 support. These additions mean extra config file settings to use them, so while your old config file will still work, you may want to consider using the new eggdrop.conf included with this release.

Speaking of the config file, we've also brought back an old feature- eggdrop-basic.conf. This file is a simplified version of the standard eggdrop.conf targeted towards new users to make the first run a little less daunting. While this file is good for a quick start, we still strongly recommend you use the full eggdrop.conf to take advantage of all the features of Eggdrop.

If you were worried, fear not- TCL scripts written for v1.6 should still function with the v1.8 series of Eggdrop. While the core functionality of most 3rd party modules should still work, many are hard-coded to only run on a v1.6 Eggdrop. We have assembled a variety of popular third-party modules at ftp://ftp.eggheads.org/pub/eggdrop/modules/1.8/ and edited them to remove this restriction, thus allowing them to function with v1.8.

For a list of major changes and advice on upgrading from 1.6.x, check out the NEWS-1.8.0 file included within the Eggdrop source.

Once again, we can't express how happy we are to have reached this milestone, and look forward to 1.8.1 in the (hopefully) not-too-distant future!

It took a little longer than expected, but we are proud to announce the release of Eggdrop 1.8.0 RC2!

Thanks to all who contributed the numerous bug reports and assisted in testing!

All in all, 26 issues were submitted (and fixed!) in response to RC1:

The majority of changes were focused on compilation fixes for cygwin, *BSD, and other general cross-compiling issues. Eggdrop should now compile out-of-the-box under cygwin; the instructions have been added to the INSTALL file.

Unfortunately, we had to remove the little known "flood-size" feature for 1.8.0 but we hope to reintroduce it in 1.8.1 with a slightly better implementation approach.

Finally, our new eggdrop-basic.conf for Eggdrop 1.8.0 is now properly installed along with the complete eggdrop.conf during a 'make install'.

Thanks to your support, we're expecting RC2 will be the final RC for 1.8.0. Barring any surprises, look for the next (hopefully stable) release sometime in the next two weeks.

Until then, RC2 can be downloaded via the official Eggheads FTP at or Github. See you then!

It has been far too long, but the long awaited first release candidate (RC) of Eggdrop version 1.8.0 is finally here!
Among literally hundreds of smaller fixes, the biggest changes were including SSL and IPv6 support. These additions mean extra config file settings to use them, so while your old config file will still work, you may want to consider using the new eggdrop.conf included with this release.

Speaking of the config file, we've also brought back an old feature - eggdrop-basic.conf. This file is a simplified version of the standard eggdrop.conf targeted towards new users to make the first run a little less daunting. While this file is good for a quick start, we still strongly recommend you use the full eggdrop.conf to take advantage of all the features of Eggdrop.

If you were worried, fear not - Tcl-scripts written for v1.6 should still function with the v1.8 series of Eggdrop. While the core functionality of most 3rd party modules should still work, many are hard-coded to only run on a v1.6 Eggdrop. We have assembled a variety of popular third-party modules at ftp://ftp.eggheads.org/pub/eggdrop/modules/1.8/ and edited them to remove this restriction, thus allowing them to function with v1.8.

We know you want SSL and IPv6. But you have to stop using bad patches, like Rootie's. They cause problems, like crashing for no good reason on DCC chat. Read through the heated discussions at forum.egghelp.org if you want more details.

People who report bugs on their eggdrops after applying any third-party SSL or IPv6 patches will be laughed at, and then told to use the development version of eggdrop, 1.8.0, from http://www.eggheads.org/devel/, which support both SSL and IPv6 natively.

You'll have to modify your existing .conf files by pasting the SSL and IPv6 options from the new default eggdrop.conf, and using 'vhost4' and 'vhost6' instead of 'my-ip', but that's far easier than trying to apply buggy patches.

Also, the more people that help us test it, the sooner it will be released as an official version! You want that to happen, right?

2010

We here at Eggheads are happy to announce the release of Eggdrop 1.6.20, the first official release of the new team. Hopefully with the experience I gained with RC1 and RC2, I'll get this one done properly!

Added support to MSGM, PUBM, NOTC, and WALL binds to support bound procs
returning 1 to prevent logging of the trigger message text.

Added the 'exclusive-binds' setting. If this is set to 0, MSGM and MSG
binds, PUB and PUBM binds, etc. are both triggered when a matching event
occurrs.

See the UPDATES1.6 file in the doc directory for more information on
things that have changed since Eggdrop 1.6.17. If all goes well, in a
couple of weeks -- the official version of 1.6.18 will be out. If not, you
might see another release candidate :)

Before I end this e-mail I'd like to personally thank everyone who is
involved in making Eggdrop what it is. The developers who are never
properly thanked for their work ... and the helpers in support channels ..
all you do an amazing job. You are all very talented and it has been a
pleasure to work with each and every one of you. Even as the development
of Eggdrop slows -- I hope you all continue to have great success in your
lives.

Due to a bug in versions of Eggdrop prior to this one, these
versions see the +l user flag and the +l bot flag as
one-and-the-same. On botnets with userfile sharing, this can
cause old bots to incorrectly think that every halfop'd bot
is a leaf. If you experiance problems, upgrade your bots to
1.6.17, as this is a bug in 1.6.16 and earlier.

Added support for Quakenet channel modes.

Added a set of Finnish language files and a Finnish MOTD.

Fixed Tcl encoding issues with .tcl and .set.

Detect Tcl in $HOME/lib and $HOME/tcl/lib first, as to make it
easier to allow users to override the system's Tcl version.

Bot idx's are now considered valid to the "valididx" Tcl command.

See the UPDATES1.6 file in the doc directory for more information on
things that have changed since Eggdrop 1.6.16.

As some of you may know, this is my last 1.6 release. We have renamed
the former Eggdrop 1.7 development tree to Eggdrop 1.9, which will
become 2.0.0 ( http://www.eggheads.org/news/2004/06/20/30). We will
be starting a new development tree, known as 1.7. This is where things
such as IPv6, SSL, and dynamic channel mode support can be added. It
will allow Eggdrop to grow and develop a bit while we're waiting for
2.0, and at the same time, allow us to keep 1.6 stable. I will be
maintaining the 1.7 tree, and Paladin (#eggdrop@Undernet) will become
the new maintainer for 1.6.

We have renamed Eggdrop 1.7 to 1.9 -- this is because when 1.9 is ready
it will be released as Eggdrop 2.0.0 because of the significant changes.
It might be a bit confusing when 2.0.0 is released because the previous
development had a project called Eggdrop2 which did not turn out so
well. We are making every effort to not follow in their footsteps and to
build a program that we are proud of and that you can be proud of too.

Eggdrop1.9 would not be anywhere near where it is without the
outstanding development work of stdarg (#eggdrop@Undernet). We are
designing Eggdrop1.9 with flexibility in mind -- this is most notable in
the ability for multiple scripting languages to co-exist (Perl, Tcl,
Javascript, etc ...). Modules are being reworked so that they actually
make sense and are no longer the ugly hack that they are in Eggdrop 1.6.

Feel free to check it out and explore -- however, at this point in time
it is not ready for anything other than development. Unless you have a
handle on program development and are comfortable using the auto* tools
-- you should not use this tree.

We are looking for people to help get Eggdrop 1.9 to completion. If you
want to get involved -- please contact eggdev@eggheads.org. There is a
lot of work yet to be done. You still have time to put into place ideas
you have that would make Eggdrop a better product. The motto we've had
for too many years of "well, this is how it has been done in the past"
is gone. We all know Eggdrop has a lot of bloated and uncomfortable code
-- this is the time to for you to trim it.

We are always looking for people to help us. Coding is just one of the
many ways that help can be delivered.

Don't like the way the botnet is? Redesign it.

Don't like the way userfile sharing works? Fix it.

Don't like the way Eggdrop looks at you in the morning? Go see a head
Doctor.

A few people have had some issues compiling Eggdrop 1.6.16 with Tcl 8.0.
If you get an error compiling Eggdrop, similar to this:

...
botmsg.c: In function `tandout_but':
botmsg.c:50: `va_list' undeclared (first use in this function)
botmsg.c:50: (Each undeclared identifier is reported only once
botmsg.c:50: for each function it appears in.)
botmsg.c:50: parse error before "va"
...

There is a simple fix. Simply add the following line to "config.h" in
the eggdrop1.6.16 directory AFTER running ./configure:

#define HAVE_STDARG_H 1

And then continue compiling Eggdrop normally. This should fix the
problem.

We have recently registered eggdrop.ca -- totally by fluke. I was up early before work one morning checking on the progress of securing eggdrop.net when I accidently did a whois on eggdrop.ca and saw it was available. For the time being, eggdrop.ca will just point to Eggheads.org; however, in the future we might actually use it for something. I'm open to suggestions!

IPv6 protocol support has been removed. It was poorly
implemented in 1.6.15, and it will be done correctly in a
later release.

You can still connect to an IPv6 server using 6tunnel.

6tunnel -s VHOST LOCALPORT IRCSERVER PORT

Then, in your config file, make the bot connect to localhost
on the specified port.

Many, many bugfixes.

The eggdrop binary is no longer stripped during the compile
process. This will make bug reports more useful to the
development team, and ultimately will help for a more stable
bot. You can still use ./configure --enable-strip to enable
stripping, which will create a smaller binary.

Several more functions have been exported for use by module
coders.

Support for non-x86 platforms and uncommon improved.
doc/COMPILING-FAQ has been updated, and now contains a compile
guide, which will be updated in versions to come as Eggdrop is
tested on more platforms.

Support for +E/+I modes on EFnet has been added.

The hand2idx Tcl command works for bots now.

Added a new Tcl EVNT bind type, "userfile-loaded", which is
called after the bot's userfile has been loaded.

All users can now .whois their own handle.

Better support for Mac OS X. This is still not perfect. If you
have a Mac OS X box and experience any problems, please let us
know.

Better support for non-standard "op" prefixes There is now a
config file option named "opchars", which will allow you to
configure what prefixes the bot will consider an op.

The default is: set opchars "@"

This will make Eggdrop recognize users with the "@" prefix in
a WHO reply as an op. If you set this to "@&~", users with the
"@", "&", or "~" prefix will be recognized as an op.

Tcl 8.5 alpha is now correctly detected.

A long-present bug has been fixed in dnslookup, having to do
with the concatenation of its arguments. It now works the way
it has always been documented in tcl-commands.doc. This could
possibly create problems with some scripts.

A security flaw reported to bugtraq recently, related to bot
linking, has been corrected.

Updated Undernet nicklen to 12.

See the UPDATES1.6 file in the doc directory for more information on
things that have changed since Eggdrop 1.6.15.

IPv6 protocol support has been removed. It was poorly implemented in 1.6.15, and it will be done correctly in a later release.

You can still connect to an IPv6 server using 6tunnel.

6tunnel -s VHOST LOCALPORT IRCSERVER PORT

Then, in your config file, make the bot connect to localhost on the
specified port.

Many, many bugfixes.

The eggdrop binary is no longer stripped during the compile process. This will make bug reports more useful to the development team, and ultimately will help for a more stable bot. You can still use ./configure --enable-strip to enable stripping, which will create a smaller binary.

Several more functions have been exported for use by module coders.

Support for non-x86 platforms and uncommon
improved. doc/COMPILING-FAQ has been updated, and now contains a compile
guide, which will be updated in versions to come as Eggdrop is tested on
more platforms.

Support for +E/+I modes on EFnet has been added.

The hand2idx Tcl command works for bots now.

Added a new Tcl EVNT bind type, "userfile-loaded", which is called after
the bot's userfile has been loaded.

All users can now .whois their own handle.

Better support for Mac OS X. This is still not perfect. If you have a
Mac OS X box and experience any problems, please let us know.

Better support for non-standard "op" prefixes
There is now a config file option named "opchars", which will allow you
to configure what prefixes the bot will consider an op.

The default is: set opchars "@"

This will make Eggdrop recognize users with the "@" prefix in a WHO reply
as an op. If you set this to "@&~", users with the "@", "&", or "~" prefix
will be recognized as an op.

Tcl 8.5 alpha is now correctly detected.

A long-present bug has been fixed in dnslookup, having to do with the
concatenation of its arguments. It now works the way it has always been
documented in tcl-commands.doc. This could possibly create problems with
some scripts.

A security flaw reported to bugtraq recently, related to bot linking,
has been corrected.

See the UPDATES1.6 file in the doc directory for more information on things
that have changed since Eggdrop 1.6.15.

We are changing the method used to release Eggdrop, as you have probably
noticed. The way releases will work will be something like this:

Release Candidate 1 will be released.

We will then wait a period from 1 to 2 weeks. If no major bugs are
reported, then rc1 will be released as the final version.

If a major bug is discovered, it will be fixed, and rc2 will be
released. Then the process will repeat.

The ban-time, invite-time, and exempt-time settings are now channel
specific settings which can be set via the .chanset command, instead
of a global setting in the config file.

Fixed a few bugs that have been present since as early as version 1.1.5.

Eggdrop should compile on older versions of SunOS properly now.

Better dynamic library detection on Mac OS 10.

User lookup functions should be much faster now.

Fixed utf-8 handling for config file strings (such as realname).

Loads of other bugfixes.

See the UPDATES1.6 file in the doc directory for more information on things
that have changed since Eggdrop 1.6.12.

I would also like to note that versions of UnrealIRCd earlier than 3.2 beta
11 have a bug which does not show halfop status symbols in who info. If the
bot
does not recognize that certain users have halfops when they really do, this
is
an IRCd problem, not an Eggdrop bug.

Hey folks,
On the heels of innovation from being able to do "wget geteggdrop.com" and get the latest copy of eggdrop -- you can now "wget eggheads.org" and do the same thing. Also, as soon as Ryan can add a DNS entry for me you will also be able to "wget bz2.eggheads.org".

Also, I wanted to show you how busy the little uptime daemon makes the MySQL
server at eggheads.org:

It has been a long time since I kept you up to date with the current happenings. For starters -- I am now part of the working world and this is keeping me rather busy. I'm working as a Network Analyst for a small web hosting company here in Regina, Saskatchewan and that is keeping me extremely busy. Also I'm planning my wedding and basically keeping busy with the real world -- can't stay on the computer forever now can I? :)

On the Eggdrop front ... I have stepped down as the maintainer of the Eggdrop 1.6 series. To fill my shoes Wcc has been appointed my replacement by me. He is doing a wonderful job and is even managing to fix long standing legacy bugs no one even remembers. Eggdrop1.7 is still progressing; however, at a slow pace but that is alright. If anyone wants to help on the development of it please contact me and I'll point you in the right direction.
I'm going to hack on some stuff for the ftp now,
Jeff

I was sitting here with Jen looking at the site and decided to write a little entry praising Mohammad for bringing life to Edward :) He did such an amazing job I can't even begin to describe how great Edward is.

Now if only Edward wasn't so geeky looking since it makes us look geeky! And we aren't, right? <g>

Eggdrop 1.6.11 has been released and comes in two flavours, yet you are only charged the price of one. You can get it in either bz2 or gz format -- amazing huh? Anyways, some of the bigger changes to this release are:

I've added the beginnings of both a Support page and a Development page. I have long been a fan of online support via IRC channels; however, I also like to see people read documentation that comes with a program. After all the best way to learn is by figuring out the problem you are presented with and if you still can't solve it after a few hours .. ask someone.

I am still working on the Search page -- currently working on redoing my FTP spider and figuring out exactly how the frontend will work. Along with the FTP spider will come Eggheads.org user accounts so that people will be able to register file descriptions and such. I don't want to give a date on which I will finish because I will most likely skip that date. Canadians hate deadlines.

Being that I had some spare time today I felt it was time to bring http://uptime.eggheads.org into the mix of things. I redid the code for the site to make it look like the new Eggheads.org site.

Everything should hopefully work on it including the new dying link which will show you a list of bots that are about to fall off the list. People for some reason like seeing all this weird and useless information.

Well the web site bug took a bite out of my ass tonight and got me working on the site again. Most of the site works except for:

the Development area

the Search area

the Support area

I expect these to be finished in 7 to 8 years if not longer .

I also cleaned out the old news database because I have changed the format of the table so I don't need as much crud in it. I am still working on the entire "Members" section of the web site; however, right now my time is very limited because I am looking for a job (hire me? please!). This section will be mainly geared towards Eggdev members at first, but I would like to eventually tie it into some other features for non-Eggdev people. For example:

User comments on news/articles

Descriptions of files found in using the as of yet non-existent FTP search engine

Setting comments on your bot(s) if listed on http://uptime.eggheads.org (this depends on a few other technical issues not related to the website, like the release of eggdrop1.6.11)

Filing bug reports and/or feature enhancements

Other whizbang stuff not yet invented

Either way for now ... I am heading off to have a good 5 1/2 hour sleep and then continue looking for work.