skysight-inc/HackerNews huggingface dataset:
From what I've observed, new comments are initially added as the first child of their parent and will stay there for a bit. They drop over time based on how many up votes they've received. I think there are other factors involved as well, such as karma as the commenter, but that's speculation.
You might not want to use emoji to represent upvotes and downvotes.
Which still results in a system where a massive percentage of the people end up unhappy.

I think you can do a lot better by giving more power to smaller parts of the government. For example, let's assume that 50% of the most controversial laws were turned over to the states. Suddenly California can be more "blue" in practice and not feel nearly so upset when "red" wins both houses and the presidency.
I've written an interface similar to GraphQL some time before it was made public using JSON to describe the desired data tree, filters, etc.

The real upside of GraphQL is that it has become popular enough that there are parsers in most languages, and that you don't waste time designing and testing a new standard. If you use it for a public API, you can also simply point people to the existing documentation.

It's definitely not a widely accepted standard, but still better than rolling your own!
What's Wrong with Literary Studies?
Airbnb works the same way with credit cards.
While Darwin was formally only a minor employee, if he had any formal position (he was not a naval person), my understanding is that he was primarily there to keep Captain Fitzroy company, in an environment where the combination of social stratification and naval discipline meant that the captain was nominally in a sort of socially-imposed solitary confinement (I wonder how Cook managed on his voyages, but I suspect he was much more flexible than Fitzroy with regards to these matters.)

Formally, the ship's surgeon was the expedition's naturalist, as was the practice in those days.
If only I had taken the advice in life I dismissed so quickly out of disbelief, just like you're doing now, I'd be where I am so much faster.
Does this value-added justify their scummy practices? Other middle-men seem to get on fine without doing the bad things outlined in the article.

And academia is already about networking; collaborations, at least in CS and Mathematics, are a big part of research, so finding the right set of reviewers shouldn't be too difficult for editors of a journal, given that these editors are probably well-placed people in the field.
> In this case the project does actually have a proper website (which btw. is nowhere mentioned on the Github page). Why not just link to the website instead? Is that somehow not cool enough any more?

I can't sympathize at all with your sense of exasperation. I know you feel like you are arguing for a cause, but you're also being condescending.

The purpose of this post isn't to introduce a project, but to announce a significant milestone version release. With that in mind, it makes a lot more sense to link to the announcement post on github. It includes plain language descriptions of the changes, download links, plenty of screenshots, and hardly any SHAs. The website is mentioned at the very top of the main github page, as well as in several other places.
OK, sure, but not exactly what I was pointing out.

If your goal is to provide a consistent look and user experience across platforms and be easily extendable, what do you choose? Feel free to name one.
A couple of years ago I was very much in favor of a universal basic income (UBI). But as support in the tech community grew, I became more skeptical of the idea. The election of Donald Trump has really solidified my opinion that it's a non-starter.

Lots of engineers, including myself, love the idea of a UBI. Many of us spend much of our free time tinkering and learning. And that time spent often directly translates into the improved marketability of our labor skills. For people out of work, what could be better than having enough income coming to support yourself while you learn new skills, pursue new business opportunities, or volunteer?

The thing is, software engineers are a self-selected group of individuals, generally much more self-motivated than most any other group in the country. This is especially true of American engineers, and of many of those who find themselves in America.

But most Americans are not that self-motivated. Worse, most middle-aged Americans are downright hostile to the idea of continuing education. (Even many software engineers are still hostile to formal education.) The echoes of the well-paying company job from the 1950s still reverberate today, and it's fubar'd most Americans' expectations. They expect to be able to find a well-paying job around the corner; without having to change their interests; without having to challenge themselves intellectually; and without having their self-esteem challenged by the inevitable failures encountered when you don't have the crutch of taking orders from someone else.

I don't think this is going to change anytime. Things are slowly changing, but not in the way we expected. I think there was a paper that came out recently that said younger people are less anxious about finding work than previous generations at their age, but mostly because they're more content playing video games. So, at best, a UBI will simply enable a more passive labor pool less reactionary and prone to voting for a Donald Trump. At worse we continue down the road of intensely bitter political warfare, with each party jockeying to capture the elusive "give me the same job my grandpa had" voter.

Also, engineers (including myself) probably have some pretty rose-colored glasses in how we view ourselves. We're probably not as self-motivated as we think we are. The differences are probably marginal at best, amplified by the tremendous growth of the past 20 years which, historically speaking, we shouldn't expect to continue indefinitely.
A resume doesn't need to be exhaustive. It's common to leave off a J.D. when applying to non-law positions (precisely because of this).
That is true, but I feel like it's exposed to a broader audience in the front-end dev world: you can be a backend dev in whatever language you like and you've probably worked on a project where a front end dev has introduced some ridiculously complex build system for css files.

