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.
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.
Looks like I am god of the software development ! You could login both dotNXT and web browser using the same password in windows. dotNXT is using Unicode inside... Oh wait. Maybe it's not an unsolvable problem?