skysight-inc/HackerNews huggingface dataset:
You're right about the "leak" distinction, but the "classified at the time it was sent" question is stickier:

http://www.factcheck.org/2016/07/clintons-handling-of-classi...

> More than 2,000 of the 30,490 emails Clinton turned over to the State Department contained classified information, including 110 emails in 52 email chains that contained classified information at the time they were sent or received. (Most emails were retroactively deemed to contain classified information by the U.S. agencies from which the information originated.)

> Some of the emails containing classified information “bore markings indicating the presence of classified information,” contrary to Clinton’s claims that none was marked classified. Comey did not provide a specific number.

> "Only a very small number of the emails containing classified information bore markings indicating the presence of classified information," Comey said. "But even if information is not marked ‘classified’ in an email, participants who know or should know that the subject matter is classified are still obligated to protect it."

It's also entirely possible that of the thousands of emails that were not turned over, some of them contained classified information. We know there were a non-zero number of these:

> Among those several thousand work-related emails that were not provided to the State Department, Comey said, "three of those were classified at the time they were sent or received; one at the secret level and two at the confidential level. There were no additional top secret emails found."
Show HN: Stack overflow command line client now supports tag based search
>while also being understandable by humans.

I don't understand how one can understand Elm and not understand Haskell, unless the expectation that Haskell is difficult makes people's brains shut down without even trying.

Most of the ML-esque concepts that make Haskell "hard" to read if you come from a C/Python/Java/etc. background (ADTs and pattern matching, application by adjacency, etc.) are present in Elm as well.

> I vastly prefer Elm's record syntax to Haskell's,

Are you familiar with Lenses? Classy lenses in Haskell provide a slightly less sexy but more powerful system of structural typing.
I wish I could upvote this more than once.
There's so many ways to accomplish the same thing in $SQLEngine that a lot of it comes down to style and clarity/rereadability. I'd prefer keeping the join conditions as USING or ON in most cases because it keeps them close to the statements related to it. Where I work I have to read through a lot of older code that hides them in the where clause and uses 3 letter abbreviations almost exclusively for table aliases which can be pretty tedious to sift through. Again it's mainly down to personal choices though (or in some cases institutional guidelines).
Our website is admittedly focused on marketers, but the product works great for event planners too. We have a scheduling feature which breaks down where each participant should be, min-by-min. I'd say share this screenshot first (http://imgur.com/of3Sn49) and then give the free trial a try. The benefits should be obvious in the first few mins.
They only apply population stratification from Figure 2 including onwards:

>The results so far do not control for population stratification because we wanted to characterize overall similarity. However, it is important to remember that some of the similarity in genotypes can be explained by simple assortment into relationships with people who have the same ancestral background. The Framingham Heart Study is composed of mostly whites (e.g., of Italian descent), so it is possible that a simple preference for ethnically similar others could explain the results in Fig. 1. However, in the following results, we applied strict controls for population stratification to ensure that any correlation we observed was not due to such a process.

I don't understand why they did not do this for Figure 1 (or why they do not show that figure) - I assume that the difference disappeared, but who knows.

I just realized that this paper is from 2014, first published on arxiv in 2013. I can't find any study replicating it in the 34 citations since so I would be careful (but this type of dataset for replication is hard to come by) https://scholar.google.com.au/scholar?cites=7301900347564089...
You can make that at Google without becoming a manager, if you know something they really want (or are otherwise technically senior enough).
Possibly stupid question: why didn't some enterprising person figure out how to produce CD-Rs with the copy protection wobble track? Is the market too small vs the cost of required equipment? Would it have been illegal?
Shoot me an email, its in
My bio. I'm a UX & UI designer working on something in the same space would love to connect.
Halo is basically an extension of the Marathon storyline. I do miss Myth and Oni though.
Ah, I read "sons of first cousins" as "two people who are first cousins to each other each have a son". "A son of a first cousin" would be much less ambiguous. In fact, even knowing what you meant, I have a hard time reading the meaning you intended to convey.

