skysight-inc/HackerNews huggingface dataset:
OpenBazaar uses 2-of-3 multisig, meaning that the buyer doens't send funds directly to the seller but instead sends it to a Bitcoin account that is jointly controlled by three parties; the buyer, the seller, and a trusted third party called a notary. Both parties agree to the notary, and then in order for the funds to be released from the multisig, any two parties must agree on how the funds are released.

In a normal transaction, once the item ships and is received, both the buyer and seller agree to the transaction and funds are released. If there is a problem, then that third party enters the picture, and sends funds from the multisig by agreeing with either buyer or seller.
I agree. But I think then there is still some question of which funds to invest in of those available through your 401K.
I agree, the ageism implied by the OP is rather disappointing. I'm relatively young (mid-30's), but the persistent implications that anyone over 40 is technical inept is rather infuriating.

Supreme court justices are (hopefully) legal experts, not technical experts. Having younger supreme court justices doesn't change that _at all_. I don't know of many lawyers that know what an API is.
Yeah, that's what I ended up doing as well. I collected more than a few Danish friends from going to school with them, but a good portion of my friends were Norwegian, Danes that lived abroad, French, etc. The international crowd is always good fun.

Groceries wise, I'm still sort of 'there', but I live in the U.S. Just pop in for exams, I'm having difficulty finding housing. That actually might be a huge part of my dislike of the city; I'm sure if I lived near Norrebro, my experience would be a lot better. Commuting is never fun.

I guess the little things got to me though. I'm used to people generally having some degree of friendliness/politeness in public, which I found lacking in CPH. The cashiers at Netto would often not even acknowledge my presence. That was weird. Asking a random stranger for something like directions sometimes felt like you were committing a no-no. Maybe I'm just projecting, but the entire city's atmosphere felt mildly hostile/alien.
How to Be Confident in Business
This could be The Producers 2.
Wow. She sounds like an interesting woman to talk to. I am sure lot of people would love to read her biography.
<sarcasm> Very handy to have if they have to tweet or something </sarcasm>
> One can predict with high accuracy a SC Justice's vote on most cases based on the political party of the president who appointed him/her.

Having taken a number of law and judicial politics courses, I can say this has been studied and its not at all true. You can tell with some accuracy a SC Justice's vote on issues that had high political salience at the time the individual justice was appointed by the position of the appointing administration on those issues, but predicting votes by party identification fails rather drastically for most other issues. There's a few evergreen issues that have had both high political salience and fairly consistent partisan breakdown of positions over a long time (e.g., abortion, gun control), and so these issues tend to be pretty consistently predictable by party ID.

OTOH, most issues aren't like that (though issues that get lots of mainstream news coverage are disproportionately likely to be -- though even there many aren't), and issues like the particular one here (whether APIs are within the scope of copyright) haven't ever had high political salience.
The problem is the reprehensible ageism inherent in claiming older people are not capable of understanding technology. The same ageism you are implicitly supporting by "reassuring" us that young people (hence, magically tech-savvy people) will have input.
My first compiler wasn't bootstrapped in nearly that extreme fashion.

I started with an assembler, and the first version was written in M68k assembly and was very simple:

It supported pretty much function calls with no arguments, and function definitions, and inline M68k assembly and that it for the first iteration. Then I "rewrote" the compiler using those facilities, and iterated, adding support for variables, function arguments, etc.. Over time I had a relatively decent object oriented language.

One of the "fun" parts of the language was that you could use M68k registers in any expression (with some caveats about having to avoid the ones the compiler used). So you might have things like "foo := D0.w + bar" where foo and bar where regular variables, and D0.w indicated 16 bits of the D0 register.

