<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' version='2.0'><channel><atom:id>http://www.blogger.com/feeds/9112657/posts/summary</atom:id><lastBuildDate>Sat, 03 Feb 2007 16:58:31 +0000</lastBuildDate><title>Developer's Daily Diary</title><description></description><link>http://hydranode.com/blog/</link><managingEditor>Alo Sarv</managingEditor><generator>Blogger</generator><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>15</openSearch:itemsPerPage><item><guid isPermaLink='false'>http://www.blogger.com/feeds/9112657/posts/summary/115797061970675350</guid><pubDate>Mon, 11 Sep 2006 10:19:00 +0000</pubDate><atom:updated>2006-09-11T13:30:19.753+03:00</atom:updated><title>When is a software project "finished" ?</title><atom:summary type='text'>anonymous commented: After that much work done, I cannot believe this will stop here. If the project is not finished, Madcat, was a waste of time. 

Define finished please. I have created generic cross-platform P2P client framework/API, and two proof-of-concept modules; I have created graphical user interface, an extendable IPC mechanism and much more.

Hydranode was meant to attract a lot of </atom:summary><link>http://hydranode.com/blog/2006/09/when-is-software-project-finished.html</link><author>Alo Sarv</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/9112657/posts/summary/115617977760751090</guid><pubDate>Mon, 21 Aug 2006 16:51:00 +0000</pubDate><atom:updated>2006-08-21T20:02:57.640+03:00</atom:updated><title>Status update</title><atom:summary type='text'>I was putting together my CV the other day, and noticed an interesting pattern. Over the last 4-5 years, I have done database programming for companies for 2-3 month periods, and then 6-12-month periods of OSS/P2P development; and after that again couple months of database development.

This pattern comes from obvious reasons - OSS/P2P development doesn't pay bills, so after a while the finacies </atom:summary><link>http://hydranode.com/blog/2006/08/status-update.html</link><author>Alo Sarv</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/9112657/posts/summary/115330197205835449</guid><pubDate>Wed, 19 Jul 2006 09:25:00 +0000</pubDate><atom:updated>2006-07-19T12:39:32.106+03:00</atom:updated><title>Busy busy busy busy</title><atom:summary type='text'>It's been quite a while since the last blog post, so I figured it's time to update the status of things and ensure that I'm still around and kicking.

What's going on currently is that I'm heavily overbooked with projects; the database project I took a while ago had some delays getting started (actual development started on 15th this month), and I'm also trying to get the entire project (</atom:summary><link>http://hydranode.com/blog/2006/07/busy-busy-busy-busy.html</link><author>Alo Sarv</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/9112657/posts/summary/115212424277989732</guid><pubDate>Wed, 05 Jul 2006 18:25:00 +0000</pubDate><atom:updated>2006-07-05T21:30:42.816+03:00</atom:updated><title>MLDonkey Import Module (experimental preview)</title><atom:summary type='text'>As the bounty payment for this module was completed yesterday, today development started on the module. Today also the first version of the module was checked into SVN, containing about 350 lines of code; it is capable of importing ed2k downloads from MLDonkey to Hydranode; no files rehashing is needed (this is different from current eMule import support, which forces files to be rehashed).

It </atom:summary><link>http://hydranode.com/blog/2006/07/mldonkey-import-module-experimental.html</link><author>Alo Sarv</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/9112657/posts/summary/115203286151325307</guid><pubDate>Tue, 04 Jul 2006 17:03:00 +0000</pubDate><atom:updated>2006-07-04T20:07:43.026+03:00</atom:updated><title>Hydranode User Experience</title><atom:summary type='text'>A few weeks ago I wrote up a public memo to Hydranode developers (both current and future) about Hydranode User Experience. Since the document got very positive feedback from people of very different backgrounds, I decided to make it available publically. It's a short read, about 8 A4 pages, so grab a cup of tea (or coffee) and enjoy. Comments welcome, as always.

