Mamnuts 1.8.3

WARNING:

A SECURITY BUG was found in Amnuts and Mamnuts. That bug exists in EVERY version of Amnuts and Mamnuts (before 1.8.3). So, if you don't want your talker compromised and the account where it is running, upgrade to Mamnuts 1.8.3.

New developer

Pix was now added as a Mamnuts developer. Thanks for your help!

Mamnuts on BerliOS

I've registred Mamnuts in BerliOS. The center of development is still this blog, but I registred the project there because from now one releases will be made there...

Mamnuts 1.8.2

As you can see in the latteral bar, Mamnuts 1.8.2 is out. This version only adds the .sto command, so if you don't want it you can ignore this release and not upgrade. Notice that I have now the tarballs in two different places (one of them as a mirror) so it gets harder to have downtime problems...

Mamnuts v1.8.1 released

Mamnuts v1.8.1 has been released today. This release fixes lot's of bugs and almost implements .visual. That implementation is just commented, because the actual code has some incorrectnesses that make have interoperability issues: it will work well (I suppose) in Linux, but I can't promiss nothing, specialy in other Operating Systems. So, I just decided to have it there in comments (that you can easily take off if you want to try it), and leave the cleanup of that code for a further version.

As allways, upgrade is recommended, since there are those bugfixes there.

The project is gaining a bigger dimension than the one I was expecting, and we actualy have contributions: NomadWolf contributed in the past and now Pix contributed (with the visual code). Keeping track of TODO stuff is also starting to get a mess, so I'm planing to have a proper project development website, instead of just a blog. File storage is one of the things needed: if you notice, this version isn't hosted where the other are, because the former server has availability problems. Problem is, this one also have them. So, what I really need is a proper project management system to keep Mamnuts development. In time, I'll be back to that...