Oh sorry I wasn't thinking of course of the Amazon option whereby Amazon merely does fullfillment for a seller! Sorry! I was thinking an older version of Amazon, where the stale inventory problem would be their problem not the manufacturer's! If you don't want to be stuck with stale inventory don't order more container-loads than you can sell!

But yeah its not mass-market enough yet for that, of course currently Amazon would insist on doing the "we just fullfill for you" model instead of "we wanna buy containerloads of your hot gadget because we can sell it like hot cakes" model. Maybe if all goes well when the next generation comes out Amazon, NewEgg, The Source, heck everyone even slightly more slanted toward electronics/gadgets than Walmart/Kmart will be banging down their doors to pre-order containerloads of this hottest new gadget in years, that prints the newfangled $15,000+ per coin internet money known as bitcoin...

-MarkM-

The GUI is spaghetti-code-entwined into the daemon.

Thus if you use the GUI, you just tell it to also act as a server, by setting server=1 in config or --server on commandline or something like that.

The daemon you don't need to tell it to act as a server, as that is all it does, it lacks all the spaghetti-code monstrousness of the interwined GUI-code.

It would have been lovely if Satoshi had coded a GUI as a totally distinct separate thing from the actual back end, but he didn't and trying to dis-entangle them is hard enough that doubtless some folk figured he actually had to entwine them to get the GUI to work nicely since a GUI that constantly knows the exact state of the back end has certain advantages. A mess of callbacks would be needed otherwise, or a whole lot of polling, and so on.

So basically you either run the GUI version or the daemon version. To get the RPC calls when running the GUI you tell the GUI you want server mode enabled, which basically means provide what the daemon does as well as providing the GUI.

The daemon also has a mode in which it merely acts as a communications interface to talk to the resident copy of the daemon. That is maybe confusing if you are used to having a separate control program to talk to your daemons. Apparently there is even now some talk about making that separation in bitcoin, so you'd run bitcoind and it'd go resident, then use bitcoinctl or ctlbitcoind or some such to talk to it. But right now e.g. devcoind is also its own control/communications program. Probably it would equally well talk to the GUI's server mode, so if you wanted from the commandline, a script etc to ask the GUI, that is in server mode, some info you'd go "devcoind getinfo" just like you would to ask the resident daemon some info.

-MarkM-

On dvcstable01, getinfo says "blocks" : 113658 so maybe you aren't quite caught up yet?

(Your image says 105341 down at the bottom... that would be a couple of months or so ago...)

-MarkM-

Etc etc.

Overall though, isn't that what Amazon etc are for? Just churn out the superior units and ship them by the containerload to someone that does all that etc etc etc stuff from their worldwide network of fulfillment centres?

-MarkM-

If bitcoin is only worth six hundred and some dollars next spring that would be very disappointing.

It needs to be worth thousands if it is ever to be actually used for real other than by some tiny clique. I have constantly been amazed at how long it managed not to go up into the thousands. Hopefully we have finally reached the start of the adoption curve...

-MarkM-

First tell us how many services for litecoin you are going to deploy by then. As its value is unlikely to be a function of time but, rather, of whether people actually sit down and make it useful instead of just sitting on a pile of it crowing about how valuable it is or is going to be.

One thing I see as a bad sign is one doesn't hear about it being able to support merged mining. So unlike bitcoin, which embraced merged mining, thus could become the solid pillar of stability / hashing power to its entire family of blockchains, litecoin is somewhat of a pariah, all the other coins using similar hashing (scrypt) being forced to compete with it instead of upholding it supporting it adding value and importance to it by adopting it as their primary chain in their merge... Nor does it talk about supporting being a secondary chain either, so even as a secondary chain in the event some other scrypt chain ends up attracting all the scrypt miners it is again out of luck...

-MarkM-

It is old code, even the new database the latest bitcoins etc use takes time to catch up to the blockchain.

Old code could take days to get the blockchain maybe, depending on your modem speed and the speed at which your processor can verify blocks.

Certainly it could take hours. Quite a few hours.

