NXT :: descendant of Bitcoin - Updated Information

[Emule]

Hi guys,

Just saw this one the nextcoin forums. Has this been seen yet?
Can anyone give him an answer? Seems like a "hidden" cost for most users.

https://nextcoin.org/index.php/topic,3755.0.html

Is there any way to reduce or outright throttle bandwidth usage of the NXT client?

I've been running NXT client on Windows since mid Dec, upgrading to newest version when new ones are out.  The client uses between 150KB/s to 500KB/s.  This works out to 390GB to 1.2TB(!) per month.  My ISP charges dearly for exceeding 300GB/mo.  I first found this out because in Jan I unexpectedly hit 500GB of usage - thanks largely to NXT client.  In the first 10 hours of the new month, NXT client (now version 0.5.11) has already racked up 18GB of transfers.

I have high confidence in this next-gen currency, and want to participate in the network. And I don't want to lose NXT due to transparent forging penalties if I don't participate. But I can't pay Comcast another $50-200+ a month to be able to run such a bandwidth hungry app.

Please let me know any way to reduce the NXT client bandwidth consumption, and/or to set explicit throttle limits on it.  My apologies if this should be common knowledge, but I've already searched these forums and general internet for throttling or bandwidth related docs or posts and found nothing.  Thanks.

silence....

were is the great messias now?

BTW coudnt you wait to expose this till I was done selling, now everyone will start selling damn

and there is more... just wait...

  ?

Let sum up what we have finished here:

- Decentralized Alias System / DNS: yes but not Complete
- Basic DDoS Protection: Complete?
- Decentralized Asset Exchange / Colored Coins:NO
- Transparent Mining:NO
- Arbitrary Messaging: Complete but absolete
- Instant Transactions:NO
- Decentralized Marketplace / Auction:NO
- Distributed Storage:NO
- Multi-signatures:NO
- Blockchain Shrinking:NO
- Two-phase Payments:NO
- Voting System:NO
- Reputation System:NO
- Decentralized Mixing Service:NO
- Distributed Computing:NO
- Smart Contracts:NO
- Hardware Wallets:NO
- Advanced DDoS Protection Project Kharo:NO
- white paper: NO
- Client:NO

What do we have:

bloated Blockchain that uses GB's of traffic that no one can afford!
hot air
unclaimed coins
12 laughing rich initial founders.
rats leaving the sinking ship already

[mcjavar]

Hi guys,

Just saw this one the nextcoin forums. Has this been seen yet?
Can anyone give him an answer? Seems like a "hidden" cost for most users.

https://nextcoin.org/index.php/topic,3755.0.html

Is there any way to reduce or outright throttle bandwidth usage of the NXT client?

I've been running NXT client on Windows since mid Dec, upgrading to newest version when new ones are out.  The client uses between 150KB/s to 500KB/s.  This works out to 390GB to 1.2TB(!) per month.  My ISP charges dearly for exceeding 300GB/mo.  I first found this out because in Jan I unexpectedly hit 500GB of usage - thanks largely to NXT client.  In the first 10 hours of the new month, NXT client (now version 0.5.11) has already racked up 18GB of transfers.

I have high confidence in this next-gen currency, and want to participate in the network. And I don't want to lose NXT due to transparent forging penalties if I don't participate. But I can't pay Comcast another $50-200+ a month to be able to run such a bandwidth hungry app.

Please let me know any way to reduce the NXT client bandwidth consumption, and/or to set explicit throttle limits on it.  My apologies if this should be common knowledge, but I've already searched these forums and general internet for throttling or bandwidth related docs or posts and found nothing.  Thanks.

silence....

were is the great messias now?

BTW coudnt you wait to expose this till I was done selling, now everyone will start selling damn

and there is more... just wait...

  ?

Let sum up what we have finished here:

