nwh

11 ms·

61.
by nwh 12y ago
There's good reason to run a fully validating client. SPV clients have quite a nice usability but really fall down in the security and privacy departments. As it currently stands people using Multibit have next to no privacy for a vari
62.
by nwh 12y ago
You make them sound casual, bitcoin has has really only had one hard forking change to enable pay-to-script transactions.
63.
by nwh 12y ago
Trivial to solve with OCR though, which sort of defeats the purpose entirely. I'm fairly certain the letters would just be in plaintext in the SWF anyway, so it's probably breakable for a malicious person at no cost. Hard for the
64.
by nwh 12y ago
I've shocked myself badly a few times and to me at least, I'd much rather wallow in self pity for a while than do it again. Probably the worst was one I didn't expect, I slipped when opening a plastic case and caught my finge
65.
by nwh 12y ago
I'd just love them to fix iMessage so that it works in something approaching a sane way. Messages "don't send" but appear on other devices, messages that are "delivered" never left my device, you still can&#x
66.
by nwh 12y ago
It really hasn't been lowered. Most users aren't running the latest code, so you would struggle to ever get your transaction into a block that way.
67.
by nwh 12y ago
Sort of fuzzy in some countries. In Australia categorising data is something not protected by copyright, say a phone books listings of numbers, because there's only one way to do that and there's no creative process involved. Some
68.
by nwh 12y ago
Neat idea, but that website needs some serious contrast. Almost unreadable when scaled.
69.
by nwh 12y ago
Prolexic hosts this site which has for some reason kills connections from my entire IP address range (residential DSL). Wonder what one of my IPv4 neighbors did to piss them off.
70.
by nwh 12y ago
That's sort of nonsense, CoinJar beat them to it.
71.
by nwh 12y ago
Something tells me you don't want the lithium in your batteries reacting with the water in the air.
72.
by nwh 12y ago
> Assuming you mean "ditch the huge, thick coax connector", yes. Whoops, lost a bit of meaning when I revised that sentence and didn't look over it. I'm not really sure what to think of the whole "watch" t
73.
by nwh 12y ago
> I don't see much of an upside doing this. Well you ditch the huge, thick lightning connector for starters. That's why the MacBook Pro doesn't have ethernet anymore, it's just too thick for the case.
74.
by nwh 12y ago
From a practical view the original authors were anonymous, would they really shed that to sue somebody forking their code against the license? Probably not.
75.
by nwh 12y ago
bitcointalk.org is spending millions on their new forum system that's being written from scratch. Hopefully that will be one to look out for when it's complete.
76.
by nwh 12y ago
One of the core developers lost over 330 BTC to Mt Gox. Tell me they are not technical experts.
77.
by nwh 12y ago
No, it's just why exchanges don't needlessly segregate wallets.
78.
by nwh 12y ago
Segregated wallets doesn't work, that would mean every single trade would be a transaction on the block chain. It would absolutely flood the network and result in massive fees. It literally can't be done that way.
79.
by nwh 12y ago
What the hell? When did I suggest that? Client side validation wasn't even a part of this, the rules are clearly enforced at the server as well. > By the way, I made mention that perhaps they're encrypting the string, and not
80.
by nwh 12y ago
You've utterly missed the point of this. If they hashed the user input, it wouldn't matter what the client gave them in terms of password requirements. Spaces, special characters, arbitrary lengths up to tens of thousands of chara
81.
by nwh 12y ago
Which begs the question why I was downvoted heavily and posted to @shit_HN_says for making the comment.
82.
by nwh 12y ago
I'm very much aware of that. I'm saying that because they're disallowing the submission of spaces, they aren't hashing their passwords when they get to the server. > they're checking the string server-side, befo
83.
by nwh 12y ago
No spaces in passwords? Obviously not hashing them.
84.
by nwh 12y ago
Solution: http://archive.today/IvjNH
85.
by nwh 12y ago
QR codes aren't the sort of thing anybody has been trained to click though, there's no other cue to even begin to suggest that it might initiate a payment request. To me that would just be a QR code of a Bitcoin address that is in
86.
by nwh 12y ago
That UI stinks. Who would know to click on the QR code to open a payment request? A payment request doesn't even involve addresses that are visible to the user, it makes no sense that it is under "send to address".
87.
by nwh 12y ago
No, the cost is due to scale. Producing ASIC chips involves millions of dollars of setup.
88.
by nwh 12y ago
Bitcoin miners can not be re-purposed. They take a header input and output only nonces, not hash results.
89.
by nwh 12y ago
Nothing. People make this mistake when doing legitimate things too. You're meant to make a new address for every single client. The response could be that they only send to unique TXID that haven't been used before, but you can al
90.
by nwh 12y ago
Is there anything to suggest this is real? Classic scam would be to just sell a bunch of random data, people tried that when Mt Gox was compromised. People apparently provided "samples" on IRC with either random data or data from

More ›