I downloaded this last night but haven't had much time to test it yet.
First thought or comment though. The client defaults to a single public node. If that node goes down for whatever reason, the application won't function. If 1000s of people pick this up and start using it, that node could become over loaded. (I don't know anything about the default node.) I know people can change the node to their own but is the targeted user group going to know what server to use?
A few options I'd recommend:
- add a list of several nodes where a node is randomly selected when the application starts to balance the load on public servers
- gives the application the ability automatically switch to another node if one stops responding
- list the servers in a drop down menu so the average user can select a different server
- keep the ability to add private servers to the list, but possibly add the ability to remove or ignore the default public servers for the paranoid
I don't think you want your application to stop if the owner of the default node decides to shut down the node for whatever reason (updates, etc.).
I'll spend some time and actually test the functionality tonight.