Another clearer way to phrase it would be "sons of my first cousin are not my second cousins".
I agree. I'm not a crazy conspiracy theorist, but this looks photoshopped. The clouds are not moving and the moon is not rotating at all :

http://imgur.com/prywsJq
To expand on what pinewurst said, the Alto was built minicomputer-style out of TTL chips, so even with minimized hardware the CPU took three large boards of chips. Within a few years, microprocessors took over and Moore's law crushed computers built from discrete chips.

Here are some bonus pictures of boards from the Xerox Dorado, which used ECL chips for higher speed. First is the ALU board; the large chips are ECL versions of the 74181 ALU. Second is a detail of chips from the 10K family, as well as unusual square memory chips.

https://lh3.googleusercontent.com/--KYoSBUuOhg/V4Rxs7tLB-I/A...
https://lh3.googleusercontent.com/-MWYhn7enXdA/V4RxsQ8YHRI/A...
Also, if I'm reading it correctly then each plaintext message from a particular client ends up at the same location within an epoch, due to the one-time shuffle at the beginning of each epoch. That might be able to reveal information about a client's activity within the epoch.

I also wonder if the presence of distinguishably-mandatory plaintext messages could be used within an epoch, particularly with respect to the previous point. E.g. maybe knowing the the same client was active in rounds 1 & 2, the inactive in round 3, then active in round 4, then inactive in rounds 5 & 6, then active in rounds 7 & 8 could be used to identify the client (imagine a low-latency system, and keystroke timings or voice packet lengths).
Very cool, Lyon. Sending you an email now.
Somewhat reminiscent of agl's awesome-but-defunct pond, with turn-based rather than randomized sends.
> I feel like I can whip up whatever software I need and fast barring super deep academic bits but can't imagine who would pay my 400K.

I don't know about the 400k specifically, but I hope you might want to change your attitude: you don't need to sell for what you believe is reasonable and can imagine; you want to be selling to people who have more money than sense.
That's interesting comment about the air..

Anyway, I should point out, though, UBI would probably make higher middle class (the people who have job, but don't have to worry about unemployment) a little worse off - they would have to pay people having low-paying jobs a little more, because the existential threat is gone. That's a good thing, IMHO. Although it makes the GP comment a little more nonsensical - UBI is actually against the interest of the higher middle class professionals.
Thanks ! It makes sense. :-)
Can you explain why you would record an infringement before the three day window for counter notices has expired? You have no section for decrementing/annulling infringements or re-enabling accounts, so if you follow this process, I can disable your users' accounts simply by filing two bad-faith DMCA notices.
Courts and the law aren't so literal. They'd almost certainly treat person that controls/rents the server as owner even if they were just renting space in the cloud.

The idea is that an end user can't give you authorization when it was explicitly revoked by the actual owner/operator.
Sometimes with complex queries, it can be tough to adhere to a simple set of style rules while also making clear where things like logical units start/stop. Don't get me wrong I'm not disagreeing with you in principle; but acknowledging that the declarative nature of the language cause you to break style for the sake of readability in some cases. I'm not going to post an example of such a case (I'd have to go digging and I'm too tired).

On a different note, I don't like a lot of the styles I do see. I like yours, with the exception of the joins. My convention is a bit different:

SELECT
members.firstname as "First Name"
,members.lastname as "Last Name"
FROM borrowings
JOIN books
ON borrowings.bookid = books.bookid
JOIN members
ON members.memberid = borrowings.memberid
WHERE books.author = 'Dan Brown';

Some of that is old habit (like the comma first thing which I know is out of favor with many) which I found useful when working with long column lists. I'd also typically and systematically alias the tables, but that wasn't done in the examples. Outside of tastes, the only real downside I run into is that it's easy to get too far to the right with the indentation style I use. But it's not that often that I get there.
$15/month on top of gas fees? Not interested. Without the monthly fee though, very interested. There's almost always a wait for gas stations when I go, so this service makes sense.
>laziness induced problems

