|
I'd like to have the client on my computer be the only one that ever has access to my master private key, and give only a subwallet's private key to my phone - so that I can spend from any accounts on my computer, but only have any access to a certain subset on my phone. I know this is possible with BIP32 key generation, but the UI has no options for it and I haven't been able to find documentation on doing it. Can I do this by exporting my private keys, picking a subwallet's master key and importing that into the client on my phone? Or would that not work / confuse the phone's client?
|
|
|
|
The idea of 'redlisting' is unstoppable. I don't like it, but you certainly don't need the foundation or the US government to do it. Any one, anywhere, is free to analyze the blockchain and issue statements and reports based on what they find. In fact, there will by many different 'redlists'. It will be a free market unto itself, and people can choose what list, if any, they want to pay attention to.
A redlist accomplishes nothing as long as there is a significant proportion of people who don't recognize it, that people with redlisted coins can use to "wash" them (with or without their knowledge). So as long as at least one major client doesn't enable a particular redlist by default, that redlist is ineffective. |
|
|
|
|
Yeah, it's the ones with lots of speakers where several have similar voices that drive me crazy, I have to spend so much time seeking through the same file in two different mplayers, comparing voices...
|
|
|
|
|
I'd code that and release it under an open source license for 150mBTC. You'd be able to run it as a utility/cron-job, or as its own daemon. Configuration would be through a simple command-line interface. I'd design it in a way that adding more complex transaction rules in the future would be straightforward. I'd implement transaction execution via bitcoind, electrum, blockchain.info, or whatever wallet type you'd prefer, and make it easy to add support for other methods.
|
|
|
|
|
There is no general solution that flags Unicode-using URL look-a-likes, but doesn't flag text that doesn't contain any URL.
|
|
|
|
Actually I was referring to this thread: https://bitcointalk.org/index.php?topic=325824.0There was a guy there who'd independently studied the topic and had some interesting points, but he called it shellfish mining in the title and I just loved that image |
|
|
|
|
Reserving 57, the shellfish mining thing is super interesting
|
|
|
|
|
Haha, no man in India, it's all me, my dvorak keyboard, and vim =)
I don't usually listen to podcasts, but I've really come to like this one. I suppose I'll read the transcripts, after this past week I can read it in their voices anyway.
I split them the way they're split on the youtube channel (I put corresponding youtube links in the scribd descriptions), I just found them easier to work with taking them by chunks.
|
|
|
|
|
I think someone said they were doing 54.
I *think* these are the episodes no one has claimed:
16, 17, 19, 37, 38, 44, 46, 47, 48
|
|
|
|
|
I'd really like to code colored coins support for this. bitcoinx / NGCCC is implemented enough that this is possible now. The task status on Ciyam seems to be "review due", is it available?
|
|
|
|
|
BTW qwk, E23 was longer than listed in your post because there was a 48:18 interview with Jon Matonis that was in a separate clip for the episode.
So S=Short, L=Long, E=?
|
|
|
|
|
You talked a lot about the frontend shininess and advertising, and the non-disclosure agreement about what your business model is, and the funding approach, but didn't say anything about any kind of backend work being needed. Making a really nice Ponzi site?
|
|
|
|
|
Payment received for 20 & 21, thank you!
For 22 onward I'm reducing the timestamps a bit since I think they're making it look more cluttered than necessary.
|
|
|
|
|
Bitcurex, do you have an ETA for reactivation of your pln.bitcurex.com API?
|
|
|
|
|
Episode 20 is 65:39 (20.1=11:05, 20.2=26:15, 20.3=16:49, 20.4=11:25)
Episode 21 is 63:50
|
|
|
|
|
Show Posts