This is literally the comment I was given by a dev who was continuing someone else's work, about how the front end assets needed to be built:

i) install npm
ii) install grunt globally (npm install -g grunt)
iii) install bower globally (npm install -g bower)
iv) install bower packages (bower install)
v) install npm packages (npm install)
vi) run grunt
Switzerland style rule is nice because it allows for some rogue candidates to be elected safely. Trump wouldn't be so scary if he had 6 other people holding a leash. But the probe would still get to signal dissatisfaction and the other parties would have a better warning that they aren't in a great position and need to update their stances on the issues.
The amount of code needed to verify that only the proper fields and records are included for a particular response taking into account the user's permissions etc is often not so different from the code needed to retrieve just that data in the first place.

There is an issue here where as you give more sophisticated querying capabilities to the client, you need to have correspondingly more sophisticated validation of those queries on the server, which offsets some of the gain.
It's too convenient, but I can't stop. However if the prices keep creeping up I might just drop them.
Your example (sputtering charge onto insulator) is of a similar flavor (but with E fields). The OP article seems like a monkey-patch way of "self-repair". Should we also create a self-repairer for the self-repairer? Little arms repairing other little arms repairing other little arms which are repairing a Raspberry PI. It's a cute, steampunk-y image -- what I imagine Leonardo Da Vinci would have jotted down in a book somewhere.

Alternatively, what you said: we could just send out a large number of duplicated devices. This might be easier, but more expensive.

How are computers even designed? If a single part fails, the entire thing can still function, more or less -- true or false? What about a brain? A body? Organs? My hand would still work, even if I ripped off a significant chunk of skin and flesh. It will even repair itself over time (the flavor of the OP article). If I cut a biofilm or an earthworm in half, both halves will "work".

Now, I am not a computer scientist, computers obviously aren't like biofilms -- but I am not familiar with the extent of this dissimilarity. For example, if I randomly remove 2,000 transistors from a computer (simulating solar wind), what is the probability that the computer will be rendered useless?

The second way I interpret what you say is that we actually redesign our computers, inspired more by biology, to be able to still work even if some computing elements or memory elements are flipped or destroyed. This is probably way outside of my lifetime, though.

But we are already seeing this in the ML community, with things like dropout. If I removed a random set of nodes from a deep learning network, the network would still work fine, more or less...

Edit 2: So, if we had something like that glass with the charged layer (i.e. maybe transistors which created a small magnetic dipole, so the entire device was effectively a ferro magnet), some elements would cop-out and the system would be rendered useless unless it was designed to be robust like an organ losing some cells. But that sounds really hard. We want the transistor or component to maintain some internal state, while being a magnetically shielded box. Hmm... almost like a topological insulator with a doped body.
I tweetstormed about this once. https://mobile.twitter.com/tomdale/status/786950181522636801
Silent Retreat
think this book is a particularly interesting read, especially considering the U.S. election opera of 2016:

"Infomocracy" -by Malka Order.

+++ some other favorites:

When Breath Becomes Air. -by Paul Kalanithi.

Arkwright. -by Allen Steele.

The God's Eye View. -by Barry Eisler.

Chaos Monkeys: Obscene Fortune and Random Failure in Silicon Valley. -by Antonio Garcia Martinez.

Ego Is the Enemy. -by Ryan Holiday.
the only way of removing your credit card details from your Uber account is to...

You could also ask them to delete your account and certify that all PIO and payment information has been purged. Depending on your state if residence, there may be other things you can ask for.
A few reasons I can think of off the top of my head:

1) Anything that can be effectively described as "blue collar" will probably be replaced by automation within 3-10 years depending on the job.
2) Creative thinkers should be valued more highly in the tech field than those that can just follow orders blindly. Very few tech fields emulate an assembly line and the ability to think for yourself and develop an alternative solution is and should be highly valued.
3) Most people in the tech field, both employees and employers, are probably intellectual to a degree and free thinkers in and of themselves. So the cycle continues.

I'd also like to point out that this idea of a blue collar work ethic is somewhat flawed. There is not specific work ethic associated with the blue collar worker naturally; it's just a result of never having enough money for pleasure, so work becomes a part of the routine. The job doesn't matter as much when you're dirt poor as long as it's making money, and the risk of job loss is what you're describing as loyalty. This is really nothing more than a capitalist machine at its worst, not some utopic worker's attitude we should all aspire to.
Good point. The following is something I thought of before and after I replied to the comment below, but which escaped my mind when I wrote it:

