just to explain why a colored feedback is not only eyecandy but usefull, consider this.
Ok, if you can make it purely on the client by checking local blockchain fast and cheap - that's great and should be added. I am just saying that this doesn't solve anything. You don't protect against typos, because there are plenty of legit cases where address will not be in the blockchain. Then, you don't protect against unhealthy server at all, because, well, you're a client. Checksums are used everywhere. Here we are talking about big money and the cost of failure is irreversible loss of it. Honestly, it's beyond me why are we even arguing this. you are misinterpreting my statement here. i am not against checksum at all. as said, this is an simple, quick and effective improvement compared to the current client, not more, not less. @marcus03, great work marcus. i have some question about how you have managed orphaned blocks and checkpoints etc. will contact you via pm. |
|
|
|
already wrote about this two weeks ago.
the client wil handle it this way:
1. check if address is within own address book -> green
2. if account exist within blockchain -> yellow
3. don't exist within blockchain -> red
simple visual control.
Why invent crazy schemes when there is a simple, elegant solution, which covers both client AND server - checksums. The way it's implemented in bitcoin. I don't buy the whole "oh my god performance" line of reasoning. You wrote it in Java, for god's sake  as soon the extra bit's are available for this, i can add it. just to explain why a colored feedback is not only eyecandy but usefull, consider this. the first step is to enter the address where to send the funds. when done the address field is loosing focus because you do the next step, enter the amount. at this point you get the visual feedback already about the account number. no need to fill out all other fields and press send to know something is wrong with your address. just a little thing but userfriendly and i can add it right now. as said, just an example... |
|
|
|
already wrote about this two weeks ago.
the client wil handle it this way:
1. check if address is within own address book -> green
2. if account exist within blockchain -> yellow
3. don't exist within blockchain -> red
simple visual control.
Some ppl confuse green and red... the user get's both, visual feedback and form warning.  without an additional alert dialog, the color wouldn't make much sense of course... |
|
|
|
already wrote about this two weeks ago.
the client wil handle it this way:
1. check if address is within own address book -> green
2. if account exist within blockchain -> yellow
3. don't exist within blockchain -> red
simple visual control.
Thx. But what about after clicking "Send"? As I recall wrong sends happened after correct address was set. you mean some kind of checksum? as soon there is a difinition for this i am adding it for sure. the above mentioned solution is of course very simple but effective as well. within an option tab you can set the warning level. of course the user will get an extra confirmation dialog for yellow and red after pressing send. a realtime verification during typing depends on the gui-latency but as soon the account number field lost focus the number is checked and gives a visual feedback. |
|
|
|
CfB + jean-luc + nexern,
There are millions of darkNXT and more being created all the time. darkNXT is NXT sent to an address that doesn't belong to anybody. I am assuming this is something we don't want the end user to be able to do easily. Anyone with direct API access could do whatever they wanted, but end users should NOT be allowed to create darkNXT, especially when all it takes is a typo or memory corruption.
The solution to this is so simple I am at a loss as to why it has not been implemented. NXT sent to an acct without key will create darkNXT, there is a call to detect if an acct has a key. Why has this simple guard not been implemented?
This is a very serious flaw and even ripple has a solution to this by not allowing money to an unfunded acct. We can't let horrible flawed useless ripple be better than NXT in this area can we?
James
P.S. For those not in the real world, EVERYTIME and end user creates darkNXT, it will create at least a support incident at worst lawsuits against a vendor supporting NXT. Need I remind people that we need widespread NXT adoption.
I hope nexern will fix this issue on client side. already wrote about this two weeks ago. the client wil handle it this way: 1. check if address is within own address book -> green 2. if account exist within blockchain -> yellow 3. don't exist within blockchain -> red simple visual control. |
|
|
|
Well I think we need to move faster. yes! and we will do. i am just adding the last components for the explorer (alias search), cleaning the codebase and finalize the explorer. it was planned to add some more features (filters/pagination/charts/mining calculator) but i think these are not so important, as long the main funktion is working properly. this can be done later and is on my todo list. i see the explorer more than a community asset than a personal project. tomorrow i am starting the client/asset-exchange fulltime, which means much more output from my side. the asset exchange is the most difficult part (async api/data storage/charts/order matching/different instruments like shared revenue, options, bonds etc.) but once fully functional all other services can be plugged in very fast. i guess much faster than other competitioners. the first beta should be ready in ~3 weeks (which is very sporty), ready to check heavily via testnet. if no major bugs are found the final is planned 1-2 weeks later and yes, competition is good, have no problems with that.  btw, happy new year! |
|
|
|
|
nexern - donations: 760220816713461210
|
|
|
|
Hello friends, I have finally completed a brand new profesionally looking introducing video for the Nxt hompage. It took me 6 days and long nights (one day up to 7 AM), but finally here it is: http://wideo.co/view/1504591387756502643-nxt-generation-of-cryptocurrencyIf you think the video deserves any bounties, donations or thank you gifts for my effort, Then my Nxt is: 15003961341330858247 If you like the video and think it will help build a good reputation (some guys wrote that they didn’t believe in Nxt, but after they watched my previous video ( http://youtu.be/zALTChPsXhQ), they changed the opinion). It took me about 50-60 hours to create it during these holidays. Since I have no job I decided to help Nxt with marketing and I will continue. But now I would also probably pay for the download of HD version that I would upload on: Youtube Facebook Vimeo and many other sites Then I would pay for deleting of the logo, if you think the video deserves to be used at our homepage (like Mastercoin or Bitcoin). Do not hesitate to comment video now, I can change or improve it before releasing it to the other platforms. There can still be changed logos if we choose another ones.. Then I will be promoting this video in at least 100 sites, in comments to other youtube videos, as I spent so much time making it, I will try to get as much attention as possible....  After a month of watching Nxt and trying to help the community I could insert to the video explanations of some myths and misinterpretations. I used my experience with other videos I had created before. Then I added my own research, when I used important comparations with Bitcoin… Thanks (big thanks) to Ola I could provide a powerfull voice over, and with permission of Psybits I used some of his sentences for the voice scenario, since I am from central Europe and I know english only thanks to TV Shows. Also I thank to QBTC for providing current logos in HD. -- Then I am planning to take care of the googledoc, put some organisation to the marketing departments... Since I can see tech section works fine here, we from the marketing must work hard too and help you build stronger community so you won’t need so much nodes  … It would be fantastic to have Wikia translated in 10 languages before 3rd January And yes, my Czech version isn’t all translated yet, but soon it will be. Then I must finally write some blog posts about last week big things, but I was so stucked with the video BTW we are still looking for: Indian translators, organizators and maybe english native correctors, since we have only 2. Maybe it will be enough. But all doors are always opened here: https://docs.google.com/spreadsheet/ccc?key=0AgAGADgnQcrtdHRrV3V3Z1lzOXVEMWtqdElUaEtqV1E#gid=1this is really cool, donating... |
|
|
|
ahh, yes, the hive. it's a personal project i start to built as soon the asset exchange is done.
since it is just a complex concept atm, the best is first to start coding and then showing a
prototype. this way the advanced ideas and features it could add to nxt are more understandable.
So... how many NXT per share are we looking at? no shares, it is (sorry for that ;-) just a pure profit tool but a very advanced one. and if possible and created, a tool to compete against major player within the global finance/stock market. they have money, direct market access and much deeper info sources. nxt, hopefully soon the hive. would be interesting to see what happend if we enter thier market this time. but as said, look at this what it is atm, vaporware. Keep up the awesome work, we are lucky to have you on dev team. thanks for your kind words msin but i have to admit, that the last time i talked more than coding (ok, it's holiday) which reminds me i planed to add the fulltext alias search today. |
|
|
|
ahh, yes, the hive. it's a personal project i start to built as soon the asset exchange is done.
since it is just a complex concept atm, the best is first to start coding and then showing a
prototype. this way the advanced ideas and features it could add to nxt are more understandable.
So... how many NXT per share are we looking at? no shares, it is (sorry for that ;-) just a pure profit tool but a very advanced one. and if possible and created, a tool to compete against major player within the global finance/stock market. they have money, direct market access and much deeper info sources. nxt, hopefully soon the hive. would be interesting to see what happend if we enter thier market this time. but as said, look at this what it is atm, vaporware. |
|
|
|
@ Nexern
What is "the Hive" feature
so it seems to me that "the Hive" is to be kept TOP SECRET till the appropriate time. ahh, yes, the hive. it's a personal project i start to built as soon the asset exchange is done. since it is just a complex concept atm, the best is first to start coding and then showing a prototype. this way the advanced ideas and features it could add to nxt are more understandable. |
|
|
|
great! this way (get) is fine too. so alt-client devs just providing/adding the desired uri-scheme, in this case thehive:
during alias creation and later then for the appropiate action triggering within the client, even if the target application
is outside e.g. a browser scope correct?
Yes ok, first i tought this approach will fragment the uri-scheme to much, which prevents creating a semi standard uri-scheme. on the other hand this approach means max. flexibillity. thx to clear my questions. |
|
|
|
would it be usefull to add an additional content-type field, which can be customized by alt-client developers
for api-servcices to other devices we haven't in mind now?
It's supported already via custom URIs. For example: thehive:action=joinNetwork&netId=42 great! this way (get) is fine too. so alt-client devs just providing/adding the desired uri-scheme, in this case thehive: during alias creation and later then for the appropiate action triggering within the client, even if the target application is outside e.g. a browser scope correct? |
|
|
|
alias is much more powerfull then just an uri/account/mails/phonenumbers shortener or stuff like this.
aliases could be also used as an mighty automation entity, e.g. to launch complete phonecalls,
sending a fax with an order confirmation, printing and sending invoices for goods bought
online, trigger db-events or even directing to gps location on interactive maps, if...we add
additional identifier fields to aliases. similar to http content-type. a content-type field could
be used for this. even if many of these examples could be done with other tools, why not
giving alias these functionality also if desired by developers.
It's already implemented. Aliases point to URIs like this -> "tel:+12024561111". If u put it inside <A href> u can make a phone call via browser. Edit: All that we need is to improve URI standard. would it be usefull to add an additional content-type field, which can be customized by alt-client developers for api-servcices to other devices we haven't in mind now? i bet in a few month we will have plenty dev's here asking to enhance the current uri-sheme. a content-type field would work as an very usefull wildcard for these services. every dev could add/cutomize his individual service with this. |
|
|
|
isn't it nessesary to adding some prefix standard to prevent content validating by parsing?
this number could be an account/transaction/block or even an phone/zip number or encoded gps location.
how could a jumpcenter find out what entity is behind this content without a declaration prefix?
entity parsing and validating doesn't work reliable this way or do i miss something here? any takers here? Is it about URIs? alias is much more powerfull then just an uri/account/mails/phonenumbers shortener or stuff like this. aliases could be also used as an mighty automation entity, e.g. to launch complete phonecalls, sending a fax with an order confirmation, printing and sending invoices for goods bought online, trigger db-events or even directing to gps location on interactive maps, if...we add additional identifier fields to aliases. similar to http content-type. a content-type field could be used for this. even if many of these examples could be done with other tools, why not giving alias these functionality also if desired by developers. |
|
|
|
isn't it nessesary to adding some prefix standard to prevent content validating by parsing?
this number could be an account/transaction/block or even an phone/zip number or encoded gps location.
how could a jumpcenter find out what entity is behind this content without a declaration prefix?
entity parsing and validating doesn't work reliable this way or do i miss something here? any takers here? |
|
|
|
how and then?
and then they ask how much ) exactly! more prceise if you doing right, they are asking your account number how much... |
|
|
|
coca-cola is not gonna be too happy either good thing is, they can't sue someone within nxt-space for aliases, there is only a nice big buy button where they can choose from. but they can alway find the owner thru Nxt-Messenger how and then? |
|
|
|
coca-cola is not gonna be too happy either good thing is, they can't sue someone within nxt-space for aliases, there is only a nice big buy button where they can choose from. |
|
|
|
I repost this from https://nextcoin.org/index.php/topic,797.msg14049.html#msg14049 coz it's importantAccount Alias
You can name your account with a alias. The rule is:
Alias:yueye
Url: nxt:5693933960808456307
This way is slightly incorrect. " nxt:" URI scheme tells that "5693933960808456307" is an alias, not an account id. U should choose other notation coz aliases pointing to other aliases will be used in future not announced yet features. I would advise to switch to other notation (for example, just "5693933960808456307") before it becomes widespread and lead to problems with standardization. isn't it nessesary to adding some prefix standard to prevent content validating by parsing? this number could be an account/transaction/block or even an phone/zip number or encoded gps location. how could a jumpcenter find out what entity is behind this content without a declaration prefix? entity parsing and validating doesn't work reliable this way or do i miss something here? |
|
|
|
|
Show Posts
