Yeah, I got nothin'.

I've been waiting for verification since 21st October. Is this normal? How long is verification taking to turn around these days?

I'm messing around with the API and it seems that api/tradeHistory/SECURITYNAME returns the last month of trades. I know ?range=all will give me everything, but is there any way I can get e.g. the last 24h of trades? I can filter them out myself, I was just wondering if there was another way.

And another one (after this I'll just start shouting Bueller?): I don't seem to be able to subscribe to both depth and trade messages. If I do, I get depth but not trade. I can repro this in <50 lines of python; is this normal behaviour?

Thread necro! Is there a limit on the number of times you can call private/idkey? My bot asks for it at startup, which is many times a day during development, and towards the end of the day (perhaps past midnight, if that has anything to do with it?), I start getting "invalid call" back instead of the key.

It's trivial enough for me to store the idkey and the time it was requested, but I wanted to know if anyone else has seen this behaviour, or if it's just Broken On My Machine?

Ta.

That works for me, thanks! It's really helpful that the documentation is full of lies 

Well, it seems that the diagnosis for at least one of these two issues is "I'm an idiot" I've edited my post above with an update.

Folks,

I've been reading this thread with interest as I too am writing a client in Python (using websocket-client). I'm connecting over plain old websockets (not socketio) and am mostly working apart from a couple of issues:

1. Once the connection is established I subscribe to the USD trades channel:
...but I get the remark spat back "Unknown channel requested or not a public channel". I seem to be subscribed to trades by default, so this isn't a huge problem - but is there anything I'm doing wrong here?

2. My websocket connection keeps dropping, for no reason that I can see. This thread's history has some talk about having to send heartbeat messages, but from what I understand that's only when you're connected to socket.io, not the plain old websockets I keep on using. I find all clients I run drop at the same time, regardless of when I start them, which makes me suspect the problem is on Gox's end. I can easily reconnect to it when it drops, but it's frustrating because it takes about 90s between the connection being dropped and me getting a new trade message after I've reconnected. EDIT: I discovered a settimeout(5) sitting quietly in the code, which was likely wrecking things... removing it and upgrading websocket-client to 0.11 seems to have done the trick.

Any advice would be much appreciated!
-Floomi

For context, I'm in the UK, but I suspect the answer will apply regardless of the jurisdiction.

I'm of the understanding that if you buy BTC and then sell for profit at a later date, you're liable for Capital Gains Tax. But what's the tax situation if you're mining coins, and then selling them on your local exchange? My intuition is that it can't be CGT, because you didn't buy the coins in the first place - in the extreme case, you bought a mining rig, which was then used to produce coins, which you later sold. But I find it impossible to believe that you don't have to declare income gained like this. So what does it fall under?

Agreed with the sentiment already expressed: we should buy bitcoin.com if possible. If the currency is to take off, the Average Joes and soccer moms need to start using it, and refusing to take a .com domain simple because of ideology is, at the most polite, not pragmatic.

This is also completely distinct from the argument of "your grandma couldn't use bitcoin anyway, it's too complicated; she'd need a vastly simplified interface". Indeed, that would be a more than legitimate - and likely quite productive - use of the bitcoin.com domain.

Then they can set up their own exchange and use that instead. Or convert to dollars and trade on Mt. Gox.

This is, of course, pure speculation.

Fairly sure Genjix said a few pages back the new version won't be accepting OpenID.