I propose they cut off a finger and send it to me by mail.
 Fingerprints is an obsolete technology. Retina scanners all the way! sending an eye is rather drastic... But that would reveal who REALLY cares  |
|
|
|
THE NAME MUST BE THE EXACT SAME TO QUALIFY.
I have different usernames, and I'd like it to stay that way. Why the hell should I change that? |
|
|
|
U shouldn't use poll this time. Force people to post their voices as messages.
I like the idea! Or people have to post an image of their handwritten votes? I propose they cut off a finger and send it to me by mail. I like the idea! I'm already cuttAAAARRRRRRGGHH. I'll send it ASAP. |
|
|
|
I made a Logo as I'm a graphic designer by trade but I don't know how to post it on a message. Any help would be appreciated.
put it on imgur, it'll give you bb-forum-like link, and just paste it here (img) are you fucking kidding? You're a graphic designer and you don't know how to add a picture, but then you do, and you add a picture of a link to your post? All you had to do was PASTE that LINK into THIS message. a) I'm not sure why you're replying to me and b) Dude, calm down, drop the coffee, take some pills or something |
|
|
|
I made a Logo as I'm a graphic designer by trade but I don't know how to post it on a message. Any help would be appreciated.
put it on imgur, it'll give you bb-forum-like link, and just paste it here  |
|
|
|
Besides real problems regarding binary formats, its psychologically most destructive property is that everybody has the self-proclaimed best encoding, the fastest encoding, the most space-efficient encoding, the most flexible encoding and so and so which only differ in one of two bits somewhere and therefore makes them 100% incompatible. Thank you.
Why? Because binary is the way to go if you want fast, efficient, direct, buzzword, buzzword, ....
Look at text-based format. Do all these requirements matter there? No. Their implementors focused primarily on the content in conjunction of readability, maintainability, flexibility, expandability and independence. All properties, which are required for the maintenance of long-term applications.
Having to deal with binary formats on a daily basis (for ca 5yrs), I cannot possibly express, how much I AGREE with you |
|
|
|
I'd like to re-iterate my support for a simple endian-neutral binary format. Encode integers using the simple variable-length scheme for numerical constants as outlined in section 2.1
This is bad idea for multiple of reasons (first one being, it would be real PITA for alternative core implementations) |
|
|
|
I did notice it, but I don't decide this question. The community does.
What is your opinion on that? I think it's a bad approach. We should rely on protocol version. Ok, so could something like protocolVersion be added to getInfo POST? Protocol version is sent with each peer request. Now, I finally know what it is! If so, why it isn't changed when (fork-resulting) changes are released? |
|
|
|
I've noticed two nodes running on it 85.130.59.83 192.0.239.235 |
|
|
|
I did notice it, but I don't decide this question. The community does.
What is your opinion on that? I think it's a bad approach. We should rely on protocol version. Ok, so could something like protocolVersion be added to getInfo POST? |
|
|
|
CfB, not sure if you've noticed "second post" regarding verison handling: This won't work when we have more implementations of the core.
It could be combination of both core + version, so <init-param>
<param-name>minimumVersion</param-name>
<param-value>NRS 0.5.11; .NXT 0.0.5.0</param-value>
</init-param>
(second one is minusbalancer's dotNXT) if app is not specified default actiot would be to "accept" |
|
|
|
Actually using ZLIB might not be the best idea, better would be something that's faster.
I'd go with LZ4. There's also lzturbo, but, lz4 has format that might be nicer for "small devices" (raspis & Co.)
And ChuckOne is right, binary protocol equals problems
Compression looks like a premature optimization to me. Let's make things more complicated when we actually need it. ChuckOne was suggesting to use compression on json instead of using binary format. We could compare the two options, and check how much compressed data is bigger than "native binary" |
|
|
|
Still, I strongly advice you to add another layer (compression whatever) instead of using a binary format.
I would agree that using, say, zlib style compression would be a better idea as it would allow for more TPS than the current JSON but would not be as tricky (i.e. stuff like "endian") as binary. I think 1000+ TPS is the eventual goal - but hey Bitcoin doesn't even do its currently max. 7 TPS at the moment (so no great hurry to get there). Even 100 TPS would put Nxt well ahead of the pack. Actually using ZLIB might not be the best idea, better would be something that's faster. I'd go with LZ4. There's also lzturbo, but, lz4 has format that might be nicer for "small devices" (raspis & Co.) And ChuckOne is right, binary protocol equals problems |
|
|
|
I'm just wondering if the ticker symbol of the coin should be tweaked a bit. I saw this mentioned in another thread... I think the name of the currency might sound better if it was "nemo" coin.
New Economy MOvement
No Envy MOvement
It still works and sounds better.
yeah, and sound like kids toy... |
|
|
|
or instead of a text file, it could be binary format, where instead of 100 character passphrase, its 256 bits of data representing the private key. In this case the client will not perform the first sha256 hash that it normally runs against the passphrase to obtain the private key.
If I could upvote this 1000 times, I would. NXT API should be changed, it should be client's resposibility, to secure your wallet. Also IMHO this would actually be MORE secure than what it is now, as the secret KEYS could be TRULY* random. *-now they are output of sha, so secret key is as secure as your pass |
|
|
|
|
Could someone contact with bter to add NXT/LTC trading?
|
|
|
|
I tried the peerexplorer's cache system - isn't there a better way to do it than creating a new account for each cache and polluting the blockchain?
+1, also bothers me |
|
|
|
Does anybody know how to setup a testnet? How many servers, etc.
I might need to get one setup as early as end of next week.
James
obtain a list of participants, have them generate new accounts from new passphrases these particiapants will provide IP addresses of their clients that will particpate. these IP addresses will be used in wellknownpeers files set up a network of clients that are configured to use some other 2 ports other than 7874/7875 have a member on 1 client willing to send NXT from their local client on the testnet from an existing account to all other new accounts then we are basically running on an isolated fork with just limited people Thanks! There is already one testnet running, search the thread. Running another one doesn't seem to have much sense |
|
|
|
So i've got another question, i had 2213 Nxt in my account. But somehow it's gone? No transactions are shown other than the one from the exhange site to my account..
What is your account number? What is the last block that you see? |
|
|
|
Does anybody know what percentage of hallmarked nodes have 1Mbps+
What about normal nodes?
James
I hope you're aware, that a) tx size currently is much bigger than 128 bytes... b) we're quite far from 1000TPS I am trying to make sure when we go to TF in April that the network is ready for it. CfB estimated 1Mbps to support that, so any nodes that doesn't have that bandwidth will need to use clients that don't do everything. Of course, just because 1000TPS is possible doesn't mean it will happen right away and I imagine it will be a gradual ramp, unless we stress test it ourselves. Who else would you recommend to be on the NXT infrastructure advisory group? I want to make sure we get input from all the people who are actually involved in setting up servers all the time. opticalcarrier, gbeirn, tbd, tbd. We still have time and can plan an orderly ramp up in NXT network capabilities. I just don't want to login one day in April to find TF was enabled while I was sleeping and we are doing 666TPS and everything went to hell James TF itself won't let you anywhere near 1000TPS on 1Mbps. Current tx size is rather closer to 500 bytes (and that is without aliases/messages) So besides TF switch to binary format must also happen, but I presume, this will happen before April. |
|
|
|
|
Show Posts
