Topic: NXT :: descendant of Bitcoin - Updated Information - page 1165. (Read 2761626 times)

About one hour before I added it on NXTarea.com to the top. I'm sure this generated many votes for me in the end. I also asked a few friends of mine to vote. But all in all it appears to be very high. Well my site had about 300 views in the last 2 hours, dunno..

I submitted 3 projects as one. You submitted 1 project with 3 ppl. It doesn't matter in the end. And I saw that you will make an IPO with your app.. Be happy that you won money..



Can someone say to me what AM features minusbalancers client has? I can't find it.. And I don't want to install it, I like the webclient.

If we use compression, I recommend it be optional for a client.

This scheme was used by an experimental compiler for the Oberon OS in the '90s for encoding constants in abstract symbol tree based object files called slim-binaries.  They used other techniques too in order to keep object file sizes down, and nearly all of what they did isn't relevant to what we're doing but on average they saw a dramatic decrease in size of their object files compared to other schemes.

This is from the article Slim Binaries by Franz and Kistler in Communications of the ACM v40 i12, Dec. 1997:


Granted, most of that savings was due to an adaptive LZW-style encoding on the elements of an AST so we won't see such savings.  I recommend the variable length encoding of integer constants not for any compression it may provide as that's just an incidental bonus we get for free.  I recommend the encoding for the following reasons:

1.  For portability of representation of constants between architectures.
2.  Low working memory requirements.
3.  Fast to encode and decode.
4.  Simple to implement.
5.  The code for the encoding and decoding of integers is very small -- only a hand-full of bytes.


The scheme is actually pretty simple.  The example code Franz gives for encoding integers doesn't do any explicit bit-twiddling: there purposefully aren't such operations in the Oberon family of languages in order to guarantee portability.  (It's a foreign way of thinking for C-accustomed programmers.)

Lol, nice catch.

Green one is cool.

testing right away.

No, I am just kidding I agree with you in general.

Yes, in some specific cases of small network messages, hand-crafted structure can mean a lot. And if we go with a binary format, embedding a type is not a bad idea.

I just think we're nowhere near (and won't be any time soon) such high loads that would justify switching to a low-level, hand-optimized binary format.

Nxt - 3D graphics: Update #08

Nxt - icon

All 3d renderings are here:
forums.nxtcrypto.org
nextcoin.org

Why 15k to everyone? It S not to fair for the 3(only 5k more) also considering that we decide to split the Work in 3 people to gave a better app, next time i will make something useless to get 15k or maybe i will cheat... Congrats to this fake Contest!

++  for example, see radius/diameter protocol

I've changed up the reference client installer again

It now searches for Java on your machine, and if it doesn't find it, it will download and install either x86 or x64, depending on your system. I also changed the Post Setup Launcher to actively ping http://127.0.0.1:7874/index.html to detect when the Nxt client comes online. It will then re-direct to https://127.0.0.1:7875. I had to use the unsecure port because the SSL Cert error prevents the browser from returning a 200 ok message which is what I use to determine if Nxt has loaded.

As stated before, there is no longer any need to remove an old client version before installing a new one. Simply download the new version and the installer will update it.

The "Folder is in use" error that showed up every now and then at the end of the install has also been fixed.

I'll use this for the next release from Jean-Luc, but I'm not going to go back and update my release of 0.5.11.

Please, PLEASE test this installer and give me your feedback on any errors. I have run it on Windows 7 x86 and x64, and Windows 8 x64 without issue. So far my overhead with things I've had to add to make this work (Jquery, PostSetupLauncher, .bat files, etc.) is about 144KB. The Uninstaller is another 719KB.

Nxt Installer 0.5.11 Web Setup BETA TEST: http://www.mediafire.com/download/uhu6m1u7upmn769/Nxt%200.5.11%20Web%20Setup%20BETA%20TEST.exe
SHA-256: CA99344D1B6D32FFC7A32B40353657CA6B2F22AE1E0B0F02C896DCA29684BF2B

+1 my congrats!

No.  Votes should not be carried out on this platform here.

However congratulations passion_ltc, I for one voted for you.

Nope. A lot of cheating, in last 15 minutes about 100+ votes!!:|

 gvans nxt monolith  -files for production available

                

As requested, I have done some research and processed manufacturing files for nxt monolith.
Instruction pdf and dxf-files for lasercutting are provided. Lasercutting is the easy and preferred method as it results polished edges for acrylic.
Also iges and stl files for 3d-print and cnc are available.

instructions pdf: https://www.dropbox.com/s/qeydnudw0z37f7o/gvans%20nxt%20monolith%20instructions.pdf

public folder: https://www.dropbox.com/sh/avdfu4e3o17breq/1jxGsOXtJM

I think these will make brilliant marketing material for Bitcoin conferences and they are exclusive novelty items too. I may look up for possibilities to manufature these myself. But feel free to use all the data to get these produced if needed asap for conferences etc. Consult and discuss details with your manufacturer before production.

 +1

 

absolutly NOT

I know something strange happend... but can we find ourselves in the results?

Are we sure this thing is reliable?..

Already happened. People encourage people to do things for NXT and people do things for NXT and get paid for it.

So, what is the reason you cannot share a piece of your value with others that have not that much?

As you say: distribution is always a good thing for NXT.


Maybe, you are right. On the other hand side, you should take these circumstances into consideration:

1) NXT is new; centralism is intrinsic to new ideas, because they come from a single point; development is also performed centrally right now; etc. etc.
2) Until this bootstrapping phase isn't over, some central pushing here and there won't hurt.
3) When the bootstrapping phase is over, NXT should be able to sustain itself without being baby-sit by its inventors. Then all centralization should be gone. I totally agree.
4) If NXT is not able to sustain itself after bootstrapping, then, well, you know...