- Decentralized Alias System / DNS: yes but not Complete
- Basic DDoS Protection: Complete?
- Decentralized Asset Exchange / Colored Coins:NO
- Transparent Mining:NO
- Arbitrary Messaging: Complete but absolete
- Instant Transactions:NO
- Decentralized Marketplace / Auction:NO
- Distributed Storage:NO
- Multi-signatures:NO
- Blockchain Shrinking:NO
- Two-phase Payments:NO
- Voting System:NO
- Reputation System:NO
- Decentralized Mixing Service:NO
- Distributed Computing:NO
- Smart Contracts:NO
- Hardware Wallets:NO
- Advanced DDoS Protection Project Kharo:NO
- white paper: NO
- Client:NO

What do we have:

bloated Blockchain that uses GB's of traffic that no one can afford!
hot air
unclaimed coins
12 laughing rich initial founders.
rats leaving the sinking ship already

+ an idiot spreading fud

[Come-from-Beyond]

Let sum up what we have finished here:

- Decentralized Alias System / DNS: yes but not Complete
- Basic DDoS Protection: Complete?
- Decentralized Asset Exchange / Colored Coins:NO
- Transparent Mining:NO
- Arbitrary Messaging: Complete but absolete
- Instant Transactions:NO
- Decentralized Marketplace / Auction:NO
- Distributed Storage:NO
- Multi-signatures:NO
- Blockchain Shrinking:NO
- Two-phase Payments:NO
- Voting System:NO
- Reputation System:NO
- Decentralized Mixing Service:NO
- Distributed Computing:NO
- Smart Contracts:NO
- Hardware Wallets:NO
- Advanced DDoS Protection Project Kharo:NO
- white paper: NO
- Client:NO

What do we have:

bloated Blockchain that uses GB's of traffic that no one can afford!
hot air
unclaimed coins
12 laughing rich initial founders.
rats leaving the sinking ship already

I'm afraid u won't reach 0.05 price this way... 1 day left.

[Hacer88]

Hi guys,

Just saw this one the nextcoin forums. Has this been seen yet?
Can anyone give him an answer? Seems like a "hidden" cost for most users.

https://nextcoin.org/index.php/topic,3755.0.html

Is there any way to reduce or outright throttle bandwidth usage of the NXT client?

I've been running NXT client on Windows since mid Dec, upgrading to newest version when new ones are out.  The client uses between 150KB/s to 500KB/s.  This works out to 390GB to 1.2TB(!) per month.  My ISP charges dearly for exceeding 300GB/mo.  I first found this out because in Jan I unexpectedly hit 500GB of usage - thanks largely to NXT client.  In the first 10 hours of the new month, NXT client (now version 0.5.11) has already racked up 18GB of transfers.

I have high confidence in this next-gen currency, and want to participate in the network. And I don't want to lose NXT due to transparent forging penalties if I don't participate. But I can't pay Comcast another $50-200+ a month to be able to run such a bandwidth hungry app.

Please let me know any way to reduce the NXT client bandwidth consumption, and/or to set explicit throttle limits on it.  My apologies if this should be common knowledge, but I've already searched these forums and general internet for throttling or bandwidth related docs or posts and found nothing.  Thanks.

silence....

were is the great messias now?

BTW coudnt you wait to expose this till I was done selling, now everyone will start selling damn

and there is more... just wait...

  ?

Let sum up what we have finished here:

- Decentralized Alias System / DNS: yes but not Complete
- Basic DDoS Protection: Complete?
- Decentralized Asset Exchange / Colored Coins:NO
- Transparent Mining:NO
- Arbitrary Messaging: Complete but absolete
- Instant Transactions:NO
- Decentralized Marketplace / Auction:NO
- Distributed Storage:NO
- Multi-signatures:NO
- Blockchain Shrinking:NO
- Two-phase Payments:NO
- Voting System:NO
- Reputation System:NO
- Decentralized Mixing Service:NO
- Distributed Computing:NO
- Smart Contracts:NO
- Hardware Wallets:NO
- Advanced DDoS Protection Project Kharo:NO
- white paper: NO
- Client:NO

What do we have:

bloated Blockchain that uses GB's of traffic that no one can afford!
hot air
unclaimed coins
12 laughing rich initial founders.
rats leaving the sinking ship already

