I can't cook much beyond boiling an egg myself - but fundamentally Chinese about basics like "oil and garlic" and the correct preparation (a lot of chopping up of ingredients which is why "mapo doufu" might be an easier starting point).

Certainly "wok" cooking is not very difficult (and is very quick).

Also note that traditional "mapo doufu" includes Sichuan "wild peppers" which *literally make your lips and tongue numb* (so you may have to decide whether or not you want to include those as a lot of westerners don't like that).

You could term it Web 2.0 if you like but I think of it more as Internet 2.0 because I see that *all* the things we do today (such as email, IM, photos, file storage, audio and video) will end up over this new "software infrastructure" (not just what we think of as "web services").

Also I believe that as we look towards things like "mesh nets" the new internet will drift from the "traditional transmission" as well (so not only software but hardware as well).

Although I can't eat spicy food now when I did one of my favourites was "mapo doufu" (a very popular Sichuan traditional Chinese dish).

It is basically minced meat (normally pork) and tofu with a bunch of red hot chilly peppers!

Easily cooked in a wok and no difficult preparation.

IMO these technologies will be the *backbone* for Internet 2.0 applications (as opposed to the centralised servers and DB storage systems used today).

Information in the digital age "likes to be free" - so any hiring would not be for such trivial tasks but only for construction of entirely *new* ATs (i.e. *skilled work*).


I think that we are not as far away from this as you might think.

In the short term I can see the appeal - what we are going to end up with in the long term though I think is something rather different to that.

If you look at things like Bitcloud what I am seeing is that application storage (i.e. the DB) doesn't need to be "on a server in the cloud" but actually in the "blockchain itself" (it is a distributed DB).

Applications themselves would also be stored in the same way - meaning that we "don't need servers running applications" as we do today but instead we just have nodes forging and exchanging storage usage.

So "applications" becomes ATs and "DBs" become "parallel storage chains".

Although I do wish "NXT starter" all the best understand that the AT system will allow you to create a crowdfunding AT that requires *zero trust* and *zero commission* (will simply be run by fees).

The plan I have in mind is to make this as simple as a "form that you will fill out" in order to create this AT (so no need to even understand programming at all).

It isn't easy to understand Internet 2.0 as we have all become so used to Internet 1.0 but hopefully people will see that "centralised websites" are going to have to become "a thing of the past".

What I think would be really great would be an "offline" smartphone that does tx signing via QR code (would only be perfect if the *fee* in Bitcoin was not *implicit* unfortunately - a design *flaw* of Bitcoin IMO).

If said smartphone could also use QR codes to do "sign up/sign in" for websites we would have a very useful little device (and even better if it could do PGP/GPG encryption/decryption).

I think then maybe Nxt was never the right choice for you to look at (there are plenty of alt coins out there which are Bitcoin/Litecoin clones so you have many other choices).

There are even Nxt clones now too!

Your criticism has been noted and hopefully in another month we won't see the same kind of problem appear again (flame wars don't improve software - that takes work which is going on as we are posting).

You have been rather emotional yourself - your "legitimate" questions I think have been reasonably answered (if not in as "polite a fashion" as you would be happier with - but I think you didn't help yourself with your own way of asking the questions).

When the "default client" has been changed that would make sense - and maybe the OP might also consider providing some links to the "alternative clients" if that is not there.

So - without anger - we understand that the "default client" is not good enough and there are new clients available one of which will *very soon become the default*.

If ECDSA algos can be coded in Javascript then I assume some sort of "big integer" stuff must have already been created.

(this shouldn't be a big problem - just will require the use of a .js *library*)

Maybe so (notice I did not *offer him NXT*).

Sometimes it is best to just try and patiently explain things until they "sink in" rather than "getting upset" (this applies to both sides of course).

Even the "die hard supporters" must admit that Nxt is still *in alpha* and is nowhere near ready for "mainstream usage yet".

I will give @solarion the *benefit of the doubt* rather than just "shooting him down in flames".

Yes - it is unfortunate that the "default" client doesn't stop you from entering an "empty" password (or a non-secure one for that matter).

As has been mentioned this will be addressed when the "new" client becomes part of the Nxt standard software.

Understand that early Bitcoin versions had even worse problems (gmaxwell has mentioned some of those) so always when using "alpha" software *be very careful*.

Indeed - thank you theymos then I guess!

EDIT: (locking topic)

I sent a PM to theymos requesting to change from "CIYAM Open" to just "CIYAM" but have received no reply.

From what I have read I gather that he isn't offering to do that now - so is there any way (other than paying 10 BTC) for me to get that changed?

What happens is that the 100 (depending upon config settings) addresses that exist in the "key pool" which you haven't used are "discarded" to be replaced by new ones that are encrypted (otherwise your new encrypted wallet would be unsafe if someone found your old unencrypted backup).

So the problem is as soon as you create a new tx to either receive BTC or make an outgoing tx that needs a *change* address (and most of the time it will even though you might not realise it) then now your "old backup" cannot see these addresses (as they are completely *new*).

So - keep your old backup - encrypt your wallet and then make a *new* backup (before doing any txs).

Then only after you have checked that your new wallet backup *works* do new transactions - hope that helps clarify things (and yes your old backup is not very useful after you have made any new txs).

I would agree - "it is his baby" so unless they "push him into the background" he'll stay.