Jean Luc Picard of the USS Enterprise....
I had to do it...it was just too tempting
Edit: USS Nxterprise boldly go where no Crypto has gone before.
In a hindsight, I have really picked up an appropriate pseudonym. I never imagined I will make the progress from a forum Newbie to a Captain that fast.
I hereby appoint CfB as my First Officer.
Now that the
USS NRS Enterprise has been making successful test flights, we have to get ready for our first trip outside the solar system, scheduled for Jan 03.
I am now proof-reading the code for any visible bugs. The memory leak has been fixed and I hope version 0.4.8 should have lower memory consumption and not require periodic restart. Next, there are some minor thread safety bugs I noticed that I will fix. I can also think of some optimization in the peer networking code, right now we create a lot of temporary byte[] and char[] that put extra load on the garbage collector and increase the memory usage too, but this is not urgent.
I need to do some refactoring of the code, because now everything is in one huge file. The parts that are to remain closed source will have to be factored out, as much as possible, in separate classes, so that they can be distributed in compiled form, still allowing one to work on the base open source part without having the complete source.
I also need to pick up a repository where we should host the source code, and prepare it for the Jan 03 launch. Probably github, but I need to investigate the alternatives.
A man with a plan. I like it
Thanks to offer your services and congrats to make the team Jean-Luc. Very pleased that some bugs are already resolved. Thanks for that too.
I encourage and support completely all efforts to focus on making existing functionalities super robust, before new ones are added. We go for broad adoption, right?
Problems and difficulties myself and so many others experienced, and reported here on the forum, could scare new Nxt'ers away easily. All efforts to try to avoid that, are well spent IMO. And being target of attacks is not the only potential difficulty we and newbies will experience I suppose.
I would also encourage to improve and simplify the 'how to get started' procedures for newbies: Installation, configuration (editing an xml file? we don't expect every Nxt'er to be an IT'er as well, right?), creating startup files depending of platform (Win, linux, iOS, ...), starting the server (On windows it should be a background service with an automatic start @boot time instead of a manual started cmd window IMO), how to choose a safe enough private key (passphrase), generating a public key (account nb), asking, earning, getting or buying some nxt's on whatever exchange (a separate procedure in itself) and then use the Nxt blockchain explorer (great tool nexern) to check your (or another's) account and transactions. It makes no sense to explain to people how they can make a payment, if they don't have at least some Nxt on their own account, does it?
Although I'm an IT'er and have experience with multiple languages, java and others, I don't consider myself a java specialist and certainly not a cryptographer. But I'm still willing to help somewhere, although I'm not sure with what or how. I would consider to help based on suggestions?
P.S. This morning I had +20.000 orphaned blocks and a script error message in the client running on Win7/Firefox: "Script:
https://localhost:7875/orpanedBlocks.html"
Stopped the server, overwritten both .nxt files with the (old) ones from the 0.4.7e download, updated the WellKnown list with the latest posted here and restarted the server. When I reopened the client, I got another script error: "Script:
https://localhost:7875/recentBlocks.html:200". Pushed F5 and since then all is ok (for now).
I suggest an attempt should be made to improve the self-recovering capability of the network. I don't know the technical details to make specific recommendations though. I hope somebody else has an idea (and shares it
)
Sorry for the long story
, but keep up the good work