I spent a lot of time in high-school working on it on paper during breaks (if you want to come across as a geek, spending breaks reading piles of assembly printouts works wonders), and occasionally lessons.
You believe it's essentially coincidental that Reagan was the first and only President to have the goal of ending the Soviet Union, not "containing" it? Or as I've noted elsewhere in this thread (https://news.ycombinator.com/edit?id=8577120) that the oil price fall just happened?

There were very few people at the time that considered it "inevitable". As late as 1989, that very year, Paul Samuelson, in the introductory university text on economics, still claimed that "[T]he Soviet economy is proof that, contrary to what many skeptics had earlier believed, a socialist command economy can function and thrive." The conventional wisdom of our ruling class at the time was that the Soviet Union was solid enough that Reagan's material attacks on it were folly, and therefore unjustifiably dangerous.
Git v2.2.0-rc1
I don't understand how copyright would help in this case.
Good question. It probably is not relevant. I presume it's predicated on the notion that olds are generally less tech savvy (and therefore less capable of fairly & reasonably adjudicating technology cases.)

Sarah Jeong has written thoughtfully on whether justices need be tech savvy:
http://sarahjeong.net/2014/04/23/scotus-is-bad-at-computers-...
> People, large numbers of them, actually believed (and it may have been true) that extinction-level global war was an accidental launch away.

Considering the Cuba Missile Crisis, perhaps that wasn't an entirely unreasonable expectation...

Reminds me of a fascinating (and rather depressing) alternative history of the missile crisis I read a while ago. I couldn't stop reading: http://www.alternatehistory.com/discussion/showthread.php?t=...
Website looks great and basing it on CSound is a solid choice. Some people may think of it as "old," but really CSound has 1,000s of hours on it over several decades. I'm looking forward to seeing where this goes!
Similar to this, I recently found out I could put an iframe in the Dreamhost admin panel if I put it as a TXT record for a domain. It screws up the page, but I'm not sure I can get to actually load the iframe; seems to do a half-job of sanitizing the input. I pulled up the online chat feature and told them about the problem; I don't know if they did anything yet.
> I estimate it wouldn't be even two times slower in most of the use cases.

In his "We Need Hardware Traps for Integer Overflow"[0], Regher quotes 5% to 100% overhead for languages such as JS or Racket, and that a "highly tuned" checker would likely be in the 5% range. Playing with arithmetics-heavy programs and Rust's checked_* (which are backed by LLVM's overflow intrinsics[1]) I got anywhere from 5 to 40% performance loss IIRC.

That's not a lot, but at the same time when you're competing with languages specifically not paying those 5%, a 5% hit on all computations is not going to get you much love.

Which is why Rust currently lets you do that (via num::Checked* and num::Saturating) but uses overflowing default semantics.

[0] http://blog.regehr.org/archives/1154

