skysight-inc/HackerNews huggingface dataset:
>If that's accurate, it's much harder to see how Dorian Nakamoto thought they were talking about his old military contracts.

How so? That's how projects work. It seems like a pretty reasonable response for someone who is trying to avoid breaking a confidentiality agreement.
I think we're all stuck with using the inbox as a place for todo/tasks. But it isn't as gloomy as it sounds. The real power of email lies in it's ability to push/pull tasks seamlessly. All you need is an email address. I think I've found a solution that does this very well :)
I'd encourage you to A/B test a text-only newsletter versus an HTML one. Or even just ask people which they prefer. I think you're in the minority.
It's the same in the US, the person you're replying to simply needs to consult a dictionary.
Cool idea.

Not sure how it works now but shouldn't Apple/Google just disable that delay if your viewport is already set to device-width? It's not like you're going to double-tap to zoom in any further.
That's really cool. I wish I could see the game unblinded when it's over though.
The plane has a set of automatic distress signals. No pilot intervention is required for those.
"Stop Using Something Which Works Perfectly Fine For Millions Of People Because We Have Compiled A Few Obscure Alternatives You Should Use Instead"
Be A Business Leader As Well As A Thought Leader
6 months ago I was hired to build a guy a website for his wifes chain of dentists offices. I was paid 1.5k upfront and proceeded to build it out, and was a few days away from turning it over to him and receiving the final 1.5k payment. I then got a notification from PayPal that he tried to reverse the original charges.

PayPal contacts me, I show them our chain of emails, and to their credit, they actually took my side. PayPal goes after his card holder, and of course they side with him, so now my PayPal is $1500 in the red because of some fucking asshole who actually owes me $1500.

Fuck freelancing.
Yeah this keeps happening. Lipstick on a pig.
Well, I would suspect that Google makes deliberate choices on how they set up these sorts of things. They've probably built models which demonstrate that only n percent of the global population will be affected by a certain naming policy and the differences in cost associated with modifying their databases or to accommodate such names or dealing with troll accounts versus maintaining the status quo. [Keep in mind I obviously do not work at Google and clearly have no idea what I'm talking about]. I suspect that, in reality, Google feels that keeping their uses safe from all the Grass Mud Horse's and Assmen of the world doesn't affect their profitability significantly. Frankly, I would love to look into the best ways to deal with the non-universality of names for users while still being able to meaningfully harvest and utilize all of their information for those sweet sweet advertising dollars. Perhaps the best way is just give users a generic field for "name" (not first/last name) and make the good, old-fashioned username be the identifier.
> /dev/random does not deliver "new entropy"

Sorry, you're wrong. /dev/random in Linux is made to deliver the new entropy to you as the user, even if these "entropy" bits do pass through the block you marked as CSPRNG. That doesn't contradict with my claim. The fact they pass through the CSPRNG block doesn't change the fact that the system makes its own best attempt to collect the actual entropy and pass it to you as the user. That's also the reson why it blocks until it has collected as much new bits as you requested -- it does its best to not lie to you. These bits are not the "continuous CSPRNG stream" they are just the nicely polished entropy bits.

Think about this this way: some system stream can be made that would deliver the unprocessed "source" entropy bits. But such bits would have to be additionally reprocessed (in effect, passed through something like CSPRNG or whatever, there are enough papers written about that) to be useful in any sensible way. Even very random natural processes (e.g. radioactive decay) can't be used in their pure form for cryptographic purposes. So the kernel does that additional processing for you. That's all. They are still entropy bits, only additionally shuffled with the "encryption" code to actually improve their characteristics for the cryptographic purposes.

Now you may claim that the claimed entropy doesn't exist in the case that estimator estimates wrong, but it's still the best attempt there is. Accepting imperfections of the real world, /dev/random in Linux is there to give you the quality entropy bits, based not only on some known states, but the very real "entropy" bits not discussing here how these can be collected, estimated and their characteristics improved.