This is like saying that Java has "strictness induced problems". It's true, but probably disingenuous. Obviously large, well-funded strict object-oriented projects have memory leak problems as well (all browsers).

> no good debugging support

One generally doesn't require as much debugging support for Haskell, but it's actually quite nice if you follow a debugging process amenable to pure functional languages. People coming from a Java background want e.g. a breakpoint debugger, which doesn't really make any sense at all in a pure functional language; a vastly superior approach is to do e.g. quickcheck-style checking or input/output debugging on pure functions. If your code is impure, you can essentially debug like normal.

Bugs in Haskell also aren't the same as most of the bugs in other languages; you never get null pointers, for example. Every bug in Haskell is either a logic bug (which can often be debugged purely, and can be minimized by the careful application of types) or an atotality bug (which can be completely avoided by totality/completeness checking, and dynamic debugging of such bugs is getting much better with the new implicit callstack feature added to recent versions of GHC).
This is a pretty good guide generally.

I am a bit skiddish about the counter filing process. What is "filing suit" in this context? That process isn't clear to me.
I may be wrong, but a quick Google shows a lack of development resources for the CHD format. Either they need to do some SEO, or some straight up marketing.
I found this when looking for more info on the "wobble": http://assemblergames.com/l/threads/saturn-copy-protection-a...

"I hope this lays the matter to rest, and prevents anyone from wasting more time on it (like my day burning useless discs).
I'm sure someone will wave their hands around and say that custom burner firmware could do the job, but good luck finding a burner with a programmable DSP in the pregroove tracking loop and managing to modify it to do the job."
Z Camera 2.24 APK FULL and FREE Download
Shocked to see no mention of PureScript [0] on this thread, which is also a Haskell-like language that compiles to JavaScript.

PureScript has the notable advantages of generating mostly-readable JavaScript and working in node. [1]

[0] - http://www.purescript.org/
[1] – http://try.purescript.org/ – click "Show JS Output"
I think it's probably much truer that big tech companies are optimizing for false negatives because they do have a really deep, talented applicant pool. Some start ups do but it's definitely more of a risk. I completely agree with you that in general you're better off optimizing the F-measure, but I'm not sure it's empirically true that lots of companies thought of as good do this.
Harasp Tapping Iran’s Luxury Fashion Market
$2M stolen from Taiwanese ATMs
"The only real way to get better is practice." 100%
Here's an example of a PureScript React application:

https://github.com/ethul/purescript-react-example/blob/maste...
Show HN: Retry – A stateless, functional way to perform actions until successful
I was looking for a well made and reusable "retry" library, but all I could find were libraries with awkward interfaces/APIs, overuses of state/pointers, a lack of extensibility, or they'd somehow opinionate themselves towards a specific purpose (HTTP retry libraries are in a major abundance).

So, I figured I'd take a stab at creating a retry library that worked in a simple loop with functional composition that would allow for easy extensibility. I ended up writing an API that somewhat heavily used the functional option pattern described so well by Dave Cheney in his blog post: "Functional options for friendly APIs" (http://dave.cheney.net/2014/10/17/functional-options-for-fri...).

Ideally, the library's packages can be used separately, so you could use the `jitter` transformations even if you don't want to use the actual `retry` mechanism. That is why the library is split into a few packages.

Anyway, I'm curious as to what HN thinks about this library. Anything that I could definitely improve? Is there anything awkward about the API in particular? Something that I missed?

I appreciate the feedback! Thanks!
> boilerplate, verbosity, and overly tight coupling