[1] http://llvm.org/docs/LangRef.html#arithmetic-with-overflow-i...
If they ever release an API and push for adoption outside of *.gov.uk, this will be a catastrophe. Banks and other services will inevitably adopt it. If they do, then the Government will have one click access to all of those accounts. Federated login is single point of failure on a scale paralleled only by email password resets (but worse, since password resets can't go unnoticed by the user).
Of course, choosing stocks/index funds/mutual funds/hedge funds/asset allocation/tilt/tax-minimization/etc all only come into play after everything else is in order.

I refer most people who ask to Dilbert's 9-Point Plan, which Scott Adams originally published in 2002 but has been reproduced many times all over the Internet eg

https://retirementplans.vanguard.com/VGApp/pe/PubVgiNews?Art...

If you can't click through, here's the list:

Everything you need to know about financial planning

1. Make a will.

2. Pay off your credit cards.

3. Get term life insurance if you have a family to support.

4. Fund your 401(k) to the maximum.

5. Fund your IRA to the maximum.

6. Buy a house if you want to live in a house and you can afford it.

7. Put six months’ expenses in a money market fund.

8. Take whatever money is left over and invest 70% in a stock index fund and 30% in a bond fund through any discount broker and never touch it until retirement.

9. If any of this confuses you, or you have something special going on (retirement, college planning, tax issues) hire a fee-based financial planner, not one who charges a percentage of your portfolio.

"What to invest in" is only answered in #8, which you shouldn't even think about until you've worked through the previous 7 steps. Yes, write that damn will already!
Good luck but please change the default font. Is this based on the actual reddit source code?
> I always wondered why they didn't just play Diplomacy[0] instead, but play for real countries instead of the imaginary ones in the boardgame. They still get to do all the scheming, backstabbing and other diplomatic shenanigans that politicians seem to love but without the loss of life and destruction.

The reason is, of course, the metagame. The first one to drop a real H-bomb on the other or launch a real assault would win, hence both sides need to play at the least simulated level available.

Also, you have just reminded me of ST:TOS episode "A Taste of Armageddon", where two planets fought a virtual war in which computers simulated the mutual bombing and after such fire exchange a computed number of people were euthanized.
To give an example, with CM you can choose to build ad hoc reports with either a full data set or a sampled data set. GA will sample data and give you an accuracy rating, but inaccuracies can grow from this depending on how you use the reports (e.g. comparing multiple metrics over a long time period). I have no idea if the premium version of GA gives you access to full data sets but that's even more expensive than CM.
Using Tor isn't required.
Professional artist whose work is very much about color here.

2. It's better to pick a single color to use to darken everything when shading; this gives a more unified feeling. Usually the best way to do this digitally is what most art programs call the "multiply" transparency mode, which I believe is simply r1xr2, g1xg2, b1xb2.

4. If you are designing for paper printing then work in the CMYK color gamut from the start. You will save yourself tons of headaches. That said modern high-end printers DO have a wider gamut than older ones, if you're going to be doing professional reproduction then talk to the people doing the printing and get color profiles.

5. Personally I do almost ALL my color choosing in HSV, it's a much better match for the way humans think about color than any other I've used. Hue: the color. Red orange yellow green purple. Saturation: how greyed out the color is. Pink is a low-saturation red, brown is a low-sat orange. Value: how dark it is. Poppy red vs. brick red. (HSV is also known as HLS, hue luminance saturation. IIRC there is a slight difference to this model, mathematically, but in practice it is much the same.)

The human eye is MUCH more drawn to contrasts in value than in hue. Two colors with the same value but different hues will vibrate uncomfortably when placed against each other. You can check for this by going to greyscale (in art programs, create a layer at the top of the stack, fill it with white or black, and set it to saturation mode); if two colors become the same grey then change one of them.
Why?

His point is to illustrate the depths of depravity to which cold-war weapons designers were allowed to dive. What is yours?
Maybe cparser: https://github.com/MatzeB/cparser
I'm not totally sure how that's different than what happens now. Is any company swelling their employee ranks with janitors?

The reason programmers command a higher salary than janitors in the US is due to labor demand; programmers can leverage that to their advantage. If I understand the article correctly, there's no need to do so in Japan because what programmers would leverage demand for (better social status/quality of life) is simply given to them.

It's also worth saying that salary aside, programmer is a better job than janitor for most people because it's more stimulating and rewarding. So it's not like you'll have a bunch of potential programmers deciding they can make almost as much money as a janitor and thus forego education, etc. In fact, isolated, it's likely to keep out people who are only into programming for the money, although in Japan the increased social status/quality of life replaces the salary incentive so it probably doesn't work there.

I also disagree with your implication that this system is economically infeasible. It's been working for decades (millennia?), and has built Japan into a world economic power. I'm not saying it's been without negatives, but I would argue that no labor system is.
The ability to link to questions and share them via social media would help.

Overall, the UI is clean an intuitive - nice job!
Looks like Source Code Pro http://adobe-fonts.github.io/source-code-pro/
> Perhaps this is why the have "invested" in Go.

I'm not sure how widely Go is being chosen (over say Java) for new projects inside Google. Maybe some Googler could clue us in?

> btw, Common Lisp is a "strong typed" language,

Can you point me to a code example? The ones I did find didn't have any type information in them.

> A lot of banking software has been written in 4GL and stored procedures (SQL). When Oracle stuffed its products with Java it was not necessarily an improvement, rather things became more difficult and messy than before.

Banking was just an example, and I'm sure they are plenty horror stories there involving Java (esp. when used in some awkward way).
What I wanted to say is that IMO the effort to build and maintain large code base in for example Python would typically be much greater than in Java. For small code bases, I'm not sure who wins - the development phase will obviously be faster in Python (which is the only thing that matters for startups - hence python/ruby/... popularity here), but maintenance will still be a pain - after the initial devs leave, hires will need to learn that Python codebase, and lack of type information will make it harder.
Well, the way I see it has nothing to do with levels of abstractions or flexibility, but everything with reducing amount of brain power required to understand the program. Sometimes abstractions do help, other times they add unnecessary complexities and reduce people's brain power to understand the rest of the code and therefore make mistakes in it. This is all about psychology.

Sorry, if I was rude, I'm just tired of pseudo-scientific language designs.
> And people make mistakes independent of language features

Unless language features prevent the existence of these bugs. Javascript will blindly let you concatenate a number and a string, Go will not. Therefore you can't make the mistake of unknowingly concatenating a number and a string in Go. Thanks to a language feature.

Iterators prevent indexing mistakes (off-by-one errors, index overflow or overflow, wrong-variable use), therefore iterators can indeed reduce bugs.
Not so much U shaped as you say. 19 5star reviews, only 2 1star reviews and no other reviews as of right now. Kinda seems like the author had his buddies review it on amazon at this point. But this could be a good book; I didn't read Flash Boys, but if I do or did, I would want to read something like this as well.
Untouchable by police? That's a pretty big claim. What would happen if the government were to round up some computers and control 50% or more of the network?
The Next Step on a Grand Adventure
The "guys" in the above sentence include your enemies.
Always conduct business like this anonymously. Public WiFi, separate browser, pastebin, free email provider, public forum.

Give them 28 days, then pastebin it and stick on reddit.

But now you can't do a thing because they know who you are and will sue you so forget about it and stop using their products.
For those who are still interested after reading the article the information is taken from the author's book [1], which I just finished and thoroughly enjoyed/was terrified by.

[1] http://www.amazon.com/Command-Control-Damascus-Accident-Illu...
I disagree.

This is not a case where you're digging around in the weeds trying to figure out which function does what. You don't need to be a computer scientist to understand the legally-relevant concepts in a case like this. Especially at the appellate level, where you're working with high-level concepts, and where you have people with the relevant technological background submitting amicus briefs explaining the concepts. I don't think anyone on the panel read the amicus briefs in this case and simply failed to understand what an API is.[1]

The real issue in this case is that a judge, applying the copyright law, simply does not care about whether finding API's to be copyrightable hinders interoperability or cloning of software. It's simply not legally relevant. The lynchpin of copyright is originality and creativity. Are the Java API's original and creative? That's the only relevant question.[2]

[1] And I would posit that software is easier to understand for a lay-person than a complex reinsurance arrangement or financial instrument. How would Hacker News react to the proposition that we should have specialized courts to decide financial disputes, with judges required to have a minimum of 10 years experience in Wall Street?

[2] Having written internal API's for software products, I would say they definitely are! API design is hard work that requires a lot of careful thought. Making a beautiful API is as much a creative expression as writing a sonnet or a short story, and is no less deserving of copyright protection.
Because the problem wasn't "ice," the problem was "cold," especially when you're dealing with finicky moving parts regarding pressure switches and tilt switches. There are tons of components of the era that were subject to thermal variance: oil-and-paper capacitors, wire coils in transformers and inductors, etc etc. We take solid-state reliability for granted these days, but there was a time before.
This is actually a very major issue. They are copyrighted to varying degrees.

The fact that feature "z" is located at "x,y" can't be copyrighted, but the data file that describes exactly that can be and is. (There are good reasons for this. It's not as simple as the straw man I set up there.)

