skysight-inc/HackerNews huggingface dataset:
> What is also very likely is that few if any of those made a decision not to uphold their end of the bargain.

I disagree. Although I agree that it is unlikely that it was their intent from the outset, there is a threshhold at which point someone has practically decided not to do something. Once they have procrastinated on doing something for X months and know that it is only #73 on their internal priority list, they have essentially decided not to do it. It could happen, but the odds are, what, maybe 10%? If you assume that a commitment to do something is giving a 100% guarantee and a commitment to not do something is a 0% guarantee, a 10% chance is, pragmatically, a "no".

Also, part of the implied deal was that you write the review promptly. From the original blog post where Schneier made the book offer:

> Liars and Outliers has been out since late February, and while it's selling great, I'd like it to sell better. So I have a special offer for my regular readers.

I don't think he was hoping they would send in their reviews a year or two later. Those who do would have a hard time arguing that they met the spirit of the deal.

The initial blog post was almost exactly 5 months ago and the offer was closed in two days, which means that a lot of readers probably got their books at least 4 months ago. (In my experience he does ship promptly, as I have gotten a book from him before.) If he was hoping that they would write their review in a reasonable amount of time, say 8 months, and only 9% wrote a review in the first half, I highly, highly doubt that even 41% will write a review in the second half. And the majority of those who will not probably subconsciously know it by now.

Edit: To be specific, I don't think he expected 90% turnout by this date, he's just disappointed that the turnout is so low by now. It's not even 1 in 10. 4 months is a decent amount of time to review a book you agreed to review.
Yes, along with workarounds. I'm reacting to the inference that someone might wait to apply the patches because they broke the Asset Pipeline somehow.
I think it should automatically scroll slowly right and left since the loop is too quick right now (girl in front keeps standing up and down)
Years ago I wrote a toy to make Mondrian style pics using PHP+GD2 ... http://ooer.com/automondrian/ ... It just makes silly random pics. Fun.
I'm pretty sure this would be news no matter how the exchange was exploited.
http://quant.stackexchange.com/
I wasn't expecting this, but it feels good to know:

"Number of incidents in which deaths occurred: 3"

all 3 were the perpetrators rather than employees / customers. On the other hand 2 hostages being the employee's family members is disappointing. It's really sad that people really do involve the families of targets just for a bank robbery.
Anyone running commands blindly without knowing what they do deserves what they get. That goes for potentially dangerous commands or not.

Or put in a slightly nicer way - Blindly running commands is going to turn into a learning experience, don't do it on a production machine.
This is David Heinemeier Hansson
He's vaguely right that it's weird that wrapping problems are still with us, especially because it's something that programmers hit every day with both code length and email-quoting from mailing lists.
I agree, it's easier to read when you can keep your eyes at approximately the same level.

Even when reading something on paper I'll find myself actually moving the book itself further away from me as I read down the page.

This design is also harder to skim, because you need to keep moving your eyes back up as you scroll.
facepalm

I forgot a very important part of the query:

row_count = Goal.update_all "completed = true", ["player_id = ? AND completed = false", player.id]

If you update where completed = false, the rowcount will only be 1 when the update works.

