skysight-inc/HackerNews huggingface dataset:
From the Slate article you posted:

"Who says two spaces is wrong?" they wanted to know. Typographers, that's who. The people who study and design the typewritten word decided long ago that we should use one space, not two, between sentences.

The only argument (which is apparently historically inaccurate according to the parent article) made against double-spacing is an appeal to authority and 'the way it's always been done', exactly what you are rallying against in your last reply.

Besides, as has been pointed out already in this thread, a period followed by a single space (followed by a capitalized letter) does not solely occur in end-of-sentence contexts, so a period followed by two spaces does provide an added degree of semantic separation.

Personally, I have no preference. You do what you like, I'll do what looks good to me. I am amazed that someone would assume that I was uneducated or ignorant (like the typographer interviewed in the Slate article), because I usually put two spaces after a sentence-ending period.
Love the content, but my hand can't take it.
I find it easist to understand if you increase the number of doors. Imagine you have to pick one of ten then the host removes eight wrong answers.
Some ad contracts require you keep server logs of hits and not post-processed versions in your DB (in case any discrepancies come up). Running through syslog allows you to centralize where your logs are being processed/sent since each log hit can branch out to multiple endpoints.
I don't have a BS in maths, but the important bit, as I read it, is that you don't know the values involved. I.e. if you have 20, there is either 10 in the other envelope, or 40. You have no way of knowing which is the case, so it's in your interest to swap since the benefits outweigh the risks.

This is totally counterintuitive, though, so I'm fully willing to accept I'm missing something! And I don't buy the 'indefinite swapping' argument, since the second swap must surely reverse any advantage gained.
I hate ads because they usually involve tracking.

I hate Facebook ads because a lot of them are for games, scams, BS products, or companies/politicians where the ad says "click like if you think/agree..." and the statement has almost nothing to do with that company/politician and are just using it to gain likes for the company/politician's Facebook page.

Before I started blocking ads and JavaScript, I've clicked on exactly four ads:

1 Google text ad in their search results - no sale

2 Facebook ads - I bought the products of both ads

1 ad on a blog (not using a third party ad service) - no sale
This sounds like a special case of the secretary problem
http://en.wikipedia.org/wiki/Secretary_problem, where instead of envelopes you swap secretaries and additionally you have a time constraint.

I find it very interesting how these statistical problems can be projected on our own life (swapping jobs, finding a better partner etc ..)
"Just"? That requires more work to set up than my method and offers no additional security benefits as you're still running an open SSH port.

You're falling into the common trap of security through obscurity. But in fact it's very easy to find which port SSH listening on even when you're using a non-standard on. However if you harden SSH properly then it doesnt matter what port it's listening on. So your method is more work for zero gain
I thought #2 was Tel Aviv.
There isn't an animal out there that doesn't have some impact on it's environment. Humans are no different.
I know there are alot of images on this site, but I really think JPEG was a poor choice. The compression artifacts on UI elements look especially bad. I also agree with philwebster about it being really hard to see the full image.
David getting ice
The first paragraph is a non issue, either you care about the original string and thus you have a variable (1) or you don't (2) or compute it from another one (3)

(1) String focus = "aaaa"
(2) String focus = "BBBB"
(3) String focus = oldString.toUpperCase();

I very rarely see list mutation in Lisp, I'd need an example.

The issue with a focus object is that it's cool to thread over one "object", but if you deal with more than one, you'll need distinguishable names, back to square one. What kind of prepositions did you see ? is like using 'it' as a generic variable name in closures/macros?

The first part of your state tracking idea really reminds me of Ref/Atom constructs in clojure.

The generic "subclass" to encode state categories as types is very nice, I toyed with it in college but I then lost interest in OOP (people were too crazy about GoF patterns), I don't know if it's used in production.

The smart cook is akin to prolog goal based programming, here we're quite far from state mutation. I wish there was more systems built on this.

