This is just a notice that we stopped licensing the full source code for our products some time ago; from this point on only pieces could be licensed. The website will be updated to explain what kind of components are available, but I can tell you which one is the most interesting -- a very expressive GUI framework for Python and wx. I'm convinced it's the best take on GUI programming I've seen so far and I've seen many of those! If you'd like more info, send your inquiries to licensing@maluke.com

Anyone considering a full source-code license for S3 Backup would probably be best served with our upcoming offer for resellers, but please wait for the actual announcement.

- Sergey

The saying goes "when all is said and done, more is said than done", and if there are exceptions to it, then this is one. There were no new releases of our software for a long time and I've had a rough time this winter and spring which set me back on a number of fronts, however I never gave up on S3 Backup or any other projects of ours and things kept moving.

I'm really in favor of actions doing the talking which is something I obviously take to extremes sometimes -- there were no status updates here for months. That's something I want to change now, so whichever way the development goes I will be keeping you guys up to date. And the good news there's a lot to report: the rough times are over and as I come back to work on the code all-out, I can't help but see that the work put into it so far is of great quality and the decisions I made along the way are generally correct.

The reason why there were no intermediate releases is that last year I had to make a decision: to get on track to where I want to take S3 Backup and my company in general we had to step back and replace some ad-hoc parts with carefully engineered components. That means that the old and the new parts need to interoperate -- that interop takes effort so it's a choice between a) getting the fully updated app out faster or b) having steady release schedule but with slower overall development. I went for the first route which would have worked well if not for the unexpected things life can throw at us. Engineering-wise there were no issues, it's just something completely unrelated that messed up the plans. I reported back in Autumn that I thought the solution would be to go back to plan B, which was something I didn't think through at the time -- it didn't take much time to see that initial development plan was good -- it's the things outside its scope that were the problem.

So here we are -- finishing the new versions of our apps and then some. Hopefully we will gradually be revealing new features and products that will make it more clear what kind of work we were doing and I expect you will appreciate the reasoning behind the re-engineering.

Also I want to thank everyone who has shown support and interest in our work during the past year -- I'm really sorry I quite often was unable to reply in timely manner, but please know that I truly appreciate it and work to justify your trust.

We are here and looking forward to an eventful year ahead of us.

Hi everybody!

There were no updates for a long time, so what's going on? While due to some reasons, which I won't get into, not as much work happened in these months as I would have liked, nothing stood still either. The entire roadmap had to be readjusted, yet the planned feature and product list is the same.

First thing to happen will be a new S3 Backup version, a release candidate this time. Then, as soon as licensing system is ready we'll make a 1.0 release (for S3 Webmaster as well).

Mac and UNIX ports are getting some attention as well, but I can't promise a hasty release because I have to admit they aren't top priority right now. We'll make an announcement with estimated release schedule as soon we could make a commitment to one.

The FTP gateway application engine is ready but lacks the UI component and need some more work to make sure it can handle more than a couple users concurrently.

Also, Word to HTML needed a better UI for a long time, and I plan to get it one this fall.

There's more in the pipeline, but one of the reasons for a prolonged silence is that it's my policy to always favour showing results instead of talking about it. Anyway, I expect there will be a steady stream of announcements from this point on, so watch this space.

See product page for download links.

Improvements

• Filedb uses SQLite
  • Multiple concurrent backups don't interfere with each other
  • Much smaller memory footprint for huge backup sets
  • Even a violent crash / powerdown leaves filedb consistent and up-to-date
  • Old XML-based database is imported automatically
• New backup job configuration UI
• Corrupted / out of date filedb does not require reuploads

Fixes

• Empty directories left behind
• KeyError: duplicate file name
• Multiple minor fixes

Known Issues

• Old corrupted XML databases might prevent the app from starting,
  • If that happens to you just delete %appdata%/S3 Backup/hashdb.xml, the app will repair the db