skysight-inc/HackerNews huggingface dataset:
The thing that concerns me the most is that I still remember how our former socialist government curbed criticism and it was pretty much entirely through non-state actors - critics and "undesirables" found them selves out of their jobs, their children got scholarships denied, landlords suddenly didn't want to rent apartments, reporters found themselves fired for gross negligence, funding (both governmental and private) for academic institutions housing critical scientists just disappeared. At the end of the day it mattered absolutely nothing WHO was the actor - expressing opinions against the party line could threaten your livelihood, your future and future of your children.

Because of that it's utterly terrifying to me when I see those notions here on HN - it seems like visitors on this site know very little about history of the 20th century and the reasoning for many ways how modern (supposedly) free states are set up.

Note that that's not to say that people cannot be criticized for their opinions - but there's a difference between criticism and attempting to destroy someones career and ability to join social circles. It's a blurry line, but still a line. It's the difference between politely shutting up your racist homophobic uncle on a gathering or demanding that his pension is revoked.
Generally:

- 79$ (solve a business problem and its worth it. There's no difference between 29 or 39 or 79 for a business user with a credit card.)

- $399 (basically max to buy without approval if you're a manager, anything below 500$.)

- enterprise (aka call us, you'll need approval for this internally.) You could add a 799 plan here, or a 1999 plan, etc.

You want to stay away from 9$ and such unless you're selling to consumers, not businesses, in very high quantities (eg. you're netflix).
> I'm not downplaying their work—it just really, really, really is not the same thing.

The methods might very well be different, but the result is the same.

Pretending that you can't do server-side rendering with React is not helpful and untrue. Just because they haven't put the same work into conventionalizing it does not mean that analogous initiatives don't exist for React.

There are plenty of guides and tutorials out there showing how to do server side rendering in React.
That command would just be `fly` or something else coming from Concourse. To me it makes more sense for the entry into the system to be safeguarded with validation, and then possibly bring your own filesystem-based configuration management system that goes through that same front door, building on trusted tools from Concourse itself. Mucking with files on disk that directly affect a live system (shipping production code!) seems like a recipe for disaster.
What's wrong with that worldview? Seems like the only issue is employers and landlords (??) overreacting. Why shouldn't someone be able to say "No soup for you 'cause I think you're an asshole?" Or why shouldn't I be able to not want to work with someone because they think npm did nothing wrong?

I find it troubling what people get upset about these days. But it seems entirely their right to be upset about whatever they feel like. And others' right to mock them for it.

It's disappointing that platforms like Facebook and Google don't seem neutral (the latter two taking steps to prevent gun sales). But until they're regulated it seems entirely OK for them to promote their own views.
Parenthetical is my point exactly. In practice, this would require them going to court themselves, which I don't expect them to do.

There are also many legitimate and well intentioned possibilities that could lead copyrighted, unlicensed code onto NPM in which case they would have no right, regardless of their ToS, to redistributed it.

I don't like the law, but it is what it is, and I wouldn't expect NPM to actually back up their new official policy if push came to shove, because as soon as they try to they lose safe harbor.
Oracle wants $9.3B in damages from Google
Greg Duffy on the Dropcam Team
While I love Ember, one of it's biggest downfalls is definitely has a longer ramp up period, and more complexity than other frameworks. Ember's documentation is very good now, but still, there is a lot you have to read (and eventually experience to truly understand) about how ember works under the covers.

One of ember's greatest benefits is that it adapts to change and doesn't miss out on features for very long at all (you can look at fastboot as a reaction to isomorphic react apps, or something that the ember team would have just pursued anyway). However, that benefit can also be a pitfall for newcomers to ember as it's hard to find consistent discussion, help, and resources for a framework that changes so fast.

BTW, while Ember CLI makes things much easier, it does not improve the complexity situation, it just becomes one more thing you have to learn when learning Ember (even as a newbie). What if a newbie isn't familiar with node? what if they're not sure why you're precompiling? what if they're not familiar with task runners like grunt and gulp?

Contrasted with frameworks like Angular 1, Backbone+Marionette, Ember definitely has the most rampup and complexity, not the least.
The overwhelming majority of the traffic we've seen so far has been Chrome and Safari, even from HN.

That being said, that wasn't necessarily the driving factor in the "use the fancy selection APIs" decision. There were many factors, but for one thing, choosing to use those APIs, while limiting our browser support (for a limited amount of time) helped us get to where we are now at a quicker pace than if we'd opted for much broader browser support from day 1.

One of the challenges here for Firefox is that there's not an API to determine when a user's selection changes. We need this in order for inline markdown to collapse/expand as the cursor comes within proximity of it. It's definitely possible to poly-fill this, we just haven't done it, yet :\ We could disable this for Firefox, but I'd rather ship Firefox support with the rad stuff that the other major browsers already get.
What about those of us who aren't US citizens? SOOL?
Its as if the system 'wants' people to suffer.

It's as if "the system" knows that without fracking, oil sands, and enhanced oil recovery technologies, with conventional crude and gas having peaked a decade ago, we would be facing a fairly significant energy shortage today, and an even worse one a decade hence.

Everyone wants to eat the bacon but nobody wants to butcher the hog. Energy supply is THE NUMBER ONE THING that enables modern civilization to repel entropy as well as it does. We, as a species, will do whatever it takes to ensure the energy supply remains. We will accept climate change and poisoned water because the alternative, short of a miracle in solar capture, is the death of several billion people.

The Spice must flow.
If it's out content you are uploading, you have the right to license it however you like in addition to the license you release publicly with. For example, there is nothing stopping you as the owner of GPL software from also selling commercial licenses. As such, requiring that NPM is provided specific capabilities does not conflict with any license, so long as the owner of the code is the one uploading it.

Put another way, the license you ship with your code for usage by end users is not necessarily the entirety of the license NPM is bound by if you use their service. There's nothing really special about this, dual licensing is used all the time.
> There just isn't really a good way to do this in/with NPM, and the top google results seem to actively discourage pursuing this pattern.

There is. The only problem is fetching packages from a central registry (registry.npmjs.org). The rest that comes with the NPM CLI is good stuff.

One way, that I have been exploring is to allow NPM to download from IPFS instead, available over at http://everythingstays.com, and that's just one way it can be solved.

The top-level comment have more tools that you can use (but doesn't seem to have been implemented yet)
Reading this article I find myself thinking again how unhappy I am that
a neural network won Go. I am unhappy because neural networks are not smart. They're
the epitome of artificial stupidity: they learn, but they don't understand
anything that they learn. They can't take what they learned and apply it to another
domain, not without training again. And every time you train one in a new thing, it
forgets all about the old thing. They got intelligence alright, but it's the
dumbest kind of intelligence possible, mechanical, unaware of itself and devoid
of all purpose other than what we give it.

And what about ourselves? Building AlphaGo is a feat of human intelligence, but
how does it improve that human intelligence itself? How do we become smarter? We
can build machines to solve problems that we don't understand, but they solve
them in ways that we still don't understand. Except- we're not even trying
anymore. We've given up. Knowledge is hard. Logic is hard. Just throw a bunch of
GPUs at the problem and make it go away.

Far from this being a promising time for artificial intelligence, I fear we're
about to see a great dumbing down as funding is cut to everything but neural
networks research. A kind of AI summer, as it were.
As someone who is not aware of what is all the problem about and couldn't really understand from the linked text, can someone provide me with some more context please. What is the difficulty that is affecting lambdaconf? What happened?
It seems you vastly overestimate the citizenry; there is a great deal of evidence that elected representatives listen when their constituents have a strong view, but the citizens rarely bother to take a side.
Full Disclosure: I also work at Pivotal on a team that has done a large amount of automation using Concourse (check out our pipelines [1])

Things that we've done so far with Concourse:

* A dependency check notifier that based on an RSS feed from various language maintainers: Sends an email, updates our pivotal tracker account, sends a message to our slack channel

* A job, that based on the completion of a build will upload the resulting artifact to Github and tag the release with a new version, auto generated release notes and checksums

* Travis.ci style github pull request analysis

* A security feed monitor that notifies us when a part of our application is vulnerable and when it is, kicks off a build and sends an email notification

* Automatically updates submodules and gems for git repos and runs specs and tests against the updated artifact.

These tasks were not difficult to implement. Every pipeline for Concourse is explicitly defined in its configuration file [2], which we version control. There is never any reconfiguring or rebuilding "snowflake" servers when we re-deploy our Concourse VMs. They rebuild identically based on the config files.

[1] - http://buildpacks-ci.cfapps.io (Chrome friendly, Firefox not)

[2] - https://github.com/cloudfoundry/buildpacks-ci
If each member is responsible for a different part of security, then you'd still want each to be as strong as possible.

It just occurred to me that diverse could mean "skilled in different forms of security", and then it's just saying to hire domain experts in as many security domains as you can. That would make diversity a direct solution to the weakest link problem.
Of course, the Keynesian policies that have failed China will also fail the US and the EU.

I do wonder how many times the Austrian school will be proved right before the public start to notice.
Yes, via "Houdini": https://github.com/vito/houdini

Concourse uses the Garden API to manage containers. Houdini is a "no-op" implementation that just tells Garden "yep, I've got your container right here".
I too was expecting a minor child, not a young-ish adult.

I don't feel like checking it now but Linus was pretty young too when he released his kernel.
Android Wear watches go chrono-a-chrono with Apple Watch
Something like that. You could either have a little daemon that watches a file and flies it when it changes, or you could do it straight from the configuration management tool. For example, in Ansible you'd write a handler which is triggered after updating a copy of the pipeline file somewhere:

http://docs.ansible.com/ansible/playbooks_intro.html#handler...

The handler could use the command module to run fly:

http://docs.ansible.com/ansible/command_module.html
I am completely out of the loop on this guy!!! I can't believe it, other than this article what's the best summary of him??
Thanks for this wonderful essay! I love learning about that period in computing, when a lot of what we use today was first challenged. It's easy to see how those same principles apply to the GRaIL visual programming interface demo[1], where different strokes create different types of elements (boxes, outputs, connections, ...).

[1]: https://www.youtube.com/watch?v=QQhVQ1UG6aM
The python distribution story is far behind Go. This article goes into more details: https://glyph.twistedmatrix.com/2015/09/software-you-can-use...

PS: I'm the original author of PyInstaller. I obviously love it but it's a gross hack around the fact that Python doesn't have a serious distribution story.
Tilt (YC W12) Is Hiring for iOS, SySops, and Data Analytics
I wrote most of that page. :)
Thanks! As Zikes say, a little competition is good and gitlab is working out fine for me. I used to be on gitorious and it got bought by gitlab so I moved. I prefer being on a platform I can theoretically port.
> Paywalls are just a pay for access method for making money from content, and unrelated to the topic

I asked what the difference between a Firewall and a paywall is "from a user's point of view". At various times and in different ways it's possible to bypass the Firewall depending on how much you want to pay, e.g. using VPN's, using proxies though there's less of them around nowadays, visiting Hong Kong, getting friends overseas to scrape and email content, and the Firewall seems to fail periodically, not just from the Google change last weekend but often for a minute here, an hour there, for different websites.
This has me thinking about taking our new powerful AI models and applying them to much simpler problems. And then, making the problems much harder than humans could do. Why not two snakes and two food dots. Or 2*n snakes n food dots on massive higher dimensional boards.
Digital Publishers Want to Put the Web on a Diet to Fight Ad Blocking
As an Australian, an astounding amount of security product vendors use HIPAA as part of a worldwide marketing strategy, and never stop to consider that it's not a thing elsewhere.

Most of the standard desktop AV vendors have contacted me with taglines like "meet your HIPAA obligations today!". I can name Kaspersky, Symantec, McAfee all as having had really confused salespeople when you try asking them why an Australian company would have HIPAA obligations, often just replying to insist "it's actually the law".
It is trivially easy to poll it in an animation loop.
Hmm. I think that's a little confused.

You need to worry about running out of memory precisely because the abstraction is leaky. If you need to micromanage, it's perhaps not leaky, but it's also not much of an abstraction.

Exploring this example a little deeper, if our model is "we never run out of memory, but our program may stochastically die at any point in time", then that's not as leaky as "we never run out of memory", and our program may die for reasons outside our control so it's a good idea to be robust against those. But now let's say we need to send a request to a service, and the service disconnects when we've sent the request. With a stochastic model of failures, we clearly should just re-send. But if the problem was that our payload demanded more memory than could be provided, retrying repeatedly will just keep killing servers.

We probably want a model of "we never run out of memory, our program may die at any point in time, possibly correlated with inputs", which I would contend is actually not very leaky. We still spill over into performance, but most things spill over into performance...

I would say that leaky abstractions constitute debt relative to non-leaky equivalently powerful abstractions. They may still pay their way.
A chatbot is definitely not choosing each letter separately. It is not even choosing each word separately. It is likely choosing a phrase structure and populating with a fixed set of words. LSTM net may be going word for word, but letter for letter would give poor results. At the very least you need n-grams.
> Until you get used to the debugger, you will ask yourself this question.

As a counterpoint to this, I was pretty much exclusively a debugger guy for the first 10-12 years of my career. Now I'm pretty much exclusively a logging kind of guy. Familiarity with a debugger has nothing to do with it.

> Console logging is bad for recursive functions, loops, huge variables, etc.

And debuggers are bad for focus/blur event handlers in UI code because they change the focus state of the thing you're trying to debug.

Ultimately, neither of them is perfect, not all problems are alike, one is not an objectively better tool than the other. They both have merits.
It looks like they had six other sponsors before this kerfuffle: https://web.archive.org/web/20160321025225/http://lambdaconf...
I wonder what the trickle down people have to say about this. I thought the more money the job creators have the more they will invest.
>What's the difference between a Firewall and a paywall from a user's point of view?

5 stories a month.
Why I don’t commit generated files to master
"Kik" is not just a trademark referring to a piece of software. It refers to a very specific type of software. KIK Interactive, Inc. has described it in many words, but they are all somewhat similar to:

>Computer software for use with mobile devices, namely, computers, personal digital assistants (PDAs) and mobile phones for downloading, displaying, transmitting, receiving, editing, extracting, encoding, decoding, playing, storing and organizing text, sound, images, audio files and video files

The `kik` package was software that was used with other devices for other purposes.

KIK Interactive hasn't even been able to produce a specific Trademark that the `kik` package would have infringed upon.
>What I would really like to see is a big institution / university take a stand and build something like Scihub to provide free and unlimited access to all of their own papers, even those that are stuck behind a paywall for "historic" reasons.

The University of California has already done this.*

Unfortunately their policy does not extend to papers created before their policy was enacted, despite what they had originally claimed.*

* http://escholarship.org/
* http://osc.universityofcalifornia.edu/2015/10/groundbreaking...
I was analysing the robot and this zef prawn offered me a sweetie. Fook prawns.
Java vs. C Performance Presentation by Cliff Click
I don't think the system wants people to suffer. It just cares only about few people and the rest don't matter.
Security B: Vulnerability in IBM Domino Web Server TLS AES GCM Nonce Generation
Cowboy-style - puts/print/console.log all over the place.

I feel no shame.
> I have health insurance, so treatment for my bodily injuries is covered

No, that's not how it typically works. If the injury was caused by car accident, your insurer will likely deny the claim. This happened to me when someone rear-ended me and I went to the ER to get checked out; I didn't want to file a claim with the other party's auto insurance but had to for payment of the ER visit.
hmm, I mean, I guess there's no harm having it be stated policy. There are any number of hypothetical situations where I'd expect their lawyers to advise them not to follow that policy when faced with the threat of litigation.
Social Engineering Probably Led to MedStar Breach
Well, I’ve checked the prices, and dedicated servers from old-style hosters are still far cheaper if you’re going to query data 24/7.
I think this is a reasonable article about China.

When people think about China they tent to assume that China is somewhat similar to a western country going thru the afterwards of some sort of overheated boom. Say the US from 2002 to 2007 and the big recession of 2008-2010.

But China is not mature and developed like the west.

Sure the east coast has nice modern cities which look like the cities of any Western country. But large parts of the country are still poor, rural and remote. When construction goes on here, a modern road is built where there was nothing before cutting the transport time between two cities from 5-10 hours to 1 hour. Houses are built for people to work in the city doing high-productive factory jobs where they before were doing small-time farming in the country side.

This is a massive lift in real economic activity which can finance a lot of debt.

Completely incomparable to the expansion of credit to low-income families to finance housing that gave the boom in the US and other western countries from 2002 to 2007.

Secondly there is a now huge upper middle class who are travelling the world, sending their kids to Australia or US for study and still buying Apple products. They are not going away. And ultimately they will change China into something more driven-by-internal-demand, civic, modern ... even democratic.
Getting robbed, kidnapped, raped, killed, etc. - I personally had a "ghost" cabbie try to swipe my credit card data using a card swipper, demand to take me to an ATM, etc. - lucky, nothing "bad" happened; after the fact, called in his ID number and it wasn't real. This is a bigger issues in some areas, Uber first introduced a panic button in countries were cabbie attacks were a larger issue, but believe they're even adding it to some cities in the US now.
BusFactor1 – Filthy Gorgeous (2016) #Ambient #Noise #Soundtrack #Cyberspace
This is literally the situation that began all these events.
>No HomeKit integration, of course, now that Google has purchased them.

Probably completely unrelated since Nest doesn't even support Google's Brillo/Weave. They're going forward with their own "Nest Weave" which despite the name is a completely separate platform/ecosystem from Google's stuff.

Wouldn't be surprised if Homekit support is actually on the cards but it's stuck in their super slow release cycle.
Just get a device from Obihai and connect your Google Voice account to it. No monthly charge
LambdaConf is permitting Curtis Yarvin to speak, which offends the sensibilities of some attendees.
I think the CLI helps tremendously, even if you have to learn it (and for simple stuff you don't aside from `ember new` and `ember start`, maybe a few file generators). The biggest problem with beginners is setting up a JS environment—I've seen people waste hours doing it. Ember's CLI tool takes care of all of that.
I sincerely doubt much of their userbase will look at things so emotionally as to damage the company. Most of github seems to quietly continue ticking over no matter what the drama.
The maintainer could see that, due to the nature of the issue, maybe the user OS would matter. Or maybe there's another version on the horizon that changes completely the functionally in topic. A hand crafted reply asking some curated questions/suggestions is not the same from an automatic "not enough information".

It's not about typing, it's about making a conversation.
Was just about to start a new app in Angular 2 because it seamed progress on fastboot was slow now might need to re-evaluate.
Worse-- the insurer will deny the claim and make the patient go after the other person's insurance