skysight-inc/HackerNews huggingface dataset:
A touch of hyperbole perhaps? Losing control of your online identity is bad, but it's not HIV bad.
Because if you speak FIX you can trade most of the electronically-tradable instruments in the world. There's no other protocol like that. The only credible effort I've seen to change this is http://blinkprotocol.org/ but that was only born a few months ago, so we can't say FIX will be obsolete anytime soon.
I'm interested to see where this can go, if there's a market of some scale for a paper product for this niche. What do you think?
This would be improved by a recognition that security involves trade offs, particular when you have existing apps in production that you don't want to break compatibility with. That isn't a laughable consideration: "A security problem in customer's code? Fire them as a customer!" Would indeed be effective at reducing their exposure but is not in their interests and has certain drawbacks with regards to one's odds of remaining employed as a security professional. Many apps - probably most apps - are not under active development, because the customer believes them to work. Sudden breaking API changes are bad news for them, possibly irreversibly bad news if e.g. the original developer can't be located to fix the problem.

A more sensible resolution to this issue, as a hypotherical security professional at an API company, would be moving more of the burden for security onto the company rather than the API consumer, by e.g. limiting the downside risk of a credentials compromise. (Similar to how banks don't say "The bad guys got your password? Sucks to be you, your balance is now $0", one would be well-advised to eventually have something on the roadmap to e.g. disallow unauthorized or poorly considered code from causing business catastrophe prior to getting a human in the loop.). You'd also want to e.g. make sure your sample code is secure of of the box, and write your first-party libraries to "just work" to the maximum extent possible, such that greenfield development would tend to be secured by default.

That's being pretty generic, but it's my understanding that many API companies actually do put quite of bit of work into internal anti-abuse tooling, for this and related reasons.
I agree, things like Oauth are also massively overkill for what should be simple jobs. The other day I was writing a script for my own personal use that needed to get some metadata from Imgur. Their API /requires/ OAuth, when even a json snippet for a public picture would have been just fine. Ended up just scraping the page as it was a one off script and was much faster than signing up, creating an application, implementing a library, etc.
I wonder if there's some economic equivalent to the second law of thermodynamics. If entropy is always increasing, perhaps the environmental costs of a system can never be non-positive. Entropy can only increase. I haven't fully thought it through but it's an intriguing idea.
It's crowd-sourced from actual people using a browser extension.

http://tldr.io/what-is-tldr

(see how I gave you a tl;dr of the link explaining how the tl;dr is generated?)
This is an API endpoint, not a web application.
Super Nintendo Emulator build in Flash
Free Raspberry Pi co-location in Sweden
Swedish citizens are offered free- yes, free- co-location of a Raspberry Pi in fsdata's datacenter in Helsingborg, Sweden. 1Mbit/s, 100GB/month, 0.00 SEK per month.
If you aren't a Swedish citizen, ask your facebook friends to co-locate the server for you.
Don't miss out.
Can you detail some of the criticism please? I understand what he's doing and it makes sense to me - and I too believe those blocks identified probably belongs to Satoshi or someone very close to them.
I was playing about with Fiddler with some mobile apps on my iPhone a while ago and noticed one app was using HTTP basic auth with HTTPS but the application was ignoring SSL errors (I was using a self signed cert on my PC to perform MITM and decrypt HTTPS traffic). This is almost as bad as using HTTP and basic auth because you're basically ignoring the fact that the certificate should not be trusted (at least give the user a choice?). You would be surprised to see how many apps ignore SSL errors and allow you to use any old self signed cert.
In a small startup there's not always room for middle-management - we report directly to the CEO
My thoughts exactly. But if there is no systematic or other error in her research and there are health-impacts for humans, too then we better get up to snuff and look for a solution to make our food healthier. Also even conventional farming is still somewhat inefficient. Vertical, largely automated farming could do much to lessen the footprint agriculture currently has on our landscapes and ecology.
Amen, I'd like to push the blame on the fact that we still even have to deal with passwords and stuff in this day and age, but that's hardly putting a better suggestion forward :(
While if you are just implementing Key/Token auth for an API, Digest might be `good enough` but does not escape the problems associated with Digest, such as its reliance on MD5 (broken, if your token is complex and longer than 32 chars it renders it less secure) and the requirement to store tokens in plain-text[1].

If you are implementing username/password, then Digest removes the ability to use a secure password system like Bcrypt or PBKDF2, which is a killer.

[1] You are able to store the digested tokens/passwords rather than plain-text, but if you need to protect the token/password in any way, the digest is an insecure way to do so.
Trillions? I think you're being just a little over optimistic about the future of bitcoin here.
Yes and no. That is true, but it's also possible, with white-collar work, for people to be fired "for performance" for pretty much any reason. That's the danger when you work on stuff where performance is pretty much impossible to define or measure.

You have the legal right to disclose pay (except in a job with a security clearance) but most companies will isolate you, then make sure you get the worst work with impossible deadlines, document everything, ruin your reputation internally (though performance reviews that follow you if you try to transfer) and finally subject you to whatever passive-firing system they have around.

I'm not saying that it's bad to discuss salary. You should figure out if you're getting a fair deal. But you do not want your employer to catch you disclosing salary. It will end badly.
But for software developers at least, I've seen no correlation (or perhaps even a slight negative correlation) between technical and negotiation ability. So that no-talent clown may actually earn more than you. In the end, many good, underpaid developers leave, because that's how they have a chance to get a fair valuation in the open market.
Isn't this sort of issue basically only going to happen during development or such?
Controlling all of home automation with a Raspberry Pi.
The article didn't say, does this site have any intelligence? A modern porn site would be like Netflix, i.e. it will slowly "learn" what (sub)genres you like, whether you like blondes, brunettes, etc. and it will automatically suggest videos to you.
Cool. Compare with http://www.edis.at/de/server/colocation/oesterreich/raspberr...
http://en.wikipedia.org/wiki/E-gold

Bear in mind that these court cases were taking place as the Bitcoin protocol and client were likely being developed (2007 and 2008).
It depends. Look at DongleGate...
Went to sign up for a 'developer account'.

My password:
udxeik8SovTCW0qhlPMr00dBBWTW6zeAbDQ77PLIOcidhXZsEhg7yP10B4ygqkzU

Rejected with:
- Password must contain at least 1 special character
- Password must not be longer than 15 character(s)

So...
?Gc76+;%ap``h}(
- Invalid Character(s) in Password

Less 'special'? ...
%_H$Jo#];:=?RK&
- Password must contain at least 1 numeric character

Here you go then:
8-8jvr£B9#UQ4Q/
- Invalid Character(s) in Password

Gah. I know just know if I sign up for this, in a few months there'll be an announcement about how they've had their account details 'stolen' by 'hackers'. Not that they're incompetent or anything.
I think the most important thing to know about Millennials is that we're the exact opposite of the smear thrown at us. Boomers call us "entitled" at work. We're actually disentitled.

An entitled person expects a social contract to be upheld, and usually the pejorative aspect of the word "entitled" implies that it's one-sided advocacy.

We're disentitled because we no longer believe in the corporate social contract at all. We'd be entitled if we expected the other side to follow the rules. We don't. We know they won't, so we break just as many rules. Sure, it's bad for social harmony to people to figure out if they're getting screwed. You know what? Fuck that! I find it worse that people are getting screwed.
Paper is not going anywhere - people like it. Probably in the future it will be exclusive product. Niche is good. I like this kind of products. This idea reminds me about http://qqnotes.com/ (unfortunately it's only in polish).
As I implied in the comment you're replying to, yours is a terrible idea ;)

I advocate transparency and simplicity not because it's a perfect system for getting the exact amount of compensation appropriate (no such system exists) - I advocate its use over the alternative which is based on empowering the employer only and unfairly rewards people for being good at negotiation. I allege the whole thing is a philosophical artifact created by the idea that unregulated free markets can solve every problem: "just let the workers fight over it, the best will get the most!"

Interestingly, a wide variation is skill is not something that is addressed at all by this don't-ask-don't-tell lottery scheme. If anything, it is based on the idea that two given people with the same skill set end up getting disparately compensated. In what world can that look right to anyone? People wonder why women and minorities get paid less than white males: that is the reason why right there.

The truth is, I'd rather rest well knowing I get the same compensation as a coworker than spending energy wondering whether I'm getting ripped off or not. And here's the shocker: I don't want my coworker to get ripped off either! Now if a team member happens to be awful, and he keeps on failing upwards through the ranks of the company, I prefer to have some visible indicators for that as well. You say you prefer to make twice the salary as that guy, but under the system you're advocating you couldn't even know whether that is indeed the case.

> I (and likely you) don't want to be lumped in with whatever the "average" worker of my years experience and skillset is making.

That really depends on the company and the kind of colleagues you are dealing with. I'd prefer to work in a team where I'm not above everyone else. I like being surrounded by people who inspire me and whom I can maybe inspire in turn. Being lumped together with comparatively untalented coworkers is not just a compensation issue, it also creates an environment where one part of the team has to constantly shoulder additional workload and carry the underperformers (who by the way are almost always better at politics).

Getting back to my levels proposal: it already works elsewhere, it's just not used that much in our industry for cultural (and probably philosophical) reasons. Yes, skills vary, but the negotiation-based system addresses this in an even worse way than compensation levels do. My experience with running a level-based system has been overwhelmingly positive. It was pleasant from an administrative point of view, and it created zero contention among employees.
Smartest poem ever? Every line an anagram of the title (image)
An interview with Andy Ashburner from Caffeinehit, developer for Summly
How To: Transfer your PuTTY settings between computers
I found one UX/UI problem so far. There's no button for Guy on Guy. I can't see this appealing to the gay community ;)
Would you mind giving a little more of an overview of how you set this up? I think this would be incredibly useful.
When I first heard about how easy it was to look up a person's income in Norway, I was blown away. I'd personally hate for that information to be public. I think perhaps in Norway, there is a bit less disparity in incomes, it's a little closer to equal. The wealthy are also heavily taxed. So it makes things a little less uncomfortable when your friends, colleagues, family members, etc. know exactly how much you make.
Bashmoji - Give your shell an emoji based on the time of day (OS X).
Sometimes listening to BitCoin proponants is hilarious. They point out all the disadvantage of current money transfer systems and how BitCoin will solve them ("No chargebacks! No transaction fees! No-one can take your money!"). Then when you quiz them, they'll admit people'll probably build systems like that on top of bitcoins ("Well people'll probably use escrow services on top of bitcoin to prevent dishonest merchants, and eventually there'll be transaction fees from the miners"). It looks like they are even talking about removing the "no-one can take your money" aspect!
I see two main possibilities: (1) the paper was prepared anytime in advance and withheld until the dollar/US/world faced serious risk. (2) The BTC paper was started in the early stages of the crisis or later.

Both possibilities could suggest the BTC creators had an interest in the success of the dollar. The alternative would be that it was opportunism of BTC creators who were always against the dollar or turned on it in the crisis. I happen to think that if you were always against the dollar you would just release bitcoin immediately and hope for the most disruption. I'd think that someone supportive of the dollar would be more apt to release it strategically as a contingency.

In my mind that means that dollar supporters are the better chance of being behind bitcoin because they could have made it any time in the past or as the crisis progressed, whereas dollar opponents only had the time of the crisis to make it.

Assuming that, I think then the US has an above-average chance of being the authors of bitcoin.
Say, for example, you and Steve have the same job description and Steve tells you that he makes $40k more than you. You naturally feel screwed, so you go talk to the boss about it. Now, one of two things might happen. It might turn out that you're actually as good as Steve, and just weren't as good at negotiating. That's the best case, and maybe you'll get yourself the raise that everybody always talks about when this topic comes up.

But more likely, you're just not as good at your job as Steve.

If Steve is a better engineer than I am, then I'll be more likely to know that than most managers. Now, software is structurally cooperative so I am just not going to raise a stink if a superior engineer makes $40k more, because he's worth it. If he's genuinely better than I am, then my attitude is, "damn right he deserves to be better paid; look at how much I learn from him every day!"

I'm not one to make waves over differences in salary. I have too much other shit that I automatically raise hell over (unfairness in project allocation, unfair review policies). I tend to let salary flamewars go. Gotta pick your battles.

And now your boss has no choice but tell you so directly. So now you feel even worse, your boss is uncomfortable, and Steve is all self-conscious.

If he's a good boss, in that circumstance, he'd tell me what I need to do to be in Steve's position in 2 years. If he's going to pay Steve $40k more because he has more immediate-term value, then fine. If I want the boss to invest in my career so I can be a Steve in two years, and he's not willing to do that, then we have to break.
It's the stated hope of some in the bitcoin community that bitcoin become one of the top 3 currencies in the world.
First, you have no idea of the earnings of the "clown" because that information is not disclosed or offered. Then you are assuming you make twice his salary. Then you are attacking suggestions that you could check if this were true as a "terrible idea".

The whole issue is you have no way of knowing if the "clown" is making double your salary or not. This can breed resentment of individuals, just as knowing peoples salaries can. People are complex beasts. For my limited experience, in all likelihood banning talk of salary or not probably has very little effect.
Big Tobacco in the USA is of course a shining example of the West's greater moral values /sarcasm
Fantastic, thank you. Are these legit/official?
I still use a Moleskine from time to time, but mostly the iPad, to take notes - especially when doing customer interviews. Yeah, I agree. Starting niche is a good thing. The question is if you want to stay niche or if there's growth potential to other niches and out of niche-dom. [edited for typo]
Startups scout elite programmers for Silicon Valley companies
If you can program, and you're under 40, it's easy to get "a job". Getting good jobs is harder.
Twitter To Show You Ads Based On What You Tweet
Why the hell would you over complicate your API with things like s3 auth or other bs like oauth?

HTTP Basic Auth works pretty well with SSL and should be enough for most cases. Also, it's dead simple for the API to return a token that can be used after authentication in non-SSL endpoints of the API.
Not necessarily. If the connection would be unmanaged, as having the power available for drainage all the time, then you're right! ...but we have computers and all kind of complex systems now. The cable may be "empty" of that high voltage current until the cable is safely plugged in and ready. After plugging, before unleashing energy, the car's system and the power source's system may first communicate and verify their sensors if everything's ready to go, like isolation and other things. The high voltage risk and its management it's an engineering solvable problem.
I don't think it's realistic to expect that to happen any time soon.
So I thought I'd test it out a little more. Pretended I'd forgotten my password. Pressed the link and it said 'Password emailed'.

Turns out it's not as bad as that! I wasn't emailed my password. I was emailed a link.

http://appcenter.html5tools-software.intel.com/csd/ForgotPas...

That's fine. So there's this unique token that means only I can reset my password... Except... Let me decode that token...

EYl0htUzhivYzcIo+zrIyEFQUE1PQkk= -> t3+(:APPMOBI

So does this mean I could reset anyone's password, given their email address?

Anyway I went to the page and put a new password in (trying to follow the unstated rules found previously). When I pressed submit, the page darkened and I was told 'Error 500'.

Tried again with a new password and was told 'Password must contain one of the following !@#$% special character[s].[sic]

Well, I was told it for a second, but the message went away really quickly, so I had to keep submitting the password it didn't like until I'd remembered what the characters it required were.

Anyway the password reset link doesn't appear to expire, so if you fancy logging in to Intel AppCenter as me, just reset my password. I can always reset it back if I want to use it.
While the differences skill levels are true, I don't think "you are just not as good as Steve" is the usual case for salary differences.

Salaries tend to stay mostly fixed while in employment at a single company, raises over 10% are rare. As a result, salary is much more related to your negotiation and self-marketing skills at the time of the interview - when the new employer has very little hard evidence of your developer skills - than any objective measure. You might in fact be much better than Steve, but may have changed jobs less often, or have worked on less marketable past projects.

For example, I've never heard of anyone negotiating upwards based on relative skills, as in "Bob is making X, I'm 3 times better, therefore my salary should be 3X".
Is there no way to make a sale like that today?

Correct.

There are not enough people who want to buy bitcoins. If those 1M bitcoin were put on the market, the price would plummet.
Google has some guidelines to be able to search dynamic (js) content too. Plus, the bot (which is some headlines webkit, I've read) also runs javascript before it reads the page.

Now, that's for Google, but anyway, ATM, I think, Google is the only search engine that matters.
Smart, Well Dressed, Presentable, Straight Arrow, Tin Foil Hat Movement.

Think Richard Stallman but with more tinfoil, better dressed, and little problem working with proprietary systems. Refuses to use any tracking devices (think RFID).
That's dumb. As dumb as saying that the cause of death is the dashboard your head bumps onto. Or that the cause of death is being alive.

If you can't tell the difference between cause and condition, you may keep silent. No one is forcing you to participate in the discussion.
They were doing a subtle PSA - put plastic pipes in the house.
This is indeed very nice.
Yes, more like that.

I mean if you ignore the other 99% of TFA.
Maybe Satoshi Nakamoto died before bitcoins got popular ...
"If you paid more this would not happen"
By my reading, the spec is not that clear about it. It does say that

A user agent that wishes to authenticate itself with an origin server--usually, but not necessarily, after receiving a 401 (Unauthorized) --

implying, imo, that no prior 401 response is needed. On the other hand, the spec also says

A client SHOULD assume that all paths at or deeper than the depth of the last symbolic element in the path field of the Request-URI also are within the protection space specified by the Basic realm value of the current challenge. A client MAY preemptively send the corresponding Authorization header with requests for resources in that space without receipt of another challenge from the server.

which would imply that at least one 401 response should be received before sending credentials.

Of course the most important part of the spec is this:

The Basic authentication scheme is not a secure method of user authentication, nor does it in any way protect the entity, which is transmitted in cleartext across the physical network used as the carrier.
Warn your users when their network goes down.Make sure they don't lose anything.
>These lists can be very locale insensitive.

Perhaps because english is all it matters to them. Who in Europe, for example, even cares if a forum or chat has some swear words in his language?

We might be even more pissed off that we can't swear and leave the service, rather than complain about it.
Here in The Netherlands we have a similar initative by hosting company PCextreme: http://raspberrypicolocatie.nl/. 100 Mbit uplink and 500Gb data, not too shabby!
Does it work with Cygwin?
Actually, I think part of being a good leader is not ordering people around, but inspiring, guiding, and teaching them.

I don't mind taking direction, but traditional management turns me off.
Or I could use Ctrl-r.
As developers, we tend to look for technical solutions to things, so when we see a situation like the one you describe, we come up with ideas to "fix" the situation and make everything fair.

But a more productive approach when confronted with the fact that "negotiation skill seems to have more bearing on how much I can make than technical skill" might be to just take advantage of that fact. If tech folk are as generally bad at negotiating as everybody here seems to agree, the best course would seem to be to simply get better at negotiating.

That's actually quite easy to do. And if you do so, you'll make a lot more money.

That's a good thing.
Debian base for first Pardus Linux Community Edition
How to create chocolate out of nothing
Thats does not sound like the whole truth. I would guess that Java long ago lost its sexiness - now everybody and everything uses Java. The other problem is that now there is vast amount of legacy code. By choosing Scala you are actually eliminating that from the equation.
Curse of the crystal skulls and other vanishing area puzzles
Many of these are small privately owned companies, I'm not sure how quarterly 'accounting' has an effect on that.