ps: dont worry, my ideas are often blurry, as is my english.
Well, that is a big yikes, but crises (mostly) averted.
Yes, it's not a paradox it's just seductive flawed reasoning.
Yes, at any point EV of picking an envelope at random is 3/4n (n being higher amount of money out of the two).
It is all there is to it. The "paradox" is introduced by silent assumption that distribution of amounts put in envelopes is uniform which is impossible (because you can't pick numbers from infite set uniformly even if there was infinite amount of money in "adversary" disposal). The assumption is then used for conditional probability calculations: "if we see 10$ there is 50% chance the other envelope contains 20$" - BEEP, ERROR, THINK AGAIN.

Perhaps good exercise in clear thinking but not really a paradox.
Good analogy is this:
"If we pick random building and climb to the roof of it there is 50% chance first building we see is higher than the one we just climbed". This is obviously true, now following "paradoxical" reasoning we get:
"If we climb a building randomly and see it's the Empire State Building there is still 50% chance first building we see will be higher".

This is exact analogy to reasoning about 2 envelopes problem which is supposed to lead to a paradox.
Wrong. That's how NOT to set up SSH. Use keys and / or log scanning to auto firewall failed login attempts. I recommend fail2ban, but there's a few daemons that do the same thing.
No man, I feel you. I saw nothing strange, original or frightening about it.
Is this how people actually use their computers? I only watched the first couple of minutes, but it seems kind of odd. I did grow up with internet (25 now) but I don't use Facebook, so maybe I'm out of touch... but seriously do people just open tabs or flash games and porn while talking to someone via video chat? What's the point of video chatting then?

I will say though, the way he didn't really pay attention to her in Skype is similar to what I experience in person... with regards to people texting. I make a conscious effort myself to not text while with another person, and if I do text, I make sure to pause if they talk to me.
I don't disagree, but there are species that invariably have more impact on their environment than others, and those species with inordinate amounts of impact on their environments, or nominal impacts in their native environment with non-nominal impacts in non-native environments are defined as 'invasive'.

We fit our definition for the term. Like I said before though, I don't see anything unnatural about it myself.
"a larger portion" of contract workers across the globe who labor a maximum of four hours a day because "the content they read is so dark and heavy,"

Oh great, he is using Mechanical Turk to watch over students in LA.
This is a hilarious debate to read on hn, a veritable shitpile of busy text. Not complaining, I like hn, just saying it's funny. (btw, I'm firmly in the 2 space camp).
No mention for SELinux because it's more than painful to get into it. No, I will actually say it: Documentation is shit about SELinux.

I actually wanted to do some kind of "frontend"* to SELinux to facilitate it's usage, but I got every time frustrated when going back to it that it never got above the idea point.

* something more like gitflow is to git; than SELinux Troubleshooting is to selinux
Bill Gates interviewed in Playboy (1994)
Or Clojure, which has a good concurrency story as well as compiles to javascript.
The First Version of Your Start-Up Should Embarrass You
lol, dude that was funny.
Meh... I don't think the problem is focusing on "disruption", and I don't see that making any attempt to defocus "disrupting" existing power structures is any sort of improvement. The problem is, it's fucking hard to actually "disrupt" big, powerful, entrenched structures and institutions! Disrupting health-care, for example, isn't as simple as, for example, setting up an EMR site and enabling the ability for people to seamlessly and transparently share their medical records across providers, etc., etc. You can build all the Electronic Medical Records tech you want, but that shit is highly regulated, and their are large, powerful companies with dominant positions in health-insurance, and health-care providers who have to be onboard for things to become widely adopted.

And, of course, there's not much competition in the health-care field, largely due to... wait for it... government regulations.