(I've updated the blog post.)
Yeah... it's tea for me.

"MISS TEEEEA!"
Collapsible comment threads for HN
Anonymous petitions Whitehouse for legalizing DDoS attacks
80 columns exists for the same reason newspaper columns are about 2 inches and a novel is about 10-15 words wide---that is a width in which the human eye and brain can ready and fficiently absorb the information. Lines longer than 80 chars may be fine at times but they are generally a bad idea. Usually it's better to break the line up in some manner.
Why can't i get paid to troll? I am a great troll, some one pay me damnit!!!!
Amongst OLED and LCD displays with everything else (size, resolution, etc.) OLEDs intrinsically consume a lot more power than LCDs. Using dark themes help for OLEDs for reasons already stated here, and from what I have seen working on the display industry for several years, the power numbers quoted by OLED display manufactures often presume a dark theme when comparing power to LCDs.
This is an effect, not a functionality.
I am somewhat upset that Rails sets a drive-by session cookie when I visit a site with no intention of logging in or doing anything.
Did you build the readership organically entirely from HN? Were there other sources from which folks signed up?

Also have you considered some kind of daily edition? Or might that be considered overkill?
Ah, I see, Meteor supports Twitter OAuth natively. Well it looks like Twitter is the least invasive OAuth provider they could have chosen because "Twitter, Weibo: requestPermissions currently not supported".
There's a difference between a transaction that locks for writes and one that locks for reads. By default the reading is not locked in this (common) case.
Peer Networks and Health Innovation
Learn from 10 great social media profiles
> Which is basically the only thing C has going for it...C's focus on dangerous low-level operations has created a software ecosystem that is constantly teetering on the edge of oblivion

Wow! How would you propose giving access to low-level operations? Writing in assembly?

> but nobody is willing to put in the effort needed to get rid of C and move the programming world forward.

So, you want me to write DSP code in Python? How is that going to work?
I love this. Very smooth in Mac 10.7.5/Chrome 24.0.x. I'm sort of stunned that an annoyance with moving text has never occurred to me consciously.
It is in fact impossible to skim with this. You're very right.
Honestly... this made things confusing without improving my reading ability.

a lot of people actually like scrolling. So many people in fact, that they successfully pressured Apple to add scrolling as an alternative to pagination in iBooks.

I'm one of the people who uses that. I'm trying to be polite, but my honest reaction to this interface was, "oh god, this is awful," when I tried to use the mouse to scroll the page.
This is already standard on ereaders, nearly all (even if it's a tablet or PC app) do this. I don't like it, more than 1/3rd of the time a page turn is accompanied by a "back to last page, back to current page" as it annihilates my flow (yes, that includes dead trees).

VT100 may have something to do with this though. Straight scroll isn't optimal either. When reading long texts, I prefer to have it presented in chunks, but retain 1/8th-1/4th of the information I was already looking at in case I need to refresh where I was just now. If I can't have that, a straight scroll (bar or paper) is preferable, and if I can't have that, page to page isn't so bad either.
Robot rock band (video)
Just anecdotal but magicscroll.net is a pretty popular ebook reader. Though that might be inspite of the scrolling rather than because of it.

For everyone who doesn't like it immediately please try it for a few days if you're able. I'm working against decades of learnt behavior so I don't think you can judge it on immediate impressions.
Both ... just not at the same time. That would be like crossing the streams!
I am not convinced about the polling argument to save battery life.

Yes, IPv6 could do that, but so can IPv4. Google have already demonstrated how to detect and adapt to the NAT device's timeout. Devices can just as easily hold a TCP connection open with minimal keepalives. All that is needed is for carrier NAT devices to increase their timeouts, and Android will detect this and start using less frequent keepalive intervals. 30 seconds (as from the article) can become 30 minutes. I'm sure the other smartphone OSes can either do the same thing or already do.

No IPv6 is needed. As much as I'd like to see IPv6 adopted, specious claims do not help.
Oscar-Worthy Movies Entrepreneurs Should See
A drop shadow under the scroll boundary would be a nice way to differentiate between what's on the "bottom" page and the new content on "top."
Norway tax auditors want to open source cash registers to combat fraud
Given that this is a Remote Code Execution vulnerability I'd be very careful about the "not breached" as well. For all we know, the attacker could still have a shell or a rootkit on the server.
That would suggest that additionally publicity would help. So I suppose convenient features to "share this" or "post this to twitter" might help growth. But it;s already an email (super easy to forward), and that wouldn't add value to the original recipient.
Right, but that involves changing your database and adding hidden form fields to your app in order for it to work on a multi process environment (like every production server should be.)

My solution is basically the same amount of lines, requires no such changes.
This thing is just cool.

And the music strange.

And the actor really bizarre... In fact I wonder why Japanese acting in general is so much... acted.
This argument seems to beg the question (in the actual meaning of that phrase), at least w.r.t Uber and AirBNB. All the problems they've had have come from the regulatory authorities, except for those one or two bad incidents on AirBNB which are pretty much unavoidable in a business like that. So is the argument that regulation is good because it's hard to cope with the regulators?

I just don't buy into the abrogation of common sense argument for regulation. If you let random people stay at your apartment, there's a chance they'll destroy it. If you're really worried about that then buy renter's insurance or don't sublet your place! If you give your bitcoins to some random website, there's a chance it'll get hacked! It's not like those people didn't have option of putting their money someplace more secure, like a bank.

I think regulation in general is really important for making our society a decent place to live, but when it makes reasonable activities effectively illegal that is generally a sign that it has passed that point and started making things worse.
Used to be coffee, but now i am experimenting with green tea, i have found that it provides a milder effect but more lasting and it doesn't have the crash associated with coffee.
Very well-written. I've had this idea for a long time, but I couldn't really put it into words [1] like Joel has.

I've always been known to set unreasonably high goals. If I fail these goals, I find that I still make substantial progress - essentially tricking myself. I usually joke with my friends "Aim for a 120 on this test. If you end up with a 100 that'll be okay." But in reality, I aim too high when it comes to personal projects. Make this, make that, make these things over the weekend. I never fully succeed, but I come out with something cool regardless, and usually a lesson.

[1]: http://jscal.es/2012/10/12/you-oughta-be-ashamed/
Cartoon about Stupid Business Meetings
Does the MOOC appeal to you?
news, not town's fair adverts
I sort of really like this.

I want a progress bar at the bottom, with filled and unfilled segments. (Or for that to be an option.) I'd like the 'transition ruler bar thing' to be bigger, maybe a 3 pixel feathering would be enough. And it'd be nice if I could have some customisation over speed. It was very fast, which is good, but I think I want some kind of acceleration style movement in there?

Somehow I got stuck at 99.99%, which is going to be frustrating for some people!

Anyway, it's neat.
Perhaps moving text is not an annoyance? I have never been annoyed by an annoyance that never occurs.
Perhaps I'm being nieve but it seems like very bad coding when front end exploits can lead to cash being stolen. I would expect the bare minimum of a message bus or some other separation between back end payment components and the public facing boxes.
If they don't want to be accused of MitM, the onus is on them to spell it out as to why Nokia's "browser" isn't as safe as a normal browser.
This has everything to do with regulating bit coins and the exchanges. No bank in the US would ever dare run a stock rails site, I would bet they would be rightfully sued. On top of that, funds in a bank are insured to a point so if someone at a bank messes up, the innocent people who lost their money won't lose everything they own. The free market is cruel and so are it's proponents, we've advanced past this "fuck you I've got mine" mentality as a species. If bit coin was regulated like a bank, this wouldn't be a problem. Since anti-regulation people fail to grasp this point, let me add that I do not support every bit of regulation ever passed. There is good regulation and bad regulation. Only intellectually childish people view it as ALL good or ALL bad.
Basically all the comments points to how amateurish that exchange was run compared to a real online banking website.

Now how many real banks do run their website using Rails? Ruby?

You guys certainly aren't as stupid as to believe this is the latest major 0-day Rails exploit to create havoc right?

And now comes the answers containing the logical fallacy: "All languages/frameworks have security issues". Which is rubbish in that it would imply that all the languages/frameworks do offer exactly the same level of security...
I'm building a new site from scratch soon, and was considering what language, and decided against RoR because of this. Perhaps not rationally, but it's been 5 years since I last did RoR, and I know there's a lot I don't know that's changed in that time. So better to stick with devils I know.
His argument about size is undermined by the fact files are compressed before going across a network. Blocks of spaces can easily be condensed into a single character.
Do you hate it because its bad, or do you hate it because it's different?
Only one person in the comments mentioned getting the book in late November. The offer closed on Aug. 18, and I've gotten a book from him before that was mailed promptly. That one person may be an outliar.
I believe at one point he said he got a lot of subscribers from a cross-promotion with the Now I Know newsletter (http://nowiknow.com/). I'm not sure if he has done this with other newsletters.

For daily content, I recommend http://dailyhn.com/. It provides a list of top daily stories with automatically-generated digests. The digests are of decent quality, but I just use it as a daily top ten list.
> tabs reduce storage, bandwidth, and I/O, three items that are important over weak links like 3G and on embedded devices with limited capacity and speed like my mobile phone.

Between minifying your css and js, and gzip compression, I doubt that tabs save you a significant amount of bandwidth when you're on your phone.

And how often are you working on code where using tabs instead of spaces seriously impacts your storage and I/O?
So it's basically incremental paging with a lot more work.
I ran down the street real quick in Google Maps, it's 2140 Great Highway: http://goo.gl/maps/NZNAO
The tabs vs. spaces debate makes me very sad. I get it, big companies use spaces because interns are stupid and don't understand how tabs work. And some people monomaniacally want their code to look exactly the same everywhere.

But I wish it could just be acknowledged somewhere that, if you know what you're doing, tabs are better and have no downsides (except that you can't control how other people see your code).

Caveat: I really mean tabs + spaces for complicated formatting beyond the indent level of the current line.

Regarding 80 character width, I'm often coding on my laptop and I really appreciate it when code is kept within those bounds as it allows me to vertically tile 3 files without line-breaks. Also, I find that it forces me to write more succinctly. 'One idea per line' is a good idea and 80 characters is a good arbitrary limitation that helps me achieve that.
A lot of negativity in the comments. I for one really like this. No loss of focus when scrolling and no flicker from clicking 'next page'. Great idea.
Last time I checked Zynga was still spending money on acquiring users that belong to Facebook, on Facebook.
On the flip side I actually liked it. I'm a FF user, and in the instant it clicked my first thought was "damn, I need chrome."

Options aren't a bad thing. Android offers multiple keyboards for people who find one method of typing more efficient/comfortable than others. I don't see any downsides to it because everyone gets what they want without forcing anyone to conform to a model they don't like.
Needs bigger margin or indication of what the 'last' page was. When it's scrolling down my eyes want to read that line and immediately jump to the middle of the last page, as that is where the line is. Make the last page darker or something.

You also have no idea how long-winded an article is and if you need to tldr;
Critique this iPhone game: What it Takes
I've just released my first game on the App Store. I'd never written a line of obj-c 6 months ago but I believe I have produced a fast, lean and polished iOS game (and backend web services to support it).

In What it Takes, players compete by earning points for forming words, reaching numerical targets, and solving 7 letter anagrams. To earn maximum points in the word rounds, a player should utilise the word and letter multipliers effectively to produce big scores. The number round scoring system is tiered, so the closer a player gets to the numerical target, the more points they will earn. Earning maximum points in the anagram rounds is simple - solve the anagram faster than your opponent, and you are awarded the points!

If you like words and numbers game, download it for free and let me know. My username on WIT is djskinner.

https://itunes.apple.com/us/app/what-it-takes-free/id584331176?mt=8
Best to discover the joys of concurrency while writing a game than a bank. =) Welcome! Our playground is a lot of fun!
That is an absolutely terrible lesson to draw from this episode.

First and most importantly, Airbnb and Uber are not disrupting industries burdened primarily by consumer safety regulations; they are disrupting industries burdened primarily by barriers to entrance that are designed to direct economic rents to politically favored actors. Huge difference.

There is no plausible 'consumer protection' story for preventing licensed livery cab drivers from picking up curb hails, whether on the iphone or otherwise. The law is there to protect the incomes of people who buy cab licences.

There is no plausible 'consumer protection' story that would explain why building codes for permanent residence are not good enough for temporary residence as well. The law is there to protect hotel operators from vacation rental competition.

So let's not compare Bitcoin with Uber and Airbnb, because they are completely different animals.

Bank security regulations, OTOH, ARE designed to protect consumers, although I'd argue that they're mostly unnecessary in practice. Legitimate banks don't get hacked because there are billions of dollars at stake for the banking institution, and their business literally depends on their ability to secure payments. The incentives are there with or without bank regulations.

Bitcoin sites, on the other hand, regularly get hacked because they are fly-by-night operations written by idiots who are probably also trying to steal from you. It's the fake-money equivalent of using www.send-monie-through-me.co.in and then being surprised when you get ripped off.

Bottom line: there is nothing wrong with regulation designed to protect consumers from actual threats. There is everything wrong with regulation designed to protect business from competition. The latter is what needs to be 'disrupted'.
> The Nokia Xpress Browser is not an HTTP web browser.

And yet there is confusion around it. The onus is on Nokia to educate their users that it isn't as secure as a HTTPS web browser.
Maybe when Facebook was still private and rising in value? I don't see where that income lies today. His salary is slightly over $1mm and $FBs value isn't shooting up anymore.
Bullshit.

Rails pushes low time to market. That is all. Its built with precisely no engineering design or quality control on top of a poorly specified rickety language in a community of hype.

However, my original generalizes the problem as a human issue which is where the real problem is:

Did they do a risk analysis on rails - no

Did they verify their architecture - no

Did they perform input/type checking - no (sorry but statically typed languages win here)

Did they act responsibly - no

Would you trust them with your cash? Probably not then.

This is the opposite of banks who have multiple layers of security to prevent all the associated risks of the business.

Would a bank run their OLTP on rails? Hell no, because they did the risk analysis above, which is my point.
There is a bug where when I scroll to the next page, all the old text from the previous page still shows. (using latest firefox on OS X)

It would be nice to use this method with some texts I want to read...but definetley not all.

Can't scan.

Probably would be really good to read an academic paper I really want to grasp a second time.

Good experiment!

Edit: (Since it said it was Chrome only...tried it with Chrome, text from previous page still shows up...)
This is really the proper way to do it.

Other people have suggested that this black box should store public/private key pairs generated from the user's password for each user on the exchange. So when a user signs up for an account on the exchange, Javascript code generates a private key from the user's password, client side. The corresponding public key is sent and stored in the offline transaction signing box. Whenever the user wants to initiate a withdrawal, the transaction signing box creates a random number that needs to the signed with the private key that corresponds to the public key it has on store. This way an attacker need to compromise a server and install an eaves dropping application that replaces new users' (or existing users changing their password) real public keys with its own. Just breaking into the server wouldn't do the attacker any good at first.
Yuk, but kudos for trying it out and I can imagine that you're not the only one who will like this.
Absolutely with you on this - any kind of pagination on the web makes me cringe.

On the other hand, I imagine that if you were someone that liked pagination, this might be pretty nice.
I think girl is perfectly acceptable in this context, but if you want to be politically correct and informal, you could use gal. My rule is use girl wherever I'd use guy/dude, and woman wherever I'd use man.

I'm not sure why "girl" is seen as derogatory, especially since I've never met a woman who minded it. This is a broad generalization, but in my experience, the only ones that seem to mind are adolescents who would prefer to be called a woman over girl because this differentiation matters to them. Women are usually secure about their adulthood, and don't feel threatened being called a girl in an informal setting. While girl technically refers to a child or an immature woman, in common slang, it has simply become the female equivalent of "guy."

Of course, "chick," "babe," etc are derogatory because they are slang meant to objectify/sexualize the woman. I don't feel the same is true of "girl."

I find it fascinating though how such a simple word can be interpreted in so many ways, and can completely change the tone of a sentence.