Eggdrop Release v1.9.2 Release Candidate 2

Happy New Years, Eggheads!

(checks calendar) ... uhh ... and Happy Valentines Day! <3

Thank you to those of you who have been working with Release Candidate 1 for v1.9.2. Two rather-significant bugs we missed in testing were discovered, so EXTRA thanks to ldm and Lord255 for helping us track these down. One dealt with a race condition in the new async DNS system, and the other dealing with an issue with Eggdrop tracking the account-tracking status properly. Both are resolved now (as well as a few other typo and simple fixes), so we're going to put out RC2 and make sure everything is playing nicely together.

As always, we can't do this without you, and we are so thankful for the support we continue to receive after all this time. As always, please report any bugs you find at https://github.com/eggheads/eggdrop/issues . THANK YOU!

Eggdrop Release v1.9.2 Release Candidate 1

Seasons Greetings, Eggheads!

We have a holiday treat for you, the release candidate for version 1.9.2! We continue to tweak, fix, and upgrade the 1.9 release series, and 1.9.2 has lots of goodies in here for you to play with. Some of the big ticket items we want to highlight here:

• Full CAP 302 support
• Asynchronous DNS requests moved to core code
• New Tcl commands (monitor, isircbot, server list) and a new Twitch bind
• New CAP capabilities (monitor, cap-notify, and SASL 3.2)

As this is an RC, there is still time to find a few bugs that may be hiding; we're depending on you to help us find those last few bugs before we declare 1.9.2 as stable. Please use it and report any bugs you find to https://github.com/eggheads/eggdrop/issues . We plan on leaving this comment period open for 2-3 weeks. Thanks again for all you do!

Eggdrop v1.9.1 *STABLE*

We're back again already, just 2 months after our last stable release. We added a lot of new features in 1.9.0, and there were a few usability/stability issues discovered after we released that we wanted to fine-tune just a bit more, and get it out to you as quickly as possible. This release doesn't have much, if anything, in the way of new features, but does fix a few bugs introduced in 1.9.0 that a small population of Eggdrop users may encounter. Specifically:

• Fixed an issue where adding a server without a port could create a condition where Eggdrop would crash on startup
• Fixed a bad merge from 1.9.0 that resulted in away status not being properly tracked by Eggdrop
• Fixed/clarified some of the terrible error messages we've all come to know and love for socket connections
• Fixed a bug in the CTCP module that resulted in an IP in the socket table being incorrectly overwritten, causing trouble with future CTCP chat requests. This was also prevents some Eggdrop's from incorrectly throwing a Tcl error during a rehash
• Fixed an error message that incorrectly appeared after a restart when using the PBKDF2 module
• Added the Libera server to accepted net-types in the config file.

We'd also like to announce that we have joined a large number of other open source projects in moving our official support channel from freenode to Libera Chat (irc.libera.chat). This was a carefully measured decision and while we regret moving from our home on freenode for well over the last decade, we look forward to transitioning all our support, development, and operations to Libera Chat. If you are interested, additional information on this move can be found at https://eggheads.org/news#news69 for additional information on this decision. Please look for us there!

Eggdrop v1.9.1 Release Candidate 1

Howdy, fellow Eggheads!

We're back again already, just 2 months after our last stable release. We added a lot of new features in 1.9.0, and there were a few usability/stability issues discovered after we released that we wanted to fine-tune just a bit more, and get it out to you as quickly as possible. This release doesn't have much, if anything, in the way of new features, but does fix a few bugs introduced in 1.9.0 that a small population of Eggdrop users may encounter. Specifically:

• Fixed an issue where adding a server without a port could create a condition where Eggdrop would crash on startup
• Fixed a bad merge from 1.9.0 that resulted in away status not being properly tracked by Eggdrop
• Fixed/clarified some of the terrible error messages we've all come to know and love for socket connections
• Fixed a bug in the CTCP module that resulted in an IP in the socket table being incorrectly overwritten, causing trouble with future CTCP chat requests. This was also prevents some Eggdrop's from incorrectly throwing a Tcl error during a rehash
• Fixed an error message that incorrectly appeared after a restart when using the PBKDF2 module

As this is an RC, there is still time to find a few bugs that may be hiding; we're depending on you to help us find those last few bugs before we declare 1.9.1 as stable. Please use it and report any bugs you find to https://github.com/eggheads/eggdrop/issues . We plan on leaving this comment period open for 2-3 weeks. Thanks again for the amazing response we've seen with 1.9.0 so far!

Eggdrop v1.9.0 *STABLE*

Greetings Eggheads!

It is done! After just over three years, Eggdrop 1.9.0 is finally here! As this was a major release, it spent a little extra time getting the finishing touches put on, but I think you'll find it well worth the wait with the new features and fixes. As we still managed to find small and mostly up-to-now unnoticed bugs to fix, we also added some SIGNIFICANT changes, to include

• CAP support, with native support for some IRCv3 features
• SASL authentication support
• A new way to add and remove servers, via 'server add' and 'server remove'
• A Twitch module
• Away-status tracking
• PBKDF2 hashing for password storage in the userfile (Make sure you read the docs for this one, or you may break your userfile!)
• A new ident module with oidentd support
• The listen command now takes an optional IP; allowing you to listen on multiple IPs at the same time
• ISUPPORT / RAW 005 parsing is now possible. There is still work to be done in the future to automatically integrate some of these values into how Eggdrop interacts with the server, but for now they are available for you to use via the Tcl interface

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, or at least comparing files to see the new changes.

