Topic: NXT :: descendant of Bitcoin - Updated Information - page 2066. (Read 2761645 times)

thanks! thats very interesting. Good to see that NXT is in top5!

I just did i quick calculation based in the USD trade volume  @ coinmarketcap.com

running my toy 10NXT account on your Pi

Seems to work, syncs blocks, doesn't show active peers, how long does it work without having to restart it?

We have to make a determined push for mobile...the android app is already full steam ahead and the iPhone app is starting off.


Messaging/DNS....Alias system can be big.

all the aliases show in the account, good team,so quick.

yes it is a really problem i hope developer can solve it. several my aliases transactions have done and the record is listed in the account. but i cant find any alias in my account. it seems just the transaction not happpened but the fee is gone.

This is a new indicator worth watching, much more significant and indicative of public interest than their default ranking of market cap.  Just wait til NXT is on Cryptsy and all the Doge folk come to play with our shiny new toy...  

Interesting article about the decline of Facebook
http://www.theguardian.com/technology/2013/dec/27/facebook-dead-and-buried-to-teens-research-finds
When the arbitrary message functionality works, I think we have a decent chance to find a niche here with right promotional efforts.
So pay attention development team

add NXT<->LTC too please, if you can )

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.

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.

For those of you that are interested in the exciting RaspPi story:

I've opened my RPi NXT server to the net. Access it by: https://raspnxt.hopto.org:7875

Just in case you wonder how NRS performs on an RPi.

Feel free to try out testing or even "serious" addresses, as both IP and RPi are completely under my control. That is, only if you trust my network, of course.

IMPORTANT ANNOUNCEMENT

Jean-Luc has joined Nxt core dev team. His role will be focused on leading the core development only, nothing more.

I know you've got a million things to look at in the code, please allow me to bring one more to your attention that I have mentioned earlier to CfB.  With the looming and critical importance of the Raspberry Pi to NXT, I suggest for monitoring purposes that a peer in the client list be identified as a Pi and designated by a raspberry-colored "star" (as a variation on the current blue) beside the software version it is running.   Basically, if NXT is running on an Armv6 processor, it's running on a Pi.  See:  http://htpcbuild.com/hardware/standalone-htpc-build/raspberry-pi-htpc/raspberry-pi-codec-license-install/ for details.

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.

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.

You're a rockstar!

CfB, are the aliases case sensitive? The wiki doesn't mention...