The meaning of "entropy" here is loosely "the non-calculable randomness which can be observed by the functioning and the interaction of the system, not the direct calculable product of the system itself." The system running in the VM and without special inputs has much less chance to observe much of such randomness.

I am aware that, according to the claims I've read here, by not using blocking, entropy estimations or whatever, FreeBSD is not delivering the entropy once it stops blocking. But it's just the FreeBSD's difference in the contract.

In Linux, it is actually the other way around to your claim: not even /dev/random on Linux actually strives to return the new entropy, the /dev/urandom won't just return CSPRNG stream but will occasionally get the added benefit of the real random bits collected via the entropy collectors. It's just guaranteed that it won't block while again, doing its best.

The source of kernel's random.c already linked in this discussion is actually very nice and clean:

https://github.com/torvalds/linux/blob/master/drivers/char/r...

Do compare random_read vs. urandom_read.
Where is a right place to put Russian translation of this article?
Grunt YSlow, a Grunt Task to Measure and Grade Web Page Performance
I believe I've seen this article posted before, possibly on HN. In any case, I re-read it today and all the lessons in it are applicable to me - yet again. Though I've made improvements in many areas, I have also fallen deeper into some of these pitfalls.

I was once obsessed with productivity, and for me it came down to an attitude of 'just do it'. This was filtered out into various micro-level attitudes and behaviours, many of which are discussed in this article... However, I now realize that going back to University sapped me of all this yet again: I was in the world where smart guys reign supreme. This is the reason why the smart guy pitfalls exist at all: there are artificial worlds where we can somehow glide by just by being smart.

The real world is real, and it takes real work to stay on top of your shit.

Some things I used to do that I will start doing much more again:

- Write everything down
- Make todo lists
- Try to actually measure productivity (http://www.rescuetime.com)
- Be realistic and conservative with estimates of how long things can take.
--Not really knowing how long something will take should be scary.
--Do a quantifiable percent of a task, time it, extrapolate.
- Stop borrowing time (and money).
9 ways to peel a banana
wouldn't it be nice if this was built into the browsers themselves ? probably with a settings to change the timeout etc/or disable the feature ..
> You can now write &-suffix (or &_suffix, or even &suffix if you really want) and Sass will make it work.

Now you can finally use BEM in Sass without the need of verbose mixins. Good stuff!
I can just imagine the sound they made as they flew overhead.
I'd be interested in listening to that talk you mentioned if you happen to find it.
> Fuck freelancing.

Nothing wrong with freelancing. Just something wrong with the way you're doing it. Screen your clients.

> 6 months ago I was hired to build a guy a website for his wifes chain of dentists offices.

You either did the job or you didn't. If you did the job, the work is good, and they're using your work ... well, then you can nail them pretty good. Especially since they have physical assets.
Poll: What is your Myers-Briggs Type Indicator (MBTI)?
I think would be useful to understand how HNers perceive the world and make decisions.

You can do the test here: http://www.humanmetrics.com/cgi-win/jtypes2.asp

from wikipedia

http://en.wikipedia.org/wiki/Myers-Briggs_Type_Indicator

The Myers-Briggs Type Indicator (MBTI) assessment is a psychometric questionnaire designed to measure psychological preferences in how people perceive the world and make decisions

A good summary of the 16 types

http://www.myersbriggs.org/my-mbti-personality-type/mbti-basics/the-16-mbti-types.asp
Thanks! Replays will be back up eventually - DB server is tiny and having memory trouble. Can't mess with it now since it will interrupt the games.
I don't think anybody can disable communications from inside the plane (but then, that's a guess, if anybody knows better, please tell so).

It would be compatible with some group kidnapping the plane, and changing the route to go over the ocean. But the plane would have already appeared somewhere, so I don't think that's likely.