Let's see what you've got;

Patience: NO

[FrictionlessCoin]

Let sum up what we have finished here:

- Decentralized Alias System / DNS: yes but not Complete
- Basic DDoS Protection: Complete?
- Decentralized Asset Exchange / Colored Coins:NO
- Transparent Mining:NO
- Arbitrary Messaging: Complete but absolete
- Instant Transactions:NO
- Decentralized Marketplace / Auction:NO
- Distributed Storage:NO
- Multi-signatures:NO
- Blockchain Shrinking:NO
- Two-phase Payments:NO
- Voting System:NO
- Reputation System:NO
- Decentralized Mixing Service:NO
- Distributed Computing:NO
- Smart Contracts:NO
- Hardware Wallets:NO
- Advanced DDoS Protection Project Kharo:NO
- white paper: NO
- Client:NO

What do we have:

bloated Blockchain that uses GB's of traffic that no one can afford!
hot air
unclaimed coins
12 laughing rich initial founders.
rats leaving the sinking ship already

I'm afraid u won't reach 0.05 price this way... 1 day left.

Poster does raise a valid point,  if there are no developers volunteering (and the latest source code hasn't been released),  then who is going to build all these wonderful features?

[LiQio]

....
bs... bss.. more bs...
...

Please people never forget that our emule is a professional investor...

https://bitcointalk.org/index.php?topic=383259.msg4260845#msg4260845

he has massively invested in crypto - 

and btw. still dumping?

[Come-from-Beyond]

....
bs... bss.. more bs...
...

Please people never forget that our emule is a professional investor...

https://bitcointalk.org/index.php?topic=383259.msg4260845#msg4260845

he has massively invested in crypto - 

and btw. still dumping?

He already dumped. Now he is waiting for lower price to buy back.

[nexern]

quick apphub update.

have tested all basic functions account/alias/amessage (asset exchange close to complete) so far and it's working as expected, fast and stable but
there is a problem with keyphrases containing unicode characters. utf-8 encoding at codelevel is working but the gui engine supports iso 8859-15.

working on this.

[Hacer88]

quick apphub update.

have tested all basic functions account/alias/amessage (asset exchange close to complete) so far and it's working as expected, fast and stable but
there is a problem with keyphrases containing unicode characters. utf-8 encoding at codelevel is working but the gui engine supports iso 8859-15.

working on this.

Good news! When can we test it? 

[landomata]

NXT AROUND THE WORLD in 8 MINUTES!



What do you guys think about this IDEA.

https://nextcoin.org/index.php/topic,3807.msg36016/topicseen.html#msg36016

[Hacer88]

NXT AROUND THE WORLD in 8 MINUTES!



What do you guys think about this IDEA.

https://nextcoin.org/index.php/topic,3807.msg36016/topicseen.html#msg36016

Nice Idea! If we can make a nice video of this. It'll be awesome!

[nexern]

quick apphub update.

have tested all basic functions account/alias/amessage (asset exchange close to complete) so far and it's working as expected, fast and stable but
there is a problem with keyphrases containing unicode characters. utf-8 encoding at codelevel is working but the gui engine supports iso 8859-15.

working on this.

Good news! When can we test it? 

this not so good, because as mentioned above existing accounts with unicode keyphrases are not supported this way. this has to be solved.

[landomata]

quick apphub update.

have tested all basic functions account/alias/amessage (asset exchange close to complete) so far and it's working as expected, fast and stable but
there is a problem with keyphrases containing unicode characters. utf-8 encoding at codelevel is working but the gui engine supports iso 8859-15.

working on this.

Good news! When can we test it?  

this not so good, because as mentioned above existing accounts with unicode keyphrases are not supported this way. this has to be solved.

account holder with unicode keyphases don;t have to use your client till it's fixed.

but new users can begin immediately with your format.

[maratmmz]

quick apphub update.

have tested all basic functions account/alias/amessage (asset exchange close to complete) so far and it's working as expected, fast and stable but
there is a problem with keyphrases containing unicode characters. utf-8 encoding at codelevel is working but the gui engine supports iso 8859-15.

working on this.

Just tell us WHEN?

[QBTC]

Blockchain Explorer shows support in my marketing account for the continuation of website and networking. I very much appreciate it! Thank you.

[FrictionlessCoin]

quick apphub update.

have tested all basic functions account/alias/amessage (asset exchange close to complete) so far and it's working as expected, fast and stable but
there is a problem with keyphrases containing unicode characters. utf-8 encoding at codelevel is working but the gui engine supports iso 8859-15.

working on this.

Good news! When can we test it?  

this not so good, because as mentioned above existing accounts with unicode keyphrases are not supported this way. this has to be solved.

The setup using the secret phrase is unfortunately not a universal solution.  It depends on what browser you were using when you set it up.  If you happened to be on windows browser, then you won't have UTF-8 encoding.  So when you walk up to another machine, say an android phone, your pass phrase won't work in certain cases.  

This is just a flaw that really doesn't have a solution.

[NxtChg]

If pointing out your last resort of snarks/eyerolls is ignorant and rude, so be it. I just don't think it's productive (neither is my bitching about your bitching, so I should probably just STFU now).

Hey, I don't enjoy sounding like a prick either

Ok, I guess, fair enough. I should probably try one more time to convince him with arguments, instead of just bitching.

So James, consider this:

To test the old system you need to go and ask Jean-Luc to build-in a distributed cryptographic accumulator and then the rest of the libzerocoin via c++/java bridge, all this so you could just see for yourself, how horrible that system is.

Then, in a couple of months, when zerocash comes out, you're gonna come back and ask him to scratch all that and replace it with a distributed Merkle tree and a completely different ZK-proof system, based on SHA256 code, translated by a specially modified GCC compiler into code for a custom VM (which also needs to be implemented in our system, by the way).

Is this your plan? Because, frankly, it doesn't look very practical.

[McDoxy]

Let sum up what we have finished here:

- Decentralized Alias System / DNS: yes but not Complete
- Basic DDoS Protection: Complete?
- Decentralized Asset Exchange / Colored Coins:NO
- Transparent Mining:NO
- Arbitrary Messaging: Complete but absolete
- Instant Transactions:NO
- Decentralized Marketplace / Auction:NO
- Distributed Storage:NO
- Multi-signatures:NO
- Blockchain Shrinking:NO
- Two-phase Payments:NO
- Voting System:NO
- Reputation System:NO
- Decentralized Mixing Service:NO
- Distributed Computing:NO
- Smart Contracts:NO
- Hardware Wallets:NO
- Advanced DDoS Protection Project Kharo:NO
- white paper: NO
- Client:NO

What do we have:

bloated Blockchain that uses GB's of traffic that no one can afford!
hot air
unclaimed coins
12 laughing rich initial founders.
rats leaving the sinking ship already

[nexern]

quick apphub update.

have tested all basic functions account/alias/amessage (asset exchange close to complete) so far and it's working as expected, fast and stable but
there is a problem with keyphrases containing unicode characters. utf-8 encoding at codelevel is working but the gui engine supports iso 8859-15.

working on this.

Good news! When can we test it?  

this not so good, because as mentioned above existing accounts with unicode keyphrases are not supported this way. this has to be solved.

account holder with unicode keyphases don;t have to use your client till it's fixed.

but new users can begin immediately with your format.

correct, this is not a problem for new users or users without unicode keyphrases but don't know how many e.g. chinese users we have now using chinese symbols as keyphrase.
anyway, i am finishing apphub now. it was already planed to include unicode into hive and apphub is part of this.

[Come-from-Beyond]

correct, this is not a problem for new users or users without unicode keyphrases but don't know how many e.g. chinese users we have now using chinese symbols as keyphrase.
anyway, i am finishing apphub now. it was already planed to include unicode into hive and apphub is part of this.

Is it possible to postpone release a little so other AE client devs catch u?