Can you give an example? Can't think of anything off the top of my head that fits this description.
Just this Sunday, I was looking for an IDE that I could use to start experimenting with Rust. Happened to find https://plugins.jetbrains.com/plugin/8182?pr=idea which is what got released more officially today. But I also then found this on the Rust site https://www.rust-lang.org/ides.html which talks about lack of on-the-fly, quick compilation support within the Rust compiler itself, a feature that's a major requirement for IDEs. I haven't yet started using this plugin (plan to do over the weekend), but I'm curious if this plugin supports on-the-fly compilation and error detection.
The clouds absolutely are moving.
So here's the Elm high level on the tree of components:

An Elm component is typocally a Model type and a Msg type. When side effects occur, the component receives a call to update with the model and the message. It returns a new model and a new side effect to cause (could be none). The model is then rendered into a view.

If you have a user profile component then maybe you have a user info component and a settings component. And maybe the settings component has a notifications component and a privacy component.

The Model for that is pretty straightforward. It's just a tree of data.

The Msg for that is what is being complained about. Any side effects caused by a child component will call the update function of the parent. It then has to route that to the child component.

The result is that you have:

type Msg = ProfileMsg Profile.Msg | SettingsMsg Settings.Msg

type Profile.Msg = ...

type Settings.Msg = NotificationsMsg Notifications.Msg | PrivacyMsg Privacy.Msg

type Notifications.Msg = ...

type Privacy.Msg = ...

So now your top level msg could be a SettingsMsg (Settings.PrivacyMsg (Privacy.SetDefault Privacy.Self))

And in order to process it in update you have to unwrap the outer type (like SettingsMsg) and then call update on the child component with the data from the msg. You repeat until a component can handle it. The the component returns a new model and possible new side effect. You wrap up that side effect in something like SettingsMsg and return it along with your new model.

It's a lot of boilerplate. As far as creating coupling, what if you want to use the notification component elsewhere in the app. Now something other than Settings needs to wrap it so you get Settings.NotificationMsg and Toolbar.NotificationMsg.

It just gets clumsy.
Filing suit means starting a lawsuit against someone (in the case of copyright, a Federal lawsuit).

http://www.uscourts.gov/about-federal-courts/types-cases/civ...
I recently quit my job because of burnout and management problems. Since then, I applied to 39 jobs. I pulled out of the process with four, 34 rejected me, and the last one was the offer I accepted. Out of the 34 that rejected me, 11 rejected me after a full loop. I don't know what was more insulting, doing 11 full loops (3 of which required air travel!) without getting an offer, or getting rejected by 23 companies without even reaching the full loop step.

Big companies have fixed interview processes that are designed to weed out false positives at the expense of having a lot of false negatives. Startups by and large don't know WTF they are doing when it comes to hiring. Companies in the middle deceive themselves into thinking they have a process when they really don't know what they're doing. Some companies experiment with their hiring process, which is a lot like not knowing what you're doing except they get usable data out of it afterwards (at the expense of you, the applicant). And some companies don't even have a clear idea of what roles they need to hire for when they bring you to a full loop. Twice I've received interview feedback to the effect of, "we like you, but we can't actually move forward with the role we interviewed you for because we lost budget/want to rework the role requirements".

If you're interviewing with places like Google and Amazon, you're in a career that pays six figures. A six figure career isn't treated like a five figure career, and tech is a pathological example of this. Most six figure careers--doctor, dentist, longshoreman--have some sort of barrier to entry where you go through years of hazing, high expenses, and unreliable income. Other six figure careers are really just the top of a five figure career. With tech, I don't know how it is if you have some sort of marker that you've already been through years of expensive hazing (i.e. a degree from MIT or CMU) but for a guy like me who went to a mid-rate state university, there's the same instinct to have a high barrier to entry but instead of making that barrier to entry something that you can spend a few years climbing through, it's a gigantic wall that you get one chance to jump over. And that wall is the interview process.
To supervise or not to supervise in AI?
Maybe a condition of copyright should be that you submit the unrestricted media to Library of Congress, and it gets released upon expiration of copyright.
If you were to stop all of those things, would that not include stopping the causes of rain, if they exist? (For that matter, is that why you can say 'surely' in that sentence?) If we thought we knew the causes of rain, and happened to be correct (both that there are causes and in what we think they are) then should we not be able to predict what, short of stopping all of those things, would stop the rain, without having observed that happen?
Micah Scott's toastermelt videos are another great example of reverse engineering workflow/techniques. More technical and detailed but still very accessible.
hi, right now its 6 pages:
Github
Remoteworking
WeWorkRemotely
Stackoverflow
Jobmote
Wfh