Hydranode User Experience (MS </atom:summary><link>http://hydranode.com/blog/2006/07/hydranode-user-experience.html</link><author>Alo Sarv</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/9112657/posts/summary/115158076831190023</guid><pubDate>Thu, 29 Jun 2006 11:15:00 +0000</pubDate><atom:updated>2006-06-29T14:42:46.660+03:00</atom:updated><title>Bounty-based development model...</title><atom:summary type='text'>...a viable solution for funding open source development?
As I mentioned about a week ago, I'm taking on a medium-sized database project for development to generate some income; this naturally drops Hydranode development to near the bottom of my activity listings; however, this gave me an idea.

There has been discussions about "donate-based bounties" since last summer already, and the topic has </atom:summary><link>http://hydranode.com/blog/2006/06/bounty-based-development-model.html</link><author>Alo Sarv</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/9112657/posts/summary/115109585396643845</guid><pubDate>Fri, 23 Jun 2006 20:40:00 +0000</pubDate><atom:updated>2006-06-23T23:50:54.006+03:00</atom:updated><title>Experimental installer</title><atom:summary type='text'>First of all, I finally got internet at home again, so I'm online 24/7 again, which means development can resume properly now.

One thing that got done during past few days was an experimental installer. After a lengthy search for the 'best installer system', I finally settled on NSIS (Nullsoft installer system) for the time being. An experimental installer is available for previewing/testing </atom:summary><link>http://hydranode.com/blog/2006/06/experimental-installer.html</link><author>Alo Sarv</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/9112657/posts/summary/115058004589624407</guid><pubDate>Sat, 17 Jun 2006 21:22:00 +0000</pubDate><atom:updated>2006-06-18T14:35:55.596+03:00</atom:updated><title>Discussions about Hydranode Web Interface</title><atom:summary type='text'>There has been some very interesting discussion with gcostanza in our forums regarding Hydranode Web Interface. From the looks of it, we'll develop a cutting-edge web interface based on cutting-edge technologies - JSON-RPC-based protocol over HTTP, Dojo Toolkit for the actual interface and eventually COMET for real-time updates. Estimated time of completition - autumn/winter 2006. Current status </atom:summary><link>http://hydranode.com/blog/2006/06/discussions-about-hydranode-web.html</link><author>Alo Sarv</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/9112657/posts/summary/115009976510822326</guid><pubDate>Mon, 12 Jun 2006 08:00:00 +0000</pubDate><atom:updated>2006-06-12T11:09:25.156+03:00</atom:updated><title>Drafting new website; fighting with dev-system</title><atom:summary type='text'>I checked in the tray-icon code to SVN repository yesterday; tested on Windows and Linux (Ubuntu/Gnome) and seems to be working well. Currently only the 'icon' with a minimal menu is implemented, for testing purposes. It "seems" to be working on Windows as well, but there seems to be something heavily wrong with my Windows development setup currently - as I mentioned before, Mingw GUI builds are </atom:summary><link>http://hydranode.com/blog/2006/06/drafting-new-website-fighting-with-dev.html</link><author>Alo Sarv</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/9112657/posts/summary/114985426128943359</guid><pubDate>Fri, 09 Jun 2006 11:48:00 +0000</pubDate><atom:updated>2006-06-09T14:57:41.380+03:00</atom:updated><title>Working on installer and tray icon</title><atom:summary type='text'>I've been further experimenting with different ad placements on the website and different configurations. I'm trying to determine the best non-intrusive locations and styles for the ads, so when we start building the new website (expected second half of this month), I have a knowledge base on the subject to work with.

Another thing that was done over the past few days was finally enabling PayPal</atom:summary><link>http://hydranode.com/blog/2006/06/working-on-installer-and-tray-icon.html</link><author>Alo Sarv</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/9112657/posts/summary/114961623462870624</guid><pubDate>Tue, 06 Jun 2006 17:46:00 +0000</pubDate><atom:updated>2006-06-06T20:50:34.660+03:00</atom:updated><title>Getting started with coding again</title><atom:summary type='text'>After such a long break, it takes a while to get into proper development-routine again. As I don't have internet at my new place yet, I'm using net-cafe, which further hinders development somewhat (the tendency to drink too much beer, that is :P).

Anyway, I made a small update yesterday which allows reloading / updating ipfilter during runtime (via hnsh, "config set IPFilter newpath" only </atom:summary><link>http://hydranode.com/blog/2006/06/getting-started-with-coding-again.html</link><author>Alo Sarv</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/9112657/posts/summary/114936733714618282</guid><pubDate>Sat, 03 Jun 2006 20:29:00 +0000</pubDate><atom:updated>2006-06-03T23:42:21.356+03:00</atom:updated><title>Back from vacation</title><atom:summary type='text'>As scheduled, I'm returning from my scheduled vacation today and resuming Hydranode project development. However, since I moved to a new location during this vacation, there are some technical difficulties getting a broadband connection to my new place, which should take 1-2 weeks at most, so I'm somewhat limited in what I can do currently. There's an internet cafe near my new place, so using </atom:summary><link>http://hydranode.com/blog/2006/06/back-from-vacation.html</link><author>Alo Sarv</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/9112657/posts/summary/114675921739110572</guid><pubDate>Thu, 04 May 2006 16:07:00 +0000</pubDate><atom:updated>2006-05-04T19:13:37.423+03:00</atom:updated><title>Vacation until June 4th</title><atom:summary type='text'>As per the 10-month schedule announced earlier, I'll be leaving for my summer vacation today. The vacation is one month long, during which I will be either completely, or almost completely, offline and unavailable except via e-mail.

The development directions following the vacation, as they are planned currently, include integration of user feedback into the user interface and improvements for </atom:summary><link>http://hydranode.com/blog/2006/05/vacation-until-june-4th.html</link><author>Alo Sarv</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/9112657/posts/summary/114653340078911183</guid><pubDate>Tue, 02 May 2006 01:20:00 +0000</pubDate><atom:updated>2006-05-02T04:30:49.096+03:00</atom:updated><title>Hydranode v0.3 Hotfix (r2998)</title><atom:summary type='text'>Due to several outstanding issues in the original v0.3 release, I decided to release a small hotfix right away instead of waiting for next scheduled release. This hotfix doesn't bump version number, so it's still called v0.3, but instead revision number was added to the download archives. The original release was built from r2995, hotfix from r2998.

Changes:Fixes torrents auto-categorization in </atom:summary><link>http://hydranode.com/blog/2006/05/hydranode-v03-hotfix-r2998.html</link><author>Alo Sarv</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/9112657/posts/summary/114624988447271364</guid><pubDate>Fri, 28 Apr 2006 18:20:00 +0000</pubDate><atom:updated>2006-05-02T04:03:09.386+03:00</atom:updated><title>Hydranode 0.3 released</title><atom:summary type='text'>

Three months have passed since the last release, and time has come again for a release. When the previous release's focus was on Bittorrent support, this time the focus was on Graphical User Interface. As such, engine updates have been minimal, but still include several important fixes, mostly on the Windows platform.

Important engine updates include support for more than 64 open connections </atom:summary><link>http://hydranode.com/blog/2006/04/hydranode-03-released.html</link><author>Alo Sarv</author></item></channel></rss>