What block does your client say it is on? (Damn do GUI clients even tell you what block they are on? I don't use GUI clients...)

-MarkM-

Hover your mouse over the link to your article.

See that it says wiki:user ?

You need the colon in there, [[:pagename]] or something like that, to make the link point out of the user-pages section to the actual main articles section.

-MarkM-

So how does that work? Can you buy it at half a cent in USD then buy almost two cents worth of bitcoin with it?

-MarkM-

Less than $1000 for a 3D printer that prints metal: http://gigaom.com/2013/11/12/meet-the-mini-metal-maker-a-basic-sub-1000-3d-printer-that-prints-metal/

One of our goals was 3D printing metal wasn't it?

-MarkM-

Oh congratulations on finally getting to the blockchain size / transaction rates stuff that was argued to death way back when.

Maybe if you can resist posting and just read you could research all that over in the technical section.

-MarkM-

That's weird, my calculations claimed it was way up near two cents a coin again today. Maybe come from believing MtGox's (weighted average) bitcoin prices though.

-MarkM-

Wow dirt cheap coins. If I hadn't already mined enough to meet my current needs I'd be so interested in snapping them up.

But as I already have some I am instead just rather disappointed at people being so eager to drive the price so low aka to throw them away so darn cheap.

Hopefully though someone actually interested will snap up these dirt cheap offers before we get onto any exchanges.

LTC isn't even a sci-fi coin though! Shouldn't you be cashing them in for gold pressed latinum and Federation credits and such to buy some new warp drives or something?!?

-MarkM-

This was a much nicer launch than all the ones back when there were new coins every day and all massive orphan-fests of insta-mining.

So its looking pretty nice to me so far compared to pretty much all the others I tried setting up right away when they launched.

If you do manage to enable merged mining that would be really cool as the existing panoply of merged mined coins has no PoS coin yet so it would help round out the set of merged coins,

-MarkM-

Nice! Is that price pretty widespread due to arbitrage or way out of line with what has been happening elsewhere / in the west?

-MarkM-

Oh don't tell them! The protoshares difficulty is high already for gosh sakes!

What are you thinking about TAG while we're on corporate-sponsored coins?

-MarkM-

Mine might be ancient, but it is unchanged since whenever partly because it has been working 24/7, for example on dvcstable01 and dvcstable02, ever since then. And run fine on other boxes too from time to time.

Only claim I have seen of it crashing was recent hearsay from someone claiming that RealSolid had claimed it crashes.

I also had the impression RealSolid might have been hacking at it and might not have been using my working version (*) too.

So thus far I haven't really seen much need for any "fixes".

Other of course than, like all the merged mined coins, a full upgrade based on the latest I0Coin to get all the RAM-hog fixes.

-MarkM-

(*) http://sourceforge.net/projects/galacticmilieu/files/  aka  https://github.com/knotwork

False advertising is not hearsay.

Actually I always had the impression that hearsay was when someone else claimed someone said or wrote something, not when the person actually did say it or write it themselves.

A poster by Pepsi corp claiming their cola cures cancer is false advertising; someone telling you they saw such a poster on the subway is hearsay. Or so I had always thought. I am not a lawyer though.

-MarkM-

EDIT: Oops, my bad, that should say such a poster might be false advertising; I don't actually know for a fact that Pepsi cola doesn't cure cancer... Just like we maybe don't yet know for a fact that they don't refund your bitcoins-paid...

The termcap (terminal capabilities) the curses library (cursor control) is using by default might be one for a linux textmode terminal, possibly putty might default to a strictly correct vt100 emulation or something. If you can find out what termcaps entry putty uses, or set it to the one you are actually using, that could help maybe.

Check putty help screens for stuff about terminal emulations maybe?

-MarkM-

I lost track long ago of what all the different versions were trying to do.

Someone sent me what was supposedly a patch to put some images in place and it was patching a totally different directory structure than the repo it was supposed to be patching.

I use what I have on my github and sourceforge, they work, daemons have no icons anyway so I don't know or even care what icons they have, certainly not if the entire directory structure has to be changed around to no longer match the normal bitcoin and most other coin repos in order to get some different icon into place.

They might even have icons as I recall much longer ago someone just sent identically named images to what coins already use for the standard images, that merely happened to look different visually without needing any code or filename changes to use them. Though maybe that was some other coin than devcoin if it is so important that devcoin's icons be moved around to some different directory structure.

Another in-progress version was aiming at depending on some fancy custom-nameserver based seeding system requiring a custom seeder daemon / nameserver service that didn't actually exist yet, I don't know if they even yet got such a seeder daemon set up let alone a few of them for redundancy so the code I use sticks with just knowing some hostnames to try to connect to so it won't be dependent on the custom nameservice thing that we don't actually seem to have. And retains the use of IRC too.

-MarkM-