nadaviv

34 ms·

301.
by nadaviv 13y ago
More of a technical exercise, but I could see it coming handy in the future.
302.
by nadaviv 13y ago
Hey, I'm the author. I'd love to hear your feedback.
303.
Show HN: btproof - trusted timestamping on the Bitcoin blockchain(btproof.com)
75 points by nadaviv 13y ago|29 comments
304.
by nadaviv 13y ago
Or they could just reply with a confirmation link.
305.
by nadaviv 13y ago
He seems to be correct. Here's the comment with more information: http://www.name.com/blog/general/2013/05/we-got-hacked/#comm...
306.
by nadaviv 13y ago
They mentioned they're using bcrypt in the comments: http://www.name.com/blog/general/2013/05/we-got-hacked/#comm...
307.
by nadaviv 13y ago
For the case of buyer-seller disputes, Bitcoin has a really neat way of handling escrow with its m-of-n transactions [1]. You can make a payment that requires 2 of 3 public keys (the 3 keys being the buyer's, the seller's, and a trusted thi
308.
by nadaviv 13y ago
And where do you think that money comes from? The financial system bears the cost of fraud by taking more money from everyone. That's an horrible replacement for proper security. I'd much rather to simply pay insurance to cover for fraud, o
309.
by nadaviv 13y ago
Break SHA256, and you can cause hash collisions that allows you to easily mine blocks until 51% of the network switches to a better hashing algorithm (which should happen pretty quick, because it'll be obvious that someone broke it). To ste
310.
by nadaviv 13y ago
Not quite. Credit card numbers can be (and mostly are) stolen from websites that accepts them. That's not true for Bitcoin - you have to gain access to the customers computers that stores the private keys. In that regard, Bitcoin is actuall
311.
by nadaviv 14y ago
> It's just that they run into situations time and time again where class-based OO is a better option Can you give an example of such situation? My experience with prototype-based inheritance is quite different - I find that it can do e
312.
by nadaviv 14y ago
Originally found on http://www.reddit.com/r/Bitcoin/comments/1bq2p8/coinbase_pub...
313.
Coinbase publishes your name and email publicly(encrypted.google.com)
33 points by nadaviv 14y ago|6 comments
314.
by nadaviv 14y ago
I guess that's right. Someone with enough computing power could harm bitcoin to the point it'll be unusable. But the people with those motives (government, banks) are much less likely to be part of something like that than people with finan
315.
by nadaviv 14y ago
No. If someone does manage to control 51% of the computing power of Bitcoin, he's much better off using that to mine bitcoins rather than "cheating". If he'll use it to cheat, he'll cause panic, make bitcoin drop their value and undermine t
316.
by nadaviv 14y ago
`<form>`s are allowed to send POST requests to wherever they want, without any restrictions. By creating a form that points to another domain, and automatically submitting it, you can send a POST request to wherever you want [1]. PO
317.
by nadaviv 14y ago
There's nothing stopping anyone from sending POST requests to wherever he wants, even without an XSS. the same-domain origin policy only forbids you from reading the response, not from sending the request. CSRF-wise, POST requests are just
318.
by nadaviv 14y ago
The big jump was due to a donation of 4500€ from telerik.
319.
by nadaviv 14y ago
You could setup tor nodes on your own servers, than configure your client to use them and mix in some regular public nodes. Its even better if you make your tor nodes public and let other people use them too, to make it more difficult to co
320.
by nadaviv 14y ago
The problem with that is that different people viewing the same URL (/profile.php) gets a different resource. What happens if someone gives a link to his profile.php over IM or something, expecting it to show his own profile? The URL the us
321.
by nadaviv 14y ago
If you manage to get the code to execute on a worker or an iframe, you should have a clean environment to operate in, with your own copy of the native environment and prototypes. The question is... how do you create an iframe or worker safe
322.
by nadaviv 14y ago
Try diffing the compiled source for 1.4 and 1.5.
323.
by nadaviv 14y ago
> All of these ignore the fact that functions are not simply declared once in Javascript and then used later, like in C. It's a dynamic language with first-class functions and function literals. You could assign to a variable in th
324.
by nadaviv 14y ago
The memory leaks issues are effecting IE <= 8, which still has around 10% market share. Losing one of ten potential customers is not acceptable for most businesses. Unless you're writing server-side JavaScript, or have a specific demogr
325.
by nadaviv 14y ago
Named functions are generally fine to use (they're hoisted, but otherwise behave the same), but named function expressions (where you both give the function name, and use it as an expression) has some nasty memory leak issues on IE [1]. S
326.
by nadaviv 14y ago
It can. See the example at https://github.com/visionmedia/jade#a4
327.
by nadaviv 14y ago
Jade has template inheritance, mixins, includes and plenty of other cool stuff. If you haven't, you might want to check it out: https://github.com/visionmedia/jade
328.
by nadaviv 14y ago
It has one important downside tho - because you can't chain calls, your code ends up much less readable: It needs to be read from the inside-out, and the functions you're applying on the array are in reverse order compared to the order of e
329.
by nadaviv 14y ago
I think they do too. I used to fall-back to vanilla DOM queries sometimes when I started using jQuery, because it didn't feel quite right, and I always worried about the performance hit... but I ended up always using CSS selectors, unless
330.
by nadaviv 14y ago
Somewhat off-topic, but that Kudos thingy is pretty cool.

More ›