they either provide remote jobs mainly or i filter them.

Thx for liking it, it would be really nice to know if someone actually found a job with that page. Truth is the page visits are quite low and i am not motivated to work on it. But it will still run without any change. I may come back to it, but there is a different side project right now that i am trying to accomplish (its great to be a full stack developer :P ).
What he actually said was "a probability for civilizations to form of one in 10 billion per planet was considered highly pessimistic [but] even if you grant that level of pessimism, a trillion civilizations still would have appeared over the course of cosmic history."

In other words, even if the paper's calculations are off by a factor of a billion, there must've been 1000 civilizations before us. And, no, that's not proof but more of a rethinking of a thought experiment based on new data.

If you wanted to dispute this, you'd have to show how any of the estimated numbers is wildly off or that the model (Drake's equation) is all wrong somehow.
> Google has extremely strict safeguards in place to prevent eg. employee Joe from accessing ex-girlfriend Mary's Gmail

I know a bit about google's internal privacy safeguards (including how long they've been in place), and I know a bit (nothing that wasn't in the news) about the NSA's internal privacy safeguards from a certain point in time.

Obviously I don't know what it's like at the NSA today, but it's worth laughing (or crying) at the fact that there was a time when Google placed more restrictions and security in place to protect its users from rogue employees than the NSA did.

Not to get too political.
So you're actually arguing for companies to hire employees who will likely produce negative output (their code will be so bad as to take not only their own time, but other programmers' time to fix) just to ...what, not hurt the feelings of the bottom 80 percent of developers?

Your analogy is poor: Hiring a bad programmer is an extremely high probability event, even in a broad pool of candidates as would apply to a high-end company like Amazon, not a low priority event. There have been studies dating back to the 70's that show a 10-20x skill difference between average and great developers. If you're going to pay roughly the same for a 1x as a 10x developer, wouldn't you want the 10x? So they tune their hiring process to skew that number as high as possible.

OP above may be an exception who fell through the cracks, not really ragging on them in particular.

I did know at least one person who applied to Amazon and who was rejected -- and rightfully so, in my opinion. His skills were sub-par, and the interview process detected that. Most others that I worked with while I was at Amazon were also above average; people I've encountered at other jobs have been mediocre by comparison, with the exception of a number of game developers I know.
One man's high cost of health care is another man's high salary opportunities in healthcare and pharma industries. Becoming a US-certified doctor is the golden ticket in many medical schools around the world.
> In the eyes of the interviewers, you were not the most qualified candidate for the position they were hiring for.

For Amazon, this is not a correct conclusion. Having done well into the low-hundreds of on-site interviews for Amazon, I do not recall a single instance of a debrief discussion comparing one candidate against another. At Amazon it is simply a matter of making the bar or not making the bar. While it may seem like you are interviewing for a specific position, in reality at Amazon you are interviewing for a given role and level. Generally the level is targeted based on the candidate's experience and if the candidate barely doesn't make the bar but the interview loop agrees they have growth potential they may get an offer at one level lower, though this is not particularly common. Amazon will extend an offer to any candidate who meets the bar regardless of how many good candidates are interviewing for a specific "opening". Between the company's growth rate and the high attrition Amazon needs more new hires than can be found that meet the bar.
Basically the only way to get a view like this is to be in a lissajous orbit at the Earth-Sun L1 point and happen to get a lucky alignment between the satellite, earth, and Moon sometime near a full moon.