I posit that our focus should be on making the changes in our society that would actually allow disruption to occur.
“And a very small percentage of readers feel convinced that the furor is resulting from people not realizing that the host is opening a losing door on purpose. (But they haven’t read my mail! The great majority of people understand the conditions perfectly.)“
— Marilyn vos Savant
Food Phreaking – issue #0
That's fine because it's a not for security reasons. In fact I've been known to do the same myself (tunnel web traffic over an SSH server running on 443 to circumvent firewalls on public WiFi hotspots)
Just take both envelopes and run.
Right, and when the FBI goes rogue (because that's whats happening) what?
An Expedia for public clouds?
I don't think federal grants cover the research costs completely. For example, if my professor wins one grant, part of the money will be put aside for to cover 10% of his salary. He certainly doesn't have 10 big grants in play at any given time, so the remainder has to be offset by the University.

Add to that, you need a lot of overhead like administrative assistants, grant managers, technology transfer officers.
Interesting.

This reminds me of a bizarre version of the Monty Hall problem: http://en.wikipedia.org/wiki/Monty_Hall_problem
A friend of mine roasted coffee beans in an air pop popcorn maker.
The paradox depends on the possibility of always being able to double the amount. This isn't true.

Swapping once will either double or half the amount; swapping back will just do the opposite.
So, Padmapper is a useful tool, but you'll get the most mileage out of HAR (http://www.har.com/) for finding a place to live. Generally, Midtown and the Heights are nice places to move to, although the southwest area near the 610 loop is somewhat undervalued and pretty decent to live at.

Optimize for living near easy access to either the light-rail, bus-stops, or the highways--59 and 45 are the big ones, the 610 loop is as well. Don't live in the Galleria area--too expensive and the traffic is shitty.

Basically, living nearish to downtown or the universities is a good idea. You can get very cheap places if you move outside Beltway 8, but the commute time sucks rocks. Inside 610 is the best if you can swing it.

If you find yourself in town, drop me a line, and we can grab beers--I'll link you in with some of my startup folks here.
Perhaps not, but I think the purpose of these Xen exokernels is to run on IaaS platforms which provide Xen VPS, like EC2 or Linode.
OCaml on Xen http://www.openmirage.org/
It's not your fault.

It's actually a PITA to overcome issues like this on a technical level because you have to run something akin to buffer queue, that works similar to how "debouncing" works.

The best approach as I have found is to...

- You rate limit events as they happen... So you might let 5 events through (within 10 minutes), and then start to rate limit them by adding each item to a queue which you will merge down every 10 minutes (but that exponentially/incrementally back off each time you exceed the 5 items, so the next queue takes 30 minutes before it's popped, and then 90 minutes... etc)

- So for example, you might have an instant pop from queue where less than 10 events have been triggered within 10 minutes.

- Then if more than 10 events have been triggered, you add each item to a queue, and after X minutes, you pop each item off and send a bulk email.

----

It's a real pain to manage such a system, because your "typical" job server, such as Gearman, doesn't let you add a "delay" on jobs...

Ideally, you'd want to make sure that you ignore any new events for at least X minutes... So you are left with the only option of running another pseudo-queue system just to catalogue all of your throttled events.

Let's talk strategy. How else do you guys handle instant email notifications?... without this spamming issue.
PS. I'm referring to GitHub implementing this strategy, not the OP in case there was any confusion.
I'm surprised that Github has not implemented a feature for repo migration from google code and sourceforge.
Once you have the second envelope in hand, since you don't actually know what's in it, the exact same expected-value argument applies to switching back: there might be $10 or $40 in the other (first) envelope, "so it's in your interest to swap since the benefits outweigh the risk".

While the second swap would reverse any advantage possibly gained, it would also reverse any possible harm sustained
You dont know. The situation is perfectly symmetric; picking and switching is the same as just picking the second one at first. So just pick one.
It wasn't Einstein
http://ianchadwick.com/blog/it-wasnt-einstein-who-said-it/
Dropbox-Hosted Websites
While you may be the "visible culprit" - I'd hardly say you're at fault. The action you're attempting is not a "send email" action, even if the API provider has decided that it should send email notifications.

The implementation you'd probably want to see is for the API's email notifications to be batched if more than small-n trigger within a short period of time. Then the end user gets a notification that "1700 updates have occured" instead of getting 1700 emails.

The API should also be set up with exceptional event detection. Spikes which are several orders of magnitude above normal should get paused in the task queue and flagged for immediate manual review. Users do things you don't expect.
Can we let go of this post-mortem analysis of the world-that-could-have-been already? It's like the reports you get after someone dies "Oh, he was so happy... he was working on a new album!"

Nokia could've done many things, but it's hard to argue that them making an Android phone would have saved either Nokia, or improved the Android ecosystem. Nokia's failings go much deeper than the choice to go with Windows, (or the failure to go Android). And had they gone Android, they would've been yet another hardware vendor trying to differentiate themselves in a crowded Android field. HTC, Samsung, and Motorola are also capable of making good hardware, but unless there was some secret sauce about Nokia that would've solved all the existing shortcomings in that ecosystem, it's pointless to lovingly sigh and talk about what might've happened.
I run a three-year old Windows Core i5 notebook with a GT460M GPU and all runs fine...
Agreed here. Making a shared protocol for the cpu, RAM, and disk? Heck, how fast is this phone expected to run exactly.
Be engineer #1 at Lob (YC S13) and build a suite of cloud APIs
Email us at jobs@lob.com with your Github link, resume, and any additional details you'd like to share with us.

-------

Company

Lob is creating a suite of API’s to revolutionize how companies operate. Our first API is a Cloud Printing API. Our product enables developers to programmatically facilitate printing and fulfillment. If you are passionate about API’s come help create the next wave of great API’s at Lob. Lob is a graduate of the YC S13 class and backed by leading internet venture capital and angels.

Team

We are currently a 3-person team (from AWS and Microsoft) based in San Francisco. We are looking for other passionate people who share our vision that API’s will eat up the world.

Job

We are seeking a software engineer to build the best cloud printing platform on the planet. You will be the first engineer to join and as such will have an unprecedented opportunity to shape the future of Lob’s APIs.

Responsibilities:
• Own the framework of the API that is the core of Lob’s business.
• Work directly to define, architect and build new Lob APIs.
• Drive towards successful deliveries of scalable, maintainable
and secure code.
• Create and define engineering best practices.
• Tackle challenging problems in distributed computing, HTTP, API
design and more.
• Build and maintain client libraries for our API in a number of
languages including PHP, Ruby, and Python.

Requirements:
• Experience leading engineers in a technical leadership role.
• Experience working with API’s and HTTP, preferably in PHP and Ruby.
• Full-stack development skills.
• Hands on. Passionate. Persistent. Creative.
• Experience with AWS.

Perks:
• Competitive salary and equity.
• Health, dental, and vision benefits for you and your dependent(s).
• Open vacation policy.
• Commuter benefits.
• Free lunch, dinner snacks and stocked fridge.

Want to stand out? Sign up and build an app using the Lob API. Include a link to it and brownie points for pointing out bugs or things that annoyed you or could better about the platform. Email jobs@lob.com if you are interested.
Ergo, it is a downside of all unregulated markets.

Unregulated? Do regulated markets have perfect information?
Reality: "Type systems don't keep you from writing wrong logic, they only forbid you to write inconsistent logic."
Interesting, I didn't know about this. However, the comment is still wrong, this was a joint effort between Apple and Novell, not "a bunch of random engineers".
And all btilly said was "If [trivial aesthetic concerns cause you to experience hate], I don't want to know you."

I think that's an entirely defensible position. And without knowing btilly, or having myself said this particular thing, I can easily imagine myself saying things like that in person, in some circumstances, and it's a point of personal pride.

To reply to some of the other comment threads, without spawning many sub-comments, I note that "I don't want to know you" is not the same sentence as "I think you should be murdered", or something. Experiencing hatred for aesthetics may or may not be a fatal character flaw, but that's completely irrelevant.
Yubi Neo looks nifty, NFC should make it real convenient to use (drop keys on desk to authenticate, what would be easier!)
The way I see it the flaw is in the first sentence of the "example":

> Assume the amount in my selected envelope is $20.

You can't just pull that assumption out of your ass. You can only assume what the problem states, which is that the values in the envelopes are X and 2X and you had a 50% chance of choosing either.

If you run the math without adding assumptions, it works out that swapping makes no difference, statistically.

Though it is a very clever trick :).
The quote:

> Why didn't you have tests that caught the syntax errors? Static typing doesn't ensure correctness for languages like C++ and Java.

It seems like they is saying: "you have to write more tests, yes, but you have to write tests, anyway!" So if I have to write 20 tests in one language, and 200 in another, the difference in effort is negligible because I need to write tests anyway? So if you can express something in 10 times less code in one language compared to another, it doesn't really matter since "you would have to write some code, anyway!". I really don't get this 'you were going to write tests anyway [says who?], so you might as well write it for any possible unintended null-value, value-was-string-but-should-have-been-char, too long argument tuple in function call....."
Starting something with the goal of disrupting an existing industry is like becoming an actor or singer with the goal of making it to the Top 10 charts: both types of efforts are doomed to fail because they focus on the wrong thing.

The right thing to focus on would be to try to do the best job possible. A musician who tries to create the best music possible and to connect with his/her fans at the deepest level possible is much more likely to actually become famous. In other words, things like "disruption" and "becoming famous" are best treated as byproducts, rather than the main goal.
> How much entropy is needed to generate a 4096 bit key?

4096 bits?
Christensen did good descriptive work in his early books. Disruption was a thing. He tagged it, studied it, and described it. All that was very helpful. I actually am sympathetic to his later prescriptive works, I think they are seeking to solve social problems through disruptive change. I think what's happening in this essay though is that Pasquale sees the effect bound to the prescriptions, or even some alliance of pundits. That's just not the case. We can argue suggestions, but disruption will keep happening where we don't expect it ... because it is a thing.
I ask again: so what?

Musicians don't need producers--in fact, this has been a role only recently filled in the 20th century. They don't need them to perform, they don't need them to record, they don't need them to make money. In fact, you can very easily find examples of producers doing more hard than good...just ask any fan of Streetlight Manifesto.

Technology, both in recording and broadcasting, has advanced to the point where we don't need these gatekeepers. The market will adapt to supply good-but-cheap recording gear for musicians who can't afford lots of studio time. The market will create cheap online labels--already has.

You didn't say a damn thing the artists, man. You just kept trying to find a way to fund the middlemen. People like you are what'll kill music, if anything.
The problem is github makes all notifications STD-level contagious. They broke out "watching" and "staring" a while ago, but they are still very overzealous with notifying everybody about everything.

The poster didn't use "send email" API, he was just automatically importing things, and every import triggered emails nonsensically.
WTF?? So,, yes,, use double-commas to drive home your point since you must have had some reason to put them there. I will continue to use double space after the end of a sentence for the same reason.
Don't worry, I doubt he'll have to rethink his position - after all, he's almost certainly white.
The City of London has a unique legal position that lets type of thing happen. If you look into this corporation's history it will make much more sense.
Use the archive view: http://madeforios7.tumblr.com/archive/.
You're being pedantic in muddying things with extra variables, namely the adjustment due to full justification. Let's simplify things and just consider ragged right. In this context, TeX is indeed approximately 1.5 spaces after a period, except for \frenchspacing, which uses 1 space.

AFAIK, the reason TeX uses this default spacing is because Don thought it looked good.
It's conceptually a single space, but the difference between 'two spaces' and 'a space twice as wide as normal spaces' isn't very important. Since lines won't wrap mid-space-block, it's effectively an encoding issue.
As others have mentioned, nginx + one of the redis (or lua-redis) modules does this very well without the complexity of syslog in the middle. We load many millions of values a day via httpredis2. It's been rock solid.

http://wiki.nginx.org/HttpRedis2Module

We log the same requests to a file in a custom log format that gets batched to s3 and then Cassandra and EMR/Hive. Makes a great platform for realtime + historical analytics.
Is it just me or is the phys.org site down?