Also, if it was a bomb, it would need to be quite a big one, to completely destroy the plane. Also unlikely.
I would recommend doing more research. Read BogleHeads.Org (it's like HN for financial news). Good luck!
You mean like some sort of malicious incompetence? That's really twisting Hanlon's razor!
If you're making games for the fun of it, your advice is spot on. But it's a terrible way to make a business decision if revenue matters. It's really more of a question of whether he has good reason to believe that 70% of the revenue is enough to cover an investment in a Mac + Developer Program. I don't much like Windows, but the investment in a license for Windows and Visual Studio has been returned many times over. Nevertheless, Android is a great place to start—on any platform.
He "decided to have GoDaddy" build the site, after I built it in wordpress. They arent using it. He actually logged in to HostGator and deleted the fucking wordpress instance. (FWIW, I actually do really great work- Not like I did a shitty job- The guy is just a fucking idiot. Cant fix that.)
I like ReST as well. With Sphinx, it is great for producing documentation. A project that I work with has converted hundreds of pages of books of technical documentation over to Sphinx and a custom Sphinx extension.
Aha! Sounds like something the true inventor of bitcoin might say. Gotcha back!
With the benefit that you can do multiple takes, or splice in a jump cut when you mess something up, review and rescript the presentation etc.

That's very different to presenting in real time with just a whiteboard to write on.
Wikimedia is a Microsoft project and targets small businesses.
How did a localhost link get to the second page on HN?
Yes they should, Chrome 34 on Android already does it actually.
Yeah, for a website with 2 seconds or more load time, instantclick will probably only help remove 100-200ms. Still worth it, but not a huge improvement. There will be lower hanging fruit.

Where this library shines is if you already have a decent, fast-ish website with ~500ms load times. This can bridge that final gap and make it look like the whole site is loading in a flash. Amazing to see in practice. It's more the fact that the page layout can be computed before the page changes. it makes a huge difference in perception.
Why Bitcoin Doesn't Want a Real Satoshi Nakamoto
Notice how that article uses the term "indirect discrimination", rather than just "discrimination"? That qualifier is there because without it, most people understand "discrimination" to mean intentional prejudice.
Is it? I read it as: depending on culture, the name may be either case sensitive, or not. (alternatively - someone's name may use alphabet with no concept of "case")
>The saddest part for me in the late 90's was the influx of business majors who were going to 'show up how its done' as opposed to problem solvers and team builders.

Funny, the saddest part for me, both in the late 90s and today, are the "Tech Stars" who are living high on the hog on other people's money, with some pipe dream of getting bought out and no plan to run a real, viable, sustainable business. Their businesses implode, they get "rich" (through money and contacts) and move on to the next project.

Laugh all you want at the MBAs, but I can assure you that they, at the very least, understand that the purpose of a business is to create value for customers and generate a return for stakeholders. I think "Silicon Valley" could have used a bit more of that sort of thinking then, as perhaps more so today.
They are confirming that the quotes were accurate, which is quite different from confirming that her conclusion was accurate. Dorian Nakamoto had already confirmed that he was quoted accurately. He also said that he misunderstood her and she apparently misunderstood him, and that seems entirely possible.

Her entire story relies heavily on the confused 'admission' from Dorian Nakamoto during a few minutes interaction. She effectively ignores evidence that does not support her claim, such as the inexplicably huge difference in public writing styles of D Nakamoto and S Nakamoto.

What this new revelation does show, if you read the full reports of it, is that the reporter prompted the critical quote from the police officer, which opens her story, by first feeding him the suggestion that Dorian Nakamoto was the creator of Bitcoin.
Either some people think it's funny, or somebody's cheating.
wasn't something like this made in the early days of chromecast & they either shut it down or it broke due to a firmware update? i think it was to stream video content from your personal network to chromecast

hm...... i've been assuming that even tho there's an SDK it is still a turf war. if it's actually open to open source development... woah. many possibilities...
It seems like a reasonable response to inquiries about a specific project. It is less likely as a general response to your general involvement in military contracts.

Now ask yourself: Which specific projects had they been talking about, other than Bitcoin? If you can find one, I think your point becomes valid. If you can't, I have to side with the grandparent, at least on this aspect of the story.

Of course, alternative explanations are possible. It's possible that there is one specific military contract project that is haunting Dorian Satoshi Nakamoto so much that that sentence came out even though the reporter had never brought it up. That does feel a bit like grasping at straws to me, though.
Excactly my thought.

Most of these command-like "advice" posts here lack a real reason why I should stop doing what I do. I have the feeling the author just writes down a piece of text about some tools and than adds some gerenic reasons on top to justify the rest.
How can I kill puppies (safely)?
IPython 2.0.0 beta Released
Markdown has always looked limited and incomplete to me.

But I can't decide between ReST(+Sphinx) and AsciiDoc(+?) - ReST seems to me like it was better thought out, but somehow my AsciiDoc documents turn out looking better, even though I like ReST more.
As long as we're being pedantic...

It says the best (presumably "most effective") way to get the right answer is to post the wrong one. That doesn't mean that posting the wrong one will always work; it might be that if posting the wrong answer fails, there was no way to get the right answer, or that the successful ways would have been more effort than they were worth. (Obviously, this isn't true.)

> Another way to disprove it is not the best way. Now that they told you this "secret" next time you have a question will you post a wrong answer or find the right place and try to formulate the question as best as you can?

This doesn't disprove Cunningham's law, any more than people failing to wash their hands disproves germ theory. And even if Cunningham's law is true, posting the wrong answer in order to get the right one is rude.
I wouldn't call it satire; they are, as the title indicates, falsehoods. That is, if your code makes any of the assumptions listed, then you're handling names in a way that inevitably won't work for users of certain cultures.
That's really interesting, I'd never heard of this before. Can you give us an example you've heard of a redefinition of racism that would exclude whites from being racist?
The two are not incompatible. If your incompetence leads you to implement a policy that disproportionally disadvantages a certain group, you are also discriminating against them.

Discrimination does not require intent.
I completely agree.

I like to think of it like the ED at a hospital. Anyone can walk in the front door (send you an email), but you need a triage nurse to organize patients, figure out what each one actually needs, and prioritize them appropriately. Otherwise, you'd just be picking the patient that looks the worst (most urgent) to treat at any given moment, which is not the most effective way to treat patients (the most efficient way to conduct business).

Email is a LIFO stack (perhaps a FIFO queue for some clients), but neither of these is inherently a reasonable way to prioritize the patients who need care, or tasks you actually want to do today.
This is exactly what I needed, thanks! Does it stream the video directly, or is there transcoding? I might even be able to stream videos from my home server (which has an HTTP interface) directly!
Biola Alabi resigns as MD of M-Net Africa, now MD, Special Projects
That's the thing. I don't know if there is "a right way to do it." Maybe names are a domain that is hard enough that you can't propose the right way to handle them--you just have to know the problems that can arise, do your best for the users you expect to have, and be prepared to rework if you need to.

The problem with the google+ real names policy isn't that their algorithms aren't smart enough (though it seems that they could use some work). The problem is that they're too arrogant to recognize that their algorithms are unreliable and indifferent to the ways that this unreliability is bad for users.
Google's stupid name policy is probably their worst idea ever.

Interestingly, it's somewhat undone by one of their other bad ideas: merging Youtube and Google+ accounts. Because nobody had a real name for their Youtube account, and suddenly Google creates a bunch of Google+ accounts that nobody asked for and are obviously pseudonyms.
I've got a few strategies that might help, depending on the circumstances.

A notebook: I'll write down some notes and just kind of free write whatever thoughts come to mind. If there's something that I think is important to come back to, I'll draw an empty box in the left margin (to be filled with a check mark later)

Readme: start writing the Readme for the project, even if you're not entirely sure of the details. Include code examples. If you don't like how the API is coming together, change it. It's way less work to modify the API now than it will be later.

Write a test: I don't always unit test, but when I do I test first :). This works well on projects that already have a decent test suite. It's kind of an executable version of the Readme.

Branch and Hack: branches are cheap. Make one and start playing. Don't like how it's turning out? Make a new branch and try again!

Ctrl-Z: maybe the answer won't come to you right away. Let it sit and run in the background for a while and come back to it. If I'm worried about forgetting details, I'll write it down in a notebook first.
Whatever line-wrap/justification setting they're using is horribly, illegibly broken on mobile Safari. Some irony.
Well, at least it doesn't require an email so it's just the username and password.
As an INTJ, I know better than to take this personality stuff seriously. :D

http://www.amazon.com/The-Cult-Personality-Miseducate-Misund...
It's not satire. They are both bad assumptions, bound to be false somewhere. Don't let your code rely on either of these assumptions.
Tomorrow's Apps Will Come From the Bitcoin Protocol
Oil slicks have been spotted in the ocean. http://bigstory.ap.org/article/china-bound-malaysian-jet-van...
Welcome To Lumdy's Blog : Why Abacha Got A Centenary Award – Reuben Abati
Case sensitive and case insensitive sound like they're the only two options, but they're not.

Take SQL as an example: are programs case-sensitive or case-insensitive? Neither!
Is this something like FastClick[1]?

1. https://github.com/ftlabs/fastclick
What everyone's takeaway should be is that Newsweek professes an editorial filter and not only let through this garbage, but featured it. WWPGD? Hell-ban Newsweek seems the appropriate measure.
Somewhere, deep in Lindley Hall at Indiana University, is an old professor exclaiming, "I told them people used it!"

I wonder if I'd have taken more to Scheme if I were learning it now. At the time, I was double majoring CS and Telecom, but the world of open source hadn't been as friendly to Mac as it is now, and Macs were a prereq for TCom. Getting Scheme running on my old iBook was a pain in the ass, let alone the assignments (which still didn't match the untouchable stability of our automated grading system). I conceptually understood why I needed to learn it, and even grasped many of the concepts of what I was learning, but it wasn't the language for me.
How is this different from opening the URL in Chrome and casting from it?
Not web based, but simple and straightforward:

http://www.ledger-cli.org/
Looks like its streaming arbitrary video URI's without needing to fullscreen the tab
in a win for civil liberties advocates,

Stop me if I'm wrong, but nobody advocates against the government lawyers in FISC arguments, right? So, how can this be a win? I know that's a technical point, but still...

If a notorious rubber stamp says the arguments are "simple unpersuasive", how bad are the gov's arguments?

This also shows that even a hint of publicity works wonders as far as getting some justice out of a secret court. One has to question what other massive abuses are going on under the cover of "national defense" or "compartmentalizatoin"/
This guy is very right. I wrote myself a simple time tracker (I tried a bunch of other ones, but I was unhappy), to track my daily activities. Like John Carmack, I'd turn the timer off any second I'm not spending doing real work, even if I go to the bathroom.

I found out that during a "8-10 hours workday" I'm actually working, as in coding, getting shit done - maybe for about 2, tops 3 hours...

That's not just an interesting observation, I was FUCKING HORRIFIED. I'm pissing my limited lifetime away!

The first step is awareness. Always. Then comes improvement. I kept tracking myself, now being very aware of what interrupts my work, and limiting my distractions. I have yet to claim 8-10 hours of solid work in a day, but it's getting better.
FastClick removes the 300/450 ms delay and makes your click trigger right after touchend, InstantClick makes use of this delay (plus the delay between touchstart and touchend) to preload the page.
"It's satire"

Absolutely not!

Case sensitivity varies amongst countries.

One very simple occidental example: in France names are usually written LASTNAME Firstname

So if you type Lastname and your DB doesn't normalize the capitalization of names you won't match

So for the last name the search is case insensitive but for the first name not so much.

Another example is Turkish, where there are two capital I's, one with a dot, one without.

And not alphabets have a notion of case.
Doing that requires transcoding and generally has very bad performance for me, this doesn't look like it does that (but I haven't tried it yet).
There are several Android apps which will stream MP4s to the Chromecast from a upnp/dlna server. I use BubbleUPnP but Avia is another one.
I don't know, maybe click on the link and see what this is about? Spoiler: no.

>FastClick: eliminating the 300ms delay between a physical tap and the firing of a click event on mobile browsers

>InstantClick: preloading links you are likely to click on