The US is very fortunate to require all government-produced cartographic data is solidly in the public domain. This is not the case in most countries.

Now there are several public-domain global datasets, but not very long ago obtaining basic cartographic data for many parts of the world was fraught with copyright issues.

It's rather annoying to have made a map of your study area and then find out that:, "Oh, wait. You can't publish that. Our license for the river locations only allows us to use the data internally. We can't publish a figure with that data on it!"
Unicode Pile of Poo
Really watered-down, yeah. It might be more appropriate to think, "arduino with higher-resolution inputs". It's really the Arduino ADC resolution that is a major headache for us.
The Larger Implications of Electronic Payments Adoption
> You believe it's essentially coincidental that Reagan was the first and only President to have the goal of ending the Soviet Union, not "containing" it?

Coincidental with what? The actual policy change of "Reagan's" that is usually credited for destroying the Soviet Union is the escalated military buildup -- a policy conceived and initiated late in the Carter Administration.

And the actual collapse of the Soviet Union occurred during the first Bush Administration.

In order for there to be even a coincidence, there'd have to be something for this alleged "first and only" status to be coincident with.
who said people only buy one of these?
This is really horrifying. But as you say, as long as there are people to pay for it, it will continue.

How did you get into your "cleaning" type of job?
Not any limits per se. Was just pointing out that you can't simply run perl5 straight through the perl6 vm and have it work magically.
I thought developers over the age of 35 were taken out the back and shot, how did you escape??