It depends on how the author represents the story. If he represents it as an example of Rockefeller's leadership technique and skill, that's one thing.

If the author represents it as Rockefeller's exceptional efficiency and engineering acumen, or is trying to show how relatable Rockefeller was, then the author is doing PR too.
I work at Real World React. We specialize in training engineers on front-end web development, specifically React, Redux, RxJS, and related technologies. We've trained engineers from Twilio, OpenTable, NerdWallet, Tesla, Esurance, and many more. We are based in SF.

Since we also do private consulting and project-based work in addition to our workshops, we have recently got to talking with our clients about helping them get full-time employment. So I think this post is pretty timely and very relevant to us. Here are a few reasons why we think React is important for the job market.

Lots of companies are choosing React for their front-end these days. It allows your front-end devs to embrace the full power of JavaScript for the front-end -- no more messing around with jQuery and tons of plugins. Sure, there's a bit of a learning curve, like all new things. But there is now a large and devoted community to React and it's only growing. A personal friend of mine convinced his boss to greenfield their entire app with 10,000 lines of jQuery, and rewrite it entirely in React. He was a new hire (and also a great communicator/salesman).

Coding bootcamps are embracing React as well. Since most of these institutions survive year-to-year based on how well their placement numbers are for graduates, they are paying close attention to the trends in development. One could argue that since they are probably more technical than the average recruiter, they may even have a better grip of the pulse. FullStack Academy, of New York and Chicago, recently wrote a blog on why they're moving their curriculum from Angular to React (https://www.fullstackacademy.com/blog/angular-to-react-fulls...). App Academy (SF & NYC) has had React in its curriculum for a number of months (https://www.appacademy.io/immersive/curriculum). And I've personally spoken with alumni of Hack Reactor in SF who said that most students built their capstone project in React (or attempted to).

Is React the best solution? That's arguable, as all things are. It also depends on what you want to accomplish. But for the relevancy of this post -- asking what tech skills people will be hiring for in 2017 -- I would argue that React is going to be one of the top skills. And with that includes...

Redux
Webpack
Immutable
RxJS

As far as backend, the top three technologies that we've seen with our clients are:

Python
Go
Docker

But of course, all of this is moot without the foundation of strong JavaScript skills. Our students who have strong JS skills pick up React quickly -- those who don't only get confused.

Anyways, if you are skilled in React and other related technologies and you are looking for work, you can always email me: ben at realworldreact dot com with some info about yourself and/or your resume.
There are modules that you can use to make node work for CPU intensive tasks. Search for WebWorkers.

The real idea is don't do CPU intensive tasks in the event loop thread.
OMG, Ethereum Is So Hard Forked
Ask HN: Resources for Communication and Listening Online
I run the tech department for a small non-profit with employees on both sides of the Pacific. Recently we have a number of new hires, or people who have never used remote communication tools in business, talking more frequently. This has lead to some unique challenges that they're not equipped to deal with.

Do you have any ready-made resources (blog posts, slides, videos) that might help staff use remote communication tools like Google Hangouts more effectively? I'm looking for both etiquette and culture type resources. My dream would be a comparison between 'real life' and 'video chat life'.

If nothing seems to exist, I'd also be interested in collaborating to create a resource like I've described.
My only suggestion is you should find a problem and build a solution. It sounds like you have a solution and you want to man-handle it onto a problem.
I should tell that to my iPad Pro 9. It can sit in my backpack for three or four day and go from 95% to 50%...
I think I read in a separate article (maybe the Fortune one) that you're focused on mid-market homes in the $250k--$500k range, in a few metro regions across the country.

Notably absent in the Bay Area. In hindsight this looks like a great move since your value add to sellers is liquidity, and you collect an illiquidity premium, so to speak. Meanwhile, the Bay Area sellers are certainly not lacking in liquidity.

So 2 questions:

1) In hindsight staying away from the Bay Area looks great but I have to think there must have been a temptation to be a player in your "home market". What was the conversation like between the founding team to eschew the local market? (I think many companies default to addressing the Bay Area first without putting in much thought into it, and it is sometimes ill advised)

2) Blackstone was buying lower end homes from 2009--2014 or so. Is the transaction volume in this segment not robust enough for your business model (i.e. hard to find buyers)? Pricing model too uncertain/unpredictable?

