petar

10 ms·

61.
Vote to see the Go Circuit at OpenStack Summit 2013 in Hong Kong(blog.gocircuit.org)
2 points by petar 13y ago|0 comments
62.
True story and a riddle: Recursive joy(maymounkov.org)
1 points by petar 13y ago|0 comments
63.
Scale-free engineering(gocircuit.org)
1 points by petar 13y ago|0 comments
64.
RFC: On the edge of noise: Recommending without adding value(maymounkov.org)
1 points by petar 13y ago|0 comments
65.
The Go Circuit will be presented at Strange Loop 2013(twitter.com)
1 points by petar 13y ago|0 comments
66.
Tumblr shares for sale
2 points by petar 13y ago|0 comments
67.
Go Circuit repo: direct link(code.google.com)
2 points by petar 13y ago|0 comments
68.
The clash between concurrency and parallelism in practice(maymounkov.org)
2 points by petar 14y ago|0 comments
69.
TOFFEE for NodeJS: Templating based on CoffeeScript with slick nesting(github.com)
5 points by petar 14y ago|0 comments
70.
Ask HN: What is the purpose of having karma higher than 100?
1 points by petar 15y ago|0 comments
71.
Tame.JS: Flow-control by the makers of OkCupid.com(tamejs.org)
247 points by petar 15y ago|52 comments
72.
by petar 15y ago
The other commenter has a good answer and I will re-iterate (I'm the author): Sure you can everything the old school way. The point is that being able to replace processes with in-program constructs is both less expensive resource-wise (mem
73.
Go: Process isolation rediscovered as a programming pattern(popalg.org)
30 points by petar 15y ago|31 comments
74.
Still a substantial design problem remains with Google+(popalg.org)
6 points by petar 15y ago|1 comments
75.
Major difference: With Google+ you can discover, with Facebook you cannot(popalg.org)
13 points by petar 15y ago|2 comments
76.
Ask HN: The growing liability of URL shortening services
1 points by petar 15y ago|0 comments
77.
Quantum money(eecs-newsletter.mit.edu)
3 points by petar 15y ago|0 comments
78.
by petar 15y ago
I don't know if there's anything new about it, but I have not seen disk encryption with plausible deniability before. From my point of this, this is new. This should be (could be) an important building block of anonymizing projects like T
79.
On-the-fly disk volume encryption with plausible deniability(truecrypt.org)
3 points by petar 15y ago|4 comments
80.
Even more DropBox security issues(blog.5ttt.org)
1 points by petar 15y ago|0 comments
81.
by petar 15y ago
To this meta comment, my response is: It is true that some good ideas rise from non-academics. However, if you have an extensive view on academic literature you will also know that any idea that enters the spotlight (like Bitcoin) usually g
82.
by petar 15y ago
One attack that was discussed by an economist (in an article I saw on HN) was an attack based on inserting multiple malicious bank servers.
83.
by petar 15y ago
None of which seems to have anything to do with Bitcoin.
84.
by petar 15y ago
Oh, and, the original Bitcoin paper -- I don't believe is published in a venue that is well known (or even known).
85.
by petar 15y ago
Of course there are. The identities and "distributed part" has to do with the servers that keep record of things in Bitcoin. In fact, a few months ago an economist wrote an article (which was here on HN) that described how the protocol amon
86.
by petar 15y ago
Yes, but this is not my attitude. This is the attitude of the entire Computer Science community. That's my point. No one seems to have pointed this out before.
87.
Bitcoin: Did you ever ask yourself why ...
6 points by petar 15y ago|12 comments
88.
Dropbox: How to steal someone else's content(blog.5ttt.org)
4 points by petar 15y ago|0 comments
89.
Dropbox: The consequences of forever(blog.5ttt.org)
2 points by petar 15y ago|0 comments
90.
A review of peer-to-peer projects addressing Freedom on the Internet(blog.5ttt.org)
2 points by petar 15y ago|0 comments

More ›