If you were worried, fear not- special care was taken to make all changes backwards compatible; Tcl scripts written for v1.6 and v1.8 should still function with the v1.9 series of Eggdrop.

We HIGHLY recommend you read NEWS for a full summary of all the changes made; it's not a terrible read, we promise and you may just find something useful tucked away in there.

We also want to make sure we thank our unofficial test force/guinea pigs Lord255, PeGaSuS, and WildCraze- they were instrumental in helping us test new features, identify bugs, and by providing feedback on general approaches. Thank you! (Want to help out? Ask in #eggdrop on Freenode!)

Eggdrop v1.9.0 Release Candidate 3

Greeting Eggheads- we're almost there!

We debated on whether or not to declare stable with this particular release, but we changed a how we handle backwards compatibility of old configs still using the now-removed "listen-addr" setting (which of course, you already knew because you have read doc/Changes1.9 and saw we now handle choosing the listening IP via the listen command, right?). Anyway, because there were so many variations on networking configurations, we decided to release one more RC so we could ensure you got the best Eggdrop possible! (We also fixed a compile error on SunOS, for the three of you out there still running Eggdrop on SunOS)

So once again, just a few more weeks and we'll (knock on wood) be ready for the stable release of 1.9.0. Thanks again for all your support!

Eggdrop v1.9.0 Release Candidate 2

💓 Happy Valentines Day, Eggheads! 💓

Ok, so maybe we're a few hours late, but for those of you in Hawaii, it is definitely still valid ❤️

We REALLY appreciate your feedback on RC1 - we fixed over 20 issues that slipped through the cracks; some big, some small. What a testament to your dedication and enthusiasm for the project, thank you!

We neglected to mention a few additional important changes to Eggdrop in the last release message:

• A new ident module with oidentd support
• The listen command now takes an optional IP; allowing you to listen on multiple IPs at the same time
• ISUPPORT / RAW 005 parsing is now possible. There is still work to be done in the future to automatically integrate some of these values into how Eggdrop interacts with the server, but for now they are available for you to use via the Tcl interface

A significant change from RC1 based on feedback: What was previously the addserver/delserver Tcl command in RC1 (used to, surprisingly, add and delete a server from the server list in lieu of the historical "set server" method) is has been refactored to 'server add' and 'server remove'. This mirrors the 'channel add/remove' syntax and allows us to extend the syntax in the future if needed.

We also want to make sure we thank our unofficial test force/guinea pigs Lord255, PeGaSuS, and WildCraze- they were instrumental in helping us test new features, identify bugs, and by providing feedback on general approaches. Thank you! (Want to help out? Ask in #eggdrop on Freenode!)

As this is an RC, we're depending on you to help us find those last few bugs before we declare 1.9.0 as stable. Please use it and report any bugs you find to https://github.com/eggheads/eggdrop/issues or via the Freenode #eggdrop channel. We plan on leaving this comment period for this RC open for 2-3 weeks. If everything remains calm for the duration, we'll officially release 1.9.0 at that time. Or another time.

We HIGHLY recommend you read NEWS for a full summary of all the changes made; it's not a terrible read, we promise and you may just find something useful tucked away in there.

Eggdrop v1.9.0 Release Candidate 1

Hello fellow Eggheads!

We did it! After just over three years, the first release candidate for Eggdrop 1.9.0 is finally here! As this was a major release, it spent a little extra time getting the finishing touches put on, but I think you'll find it well worth the wait with the new features and fixes. As we still managed to find small and mostly up-to-now unnoticed bugs to fix, we also added some SIGNIFICANT changes, to include:

• CAP support, with native support for some IRCv3 features
• SASL authentication support
• A Twitch module
• Away-status tracking
• PBKDF2 hashing for password storage in the userfile (Make sure you read the docs for this one, or you may break your userfile!)

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, or at least comparing files to see the new changes.

If you were worried, fear not- Tcl scripts written for v1.6 and v1.8 should still function with the v1.9 series of Eggdrop.

As this is an RC, we're depending on you to help us find those last few bugs before we declare 1.9.0 as stable. Please use it and report any bugs you find to https://github.com/eggheads/eggdrop/issues . We plan on leaving this comment period open for 2-3 weeks.

We HIGHLY recommend you read NEWS for a full summary of all the changes made; it's not a terrible read, we promise and you may just find something useful tucked away in there.

Eggdrop v1.8.4

It appears the small fixes made across 3 release candidates have settled in nicely, and all the little eggheads stayed off the naughty list, so we are pleased as punch to announce Eggdrop v1.8.4 has gone STABLE. Hooray!

The major changes in the release include:

• Lots of work on the compile process for less-commonly seen systems (SunOS, DragonFly, etc), and making Eggdrop more compiler-friendly in general
• Added and enhanced SSL/TLS warnings to make troubleshooting easier
• Raised the ban expiration limit from 1 year to 5 years, and added a new %y field to +ban
• Lots of work on TLS bot links
• Improved/clarified botnet TLS documentation- go read it!
• Made TLS fingerprints persistent across a botnet after relinking
• Sterilized a LOT of small, lingering bugs.

Again, thank you to all those who helped us test out the release candidates, and a special thanks to mortmann for joining the development team. Everyone's help was invaluable!

Eggdrop v1.8.4 Release Candidate 3

Thanks to Harekiet for identifying an ssl variable that was not properly #ifdef'd out, causing a compiler error if TLS was not detected/enabled for the compile. Fixed!