Just curious as I turn 35 in a couple of years...

Edit: to the person who downvoted this, it's a joke in case you didn't notice
Signed by

1. Harold Abelson.*
2. Alfred V. Aho
3. Tom Ball.*
4. John Perry Barlow
5. Brian Behlendorf
6. Richard A. Belgard
7. Jon Bentley
8. Matthew Bishop
9. Joshua Bloch
10. Dan Boneh
11. Gilad Bracha.*
12. Eric Brewer.*
13. Frederick Brooks
14. Rick Cattell
15. Vinton G. Cerf.*
16. William Cook
17. Ward Cunningham
18. Mark Davis.*
19. Jeffrey Dean.*
20. L Peter Deutsch
21. David L. Dill
22. Les Earnest
23. Brendan Eich
24. Dave Farber
25. Stuart Feldman.*
26. Edward W. Felten
27. Jeremiah Flerchinger
28. Martin Fowler
29. Neal Gafter
30. John Gage
31. Allan Gottlieb
32. Miguel de Icaza
33. John Hennessy.*
34. Tom Jennings
35. Mitchell Kapor
36. Alan Kay
37. Brian Kernighan.*
38. David Klausner
39. Ray Kurzweil.*
40. Kin Lane
41. Ed Lazowska
42. Doug Lea
43. Sheng Liang
44. Barbara Liskov
45. Paul Menchini
46. James H. Morris
47. Peter Norvig.*
48. Martin Odersky
49. Tim Paterson
50. David Patterson.*
51. Alex Payne
52. Tim Peierls
53. Simon Phipps
54. Bill Pugh
55. Larry Roberts
56. Guido van Rossum
57. Avi Rubin
58. Bruce Schneier
59. Curtis Schroeder
60. Barbara Simons
61. Dave Snigier
62. Alfred Z. Spector.*
63. Bjarne Stroustrup
64. Gerald Jay Sussman
65. Brad Templeton
66. Ken Thompson.*
67. Michael Tiemann
68. Andrew Tridgell
69. Josh Triplett
70. Jeff Ullman.*
71. John Villasenor
72. Jan Vitek
73. Phillip Wadler
74. James H. “Jim” Waldo
75. Dan Wallach
76. Peter Weinberger.*
77. Frank Yellin.*

Asterisk:

"presently Google employees, consultants, and/or
directors. Those amici are signing this brief as individual
computer scientists whose work in the field long preceded
their affiliation with Google. They are not signing this
brief on behalf of Google or at Google's request."
> Expandables 3 bombed in theatres after a high-definition version was posted on sites that traffic in pirated films.

The movie quality is never to blame, of course. When Gigli flopped, it was because the horrible audience texted to warn their friends after seeing the first showing[0]

If the courts were courts of facts, inference and justice, I would have expected the court to demand statistically significant proof that leaks cause a disaster. That would require showing that more leaked movie did bad than non-leaked movies did well. But the courts seem to rarely care about statistical plausibility in these issues.

[0] http://news-beta.slashdot.org/story/03/08/19/1918243/movie-i...
Just notice that the homepage from googlecode is much more "words" per square than from github.