I think we had coffee once back in 2013 when you were still at Addepar. Congrats on the move; always thought this could be a tremendous business since news first broke about the company.
Inside India's big Twitter hacks: Legion group makes more, bigger threats
I've always liked Alas Babylon by Pat Frank. They focus on food, and it really captures the terror the people were feeling and how a community might end up forming.
Did I need another reason to loathe Uber? No, but reasons keep showing up.
So if they are delivering 30k a second per box and the max "backlog" you allow to build is ~50k, then you cap your backlog at under 2sec worth of delivery? Or am I missing something?
"It's a hard problem to determine the repeat purchase cadence of a product."

I don't think it is.
thank you. i didnt read it with that context
Extremely simple blockchain in Node.js for starting the first step
If there was a good point to this poorly worded rant I couldn't stick around long enough to find it.

The evidence given for our intellectuals being clueless is the low replicability of psychology and pharmaceutical studies, and no thought is given to the fact that maybe, this stuff is hard, and maybe it's exponentially hard to keep up the exponential progress we've seen.

Maybe people are trying hard to work on hard things to help others, and they get righteous articles deriding them as elitist hacks for their troubles.
Ubiquiti is the best. Their stuff rivals and even beats lots of the more expensive stuff at a fraction of the price. It's all very high quality but so cheap that you think they are joking when you see the price.

Edge router: amazing

Edge switch: amazing

AC access points: amazing

I've never tried any of the unifi stuff though.
Writing the same amount of code is OK.

Doing one round-trip instead of several, no matter how deep and complicated your data tree is, may be the interesting part.
Windows 10 ISO 2017 Edition X86-X64 Full Version Download
s/pass/skip
Just remembered -- FirstREX does exactly this. Equity financing of homes, and selling off their stakes in collateralized fashion to institutional invsetors.
Preliminary injunction against filtered movie streaming service VidAngel
If it's worth anything, this southern Californian thinks very highly of TU Delft. Their product design course on edX was a great little introduction to the field, and the only MOOC I've actually seen the whole way through!
The first gig came to me. The second was a result of the first. And it goes on from there. If you network then someone will approach you to help them with some code. Do a great job and the second will start. After you do a few, then worry about sales and marketing.
Except for the people who get fat without eating almost any sugar and just eat plain old starches. Not everyone enjoys sweet things.
Most people don't agree with libertarianism. That's basically it.
Advertising is trained against ROI, not against what will "seem right" to the user.

Maybe in-market* furniture shoppers tend to spend a lot of money. Maybe furniture is a very profitable category. Even if the system is smart enough to assume there's only a 20% chance that you're in the process of significant furniture purchases, furniture ads may still be a better use of the ad slot than a lower value item where you have an 80% chance of being in-market.

Then why show the same damn coffee table over and over? Maybe that's more likely to return your attention to your furniture purchasing? I have no idea. Most likely, they don't know exactly either. Most likely, that's just what the highest-scoring current algorithm decided.

*The duration of "in-market" varies by category. Some product categories have a long consideration phase. For example car shoppers tend to spend 2-3 months considering alternative brands and models before they spend a few weeks narrowing down on a specific car configuration and exact pricing.
People are idiosyncratic, and not only that, dynamic. For many things we'll always find exceptions. What matters is understanding solutions that (a) work for many people and (b) work for each individually. Those solutions aren't necessarily the same.
I don't necessarily buy being blocked by CPU-intensive operations as a rationale as to why you shouldn't Node, given that it's pretty trivial to offload these onto a separate process.

https://github.com/LearnBoost/cluster - one I've used
If you look at the demos, it looks like you can do RBAC security. The user id is stored into a session (transaction?) local variable, and then used to filter various tables using postgres' row based security model.
My opinion of Apple is about the same as it was two years ago. My confidence in that opinion is much solidified. The ship is tilting, the fruit rotting.
Can you IPO so I can invest?
How can you know a seller is telling the truth RE: matters that are hard to validate in an inspection, e.g. terrible neighbors?
Ask HN: How do you document server installs
Good day HN,

I'm sure everyone here has set up many servers (or VPSs, VMs, etc) over the course of their work and/or side-projects/hobbies/personal rigs. I do a little bit of both, and am struggling to find a consistent way to log or document the whole process.

What do you use to document these setups, specifically:

* Versions of installed packages / method of installation
* Config file changes
* Setup commands/scripts run
* Deployment commands
* Custom scripts/changes
* Order of changes
* Information from vendors/maintainers covering niche cases/installation issues

Especially if it's a non-trivial setup (or the first time you're doing it), how do you keep track of what the final working approach was, the order of installation, etc?

Typically, I use a wiki with lots of links, and copies of any custom scripts I made, but it's not a comprehensive solution, and possibly error-prone.

Bonus points if your system has a way to easily redo all the work you've done (puppet, chef?).

Thanks!
Who still does that? I know American Express used to offer one-time CC numbers, but no longer does.