skysight-inc/HackerNews huggingface dataset:
U.S. is number one but the kind of welfare path it has chosen it remains to be seen when the real sinking of US starts.

The case with China is slightly different. They are not a democracy and hence can afford to spend lot more money on tanks and nuclear warheads while millions rot in poverty. This is not possible for a country like India. So as Chinese economy grows its global influence is going to grow more exponentially than say that of India. Countries who become global powers try to impose their worldview on others for example US has pushed democracy everywhere and I am reasonably sure China is going to put "state knows the best" attitude everywhere they go.
Here's an animated gif: http://gizmodo.com/google-changed-its-logo-this-weekend-and-...
It's a dreadful article, just overwritten adolescent FUD pandering ot he biases of readers.

At the extreme, though, with an evenly-distributed network of security cameras, you could track one individual's comngs and going and activities by aggregating Kinect-like motion/gait recognition across a (theoretical) array of always-on cameras. Realistically pulling data from people's phones already delivers 90% of the same capability, but this could track you when you leave your phone at home.
1.
Sure. My point is that I should have the right to choose what's in my interest, rather than have a company tell me what's in my interest. At a minimum, companies should explicitly say exactly what they are doing with my data. That's part of our agreement, after all. I use DDG for this reason. Actually I'm not super-happy with DDG in this respect: I believe there is some shady blurring of their promotional message vs the small print. But I would rather support DDG than Google, for now.

I don't think DDG needs to or should be catering for the people who find a lack of super-personalised results deal-breaking:

a) the world certainly doesn't need DDG to ape Google. There needs to be more competition in this space, and DDG's position distinguishes it. I hope and believe there is a market for a variety of search engines (as there are around the world).

b) in blind-testing, I'm not aware there is any evidence that Google does better.

2.
I hold out hope that the EU data protection principles will one day be properly upheld within the EU. I have no such hope for the US government.
Data Visualization and D3.js Newsletter – Issue 80
You don't intentionally build an automated way to take down all your servers at once.

You build a way to automatically perform some mundane standard procedure, like propagating a new firewall rule to all your systems at once. Then you accidentally propagate a rule that blocks all inbound ports. Huh, when I tested locally I didn't notice that.

Or you build a way to automatically delete timestamped log files more than a month old. And when it runs in production, it also deletes critical libraries which have the build timestamp in their filename. Ah, the test server was running a nightly build instead of a release so the files were named differently.

Or you build a way to automatically deploy the post-heartbleed replacement certificates to all your TLS servers, and only after you do that you find you didn't deploy the replacement corporate CA certificate to all the clients. Hmm, the test environment has a different CA arrangement, so testers don't get the private keys of prod certificates.

Or you build a way to retain timestamped snapshots of all your files, every five minutes, so you can roll back anything - then find that huge log file that constantly changes gets snapshotted every time, and everything is hanging because of lack of disk space. Oh, production does get a lot more traffic to log, now I think about it.

Or you do any of a hundred other things that seem like simple, low risk operations until you realise they aren't.
NPAPI is bad, bad business, and wouldn't fly for a second today if it weren't grandfathered into browsers.

Agreed, but I still don't see a reasonable replacement for it. PPAPI and NaCl don't fit the bill, and even if they did, no one implements them but Chrome.

Chrome is the IE of the '10s.
Comparing "the US" and "China" is comparing apples and oranges. China, like the rest of East Asia and most of Europe, is an ethnic-based country, whereas the US, like Australia, Brazil, and even the UK and France, is an immigration-based country. Generally, Americans don't become Chinese, nor would they want to. That's the key for why the US will remain tog dog. Of course, there's other factors: the US military control of the world's oceans, and the under-utilization of the Mississippi compared to the Yangtze or Ganges. Talking about China's skewed population distribution or lack of innovative freedom are effects, not causes, of the ethnic- or immigration-based nature of the two countries.
There are keysharing protocols; you can do something like 5 sysadmins have a split of the master key such that any 3 of them can access the master account.
I feel bad for the person who made the mistake. Even though its obviously a systemic problem, and highly unlikely to be an act of negligence, Im sure he/she doesnt feel too hot right now.
Those capabilities (at least the new ones—old SpiderMonkey JS extensions notwithstanding) aren't exposed to Web content.
People probably don't want to hear this, but I think the anti-trolls are winning on technicalities. In many cases a reverse DNS lookup can determine the proper jurisdiction. Improper joinder can be solved by just not joining defendants. Prenda may be making simple mistakes but Malibu appears to be learning from them.
I do not. Sorry.
Why iron.io over cron?
Facebook moves fast. I'm not saying that they're going to abandon Hack or give it away to Apache or something, but if I were a corporation, sticking with vanilla PHP is attractive because it has a large developing body, and it's future isn't dependent on the whim of one company.

Otherwise, yeah, Hack is an improved PHP. To be clear, it adds additional functionality to PHP, but is still entirely backwards compatible. PHP >= 5.4 still has solid bones.
I get this:

`<class:Server>': undefined method `using' for Knod::Server:Class (NoMethodError)

Am I a loser?
This would be more useful to me (as a hiring manager) with something that encouraged better links to somebody's accounts / portfolio / etc. instead of just their usually-empty HN profile.

e.g., I'm currently looking to contract somebody for some devops work here at Mozilla Research, and going through the set of listings that have 'devops' in them and actually finding a link to a resume / github account / anything more substantial than a twitter feed is pretty maddening.
wiresurfer, don't understand why you were down voted into oblivion, but now I can't reply to you. Anyway, massive thanks for that, really helpful starting point
Don't know, don't care.

I find debating whether the ship struck the iceberg on the left-hand side or the right-hand side a bit of a distraction from the effort underway to board the lifeboats.
From a very practical point of view, webOS is/was webkit based, while we obviously wanted to leverage our own rendering engine (gecko). webOS also is not 100% web technologies (the "window manager" is native code iirc), and overall we had different ideas on how to improve the web platform to build an OS.

I don't know much about Enyo, but one important thing is that we think that no framework should be needed to build apps for firefoxOS. But I'd like to know if enyo apps can run on fxos. The UI of the phone itself (called gaia, https://github.com/mozilla-b2g/gaia/) is pretty much framework-less.

webOS didn't make it as a platform for various reasons: lack of devices, no strong community for instance. Mozilla is in a way better position here.
Deep learning for natural language processing and related applications
From what I've gathered, it's run in production, just not the production environments this community usually hears about. There is pretty much no web ecosystem in Common Lisp, which is what I'm trying to fix, but in other domains it fits just fine.
I liked the ExtJS4 implementation most.

They kept the data in a div with hidden overflow so you could alway see header and footer (not that useful for mobile).

But they also deleted old nodes when they were far enough away from the visible space in the div.
Make sure to download the 146 page PDF linked at the end of the article.
Also, even if this paper were written before the plane was found, this N=1 example would not be strong proof that the method at hand works.
I wrote this:

https://github.com/cjbarber/hipchat-alternatives/

I while back.

This move by HipChat makes me happy.

I've attempted to move over, but HipChat is far superior for my needs.
No, I don't think it did, or if it did it was in the fine print and I didn't notice it.
Pierre Joye from Microsoft started a big refactor in the open (make string length size_t everywhere) meanwhile Dmitry Stogov of Zend worked in total secret on an even bigger refactor which is phpng, completely ignoring the size_t work (also known as 64 bit). A feud in PHP Internals followed not the first heated debate there... that mailing list is very useful as a textbook example of how not to run an open source community. At the end, Pierre have decided it's better to cooperate and now http://news.php.net/php.internals/74352 there's a vote that seems to pass and so on top of phpng size_t is also coming.
Hack is nice. But right now is only backed by Facebook. PHP is backed by a bigger community.
I guess hack is not backward compatible with some older php code.
Particularly code that mingles php and html together. For a lot of us this doesn't matter (frameworks and templating engines), but a lot of tutorials mix the html and php.

Most frameworks work with hack now, so your right it would be easier if there where just 1 version of "php".
I don't disagree with you. ;)

Its a fair point that visualizing branches makes a big difference to people learning git. One reason that all git intro articles have these A->B->C diagrams.

FYI, the git CLI can give you branch visuals, e.g., 'git log --graph'. I was honestly thinking beyond basic branching when I wrote the above, but its worth remembering that the basics matter, and I also wouldn't even disagree with someone who claimed a GUI branch graph is easier to look at than a CLI branch graph, even though there may be no informational difference.

Still, I think the larger points I was trying to make stand:

- There is no git GUI that can replace the git CLI. There are many GUIs that give you pieces of git's workflow, but none complete enough to be a true one-stop-git-shop -- especially when it comes to more advanced workflows & repo administration.

- Git was not designed for a GUI, it was designed for a command line, and it shows in many ways. The CLI is the only place you can use all of git's power and understand all of git's features. It's also, as wildlyinaccurate was trying to explain, the lowest common denominator interface, hence the easiest to start basic explanations with. All people who have git have a CLI interface. Written with any GUI in mind, and a git tutorial immediately loses the majority of its potential audience.
I'll let shanselman's response to your first sentence stand on its own :)

Regarding other people, certainly many are worth following. It'd be remiss not to mention Erik Meijer's group or the work done by others in MSR. They make for great Channel9 videos and great papers when they publish. But when I go to or watch a MSFT conference, those 3 are the top names I look for. Fair enough?
The way I see it, the CLI stuff is a distraction, when you "want to learn git", what you really want to do is understand how a DAG can be used for version control. Git is the idea. The standard/stock CLI is just one of many imperfect realizations of the idea that is git. Getting the handle of that particular realization of git is an unfortunate distraction that is needlessly weird in some cases.

Think of it like the difference between learning how an engine works, and learning how [some particular engine, in some particular car] works. The first is pretty simple and illuminating. The second has lots of annoying details and imperfections. If you want to work with cars, you learn the former first.
For day-to-day maintenance of systems, that's crippling. If I need 2 cosigns to run "date" across the fleet while I'm troubleshooting an NTP issue, and then 2 cosigns again to run "service ntpd status", and so forth, my coworkers will have lit my desk on fire long before I fix the clocks.

There are definitely use cases for keysharing systems like you describe: if we're talking about getting access to a database with sensitive information, or signing a new cert that all our systems are about to put their full faith in. But for the day-to-day administrative efforts, it's overkill and ends up being counterproductive: after a certain point, Alice and Bob write scripts that let them hotkey signing off on my requests.
Iron.io has 3 functions: the scheduler, the queue, and the processing/worker platform. CRON would just be the scheduler part of that and you'd still be left dealing with where to host workers, how to scale them, manage/monitor, etc.

IronWorker (and IronMQ) automates a lot of this operational overhead and makes it easy to just focus on your worker code.

Also when it scales, you can have hundreds, even thousands, of workers running in parallel.
Yeah, for the record, I've never heard of 4 Hour Body.
Zappos is an unconventional company run by an unconventional CEO, Tony Hsieh. You can read an earlier interview about his hiring strategy[0], take a look at his office[1], and read about his plan to turn around downtown Las Vegas[2]. An unusual man, but unusually effective.

[0] http://www.nytimes.com/2010/01/10/business/10corner.html?pag...

[1] http://www.nytimes.com/2013/12/29/business/tony-hsiehs-offic...

[2] http://www.nytimes.com/2012/10/21/magazine/what-happens-in-b...
Could someone explain to me what appeal is left to Bitcoin once you get rid of anonymity?

There must be some, given all the trackable-as-dollars implementations I've seen lately, like the Bitcoin debit card and this, which is actually less anonymous than dollars (since you're sending under an account that has your real name per the Facebook TOS).

From my naive standpoint, it seems like you're exposing yourself to a lot of value volatility and to a relatively complex and uncommon processing system. Why not just use PayPal, Stripe, whatever?
I was wondering this as well. Does Netflix already support playback without Silverlight on Chrome using a <video> CDM?

What is going to happen to Java applets? You must use a different browser?
Oh man, search for "married sophisticate" and read the "day in the life of" section for the group.

I wanted to kick someone's ass so badly after reading that.
I have this and youtube history turned off because both use broken machine learning to try to interest me in nonsense I don't care about each time I search for something.

Example: Yea I clicked on the "Oprah gives a car to everyone" video, but right now I'm trying to watch videos relevant to PHP security, and I don't care to see talkshow outtakes in the "related" sidebar.
NPAPI plugins are already ActiveX in the browser by your definition: technologies controlled and pushed by a single vendor. In fact, they're even more like ActiveX than NaCl is: they're generally closed-source, vulnerable to a wide variety of exploits, and in some cases not even cross-platform (Silverlight, for example, is a closed-source Microsoft product that "extends" the web and is not released for Linux). Moving to NaCl is better in those senses than NPAPI-based plugins: if the plugins are written in NaCl, they'll at least run on every major OS, and be sandboxed safely.

And NaCl isn't the only recourse for previously-NPAPI-based plugins. It's just the worst (for the web) choice. Better is to build the plugins on top of JS, which some vendors are already doing: for example, the announced future of the Unity on the web is compiling to JS.

Non-web-technologies (like the current iteration of NaCl) intruding on the browser is bad for the open web. But plugins are also bad for the open web, and deprecating them is better than not deprecating them. You can't fault the Chrome team too much for closing one door just because they left another open. :)
Add "Marshall Hayner" on Facebook and I will blast you some bits :)
Photopea 0.8 – edit PSDs in a browser
what about dependencies in the workers?
The oroblem with non-whites not quite fitting in is real, though, and much worse than in the US. Besides color, muslims are pretty hard to assimilate, so there will be not only color-based racism but also cultural ethnocentrism.

Imagine you have the problems of economic class and then add another dimension of cultural class. Society becomes much more fragmented. The new dimension is not really worse than economic class, but class alone is already unpleasant. It will turn out all right, I guess, but there will be minor persistent problems for a long time.
Our internal culture is such that everyone on the team would rather be blamed for something than accuse someone else of doing it. That's shitty, and not something you do to someone. You fix the problem and then you move on.

If it makes you happy, blame me - I don't mind.
Did you get internships? I did an internship every year at my school and their network helped me get them. Network doesn't just mean knowing people from the school after graduating, it also means leveraging it to get ahead while you're still in school.
You're going to need a bigger crew.
Your wallet and the private key it uses to sign your transactions are generated in your web browser. You are free to send to and from any Bitcoin address.

Your wallet is only associated with our services by signing and submitting a token that proves it owns the associated public address.

We are exploring ways where any Bitcoin private keys can sign their own token and register with our infrastructure. This process would require the cooperation of other wallet software creators but we're sure a standard will emerge at some point.

We would like to have some form of two-factor authorization in place before we expose the private keys to the user interface. Right now the private key never leaves the warm embrace of a function closure inside of a web worker and well out of the global scope of the DOM.
Consumer Expectations
PressOcean, a startup that aims to disrupt PR industry, is in private beta now
I think that's true for anyone aiming at being healthy. I'd say that eating meat and not having any nutrition knowledge is even worse. If you don't know anything about nutrition, sticking with fruits, legumes, grains, nuts, seeds and greens is a pretty safe choice.
This is most likely the reference you were looking for:

http://blog.bumblebeelabs.com/social-software-sundays-2-the-...
Sure, if you only want to run code on 64-bit linux.
I believe you were down voted not for what you said, but the way you have said it.

I've been down voted several times for (what I see) as relatively minor remarks. The HN readers are a sensitive bunch...
I think a lot of people have, privately at least. My guess for why they are still around is the fact that they have literally become a household name and have the infrastructure to back it up.

As far as technology, you hit the nail on the head. A simple Android / iPhone app could literally replace all 5 boxes. I gasped when I heard they are still using modems, jeeze.
I can't speak for HT specifically but dependency management is fairly straightforward. You can include any gems or libraries in your worker code package. If they contain native extensions, we'll compile and package them in at the time of upload so that the worker can execute at runtime until the next time you change the code and re-upload.

More information here: http://dev.iron.io/worker/reference/builds/
I think a big advantage of something that accepts bitcoin through something like this is that even though the "normal" case is the same as things like paypal/stripe, it means that the backend supports bitcoin and can easily accept "raw bitcoins".
I guess tomjen3 was thinking about a badge for himself :)
Depending on the program, the quality of your instruction can be vastly different from college to college. While an elite college is not a guarantee of a good curriculum, or better teachers, those colleges are more likely to have better programs (but you can definitely find less prestigious colleges with great programs too if you know what to look for). I always double check a universities curriculum to get a general idea for quality, and I've seen them vary greatly.
Responding Rationally to a Tragedy
"What's this button do?"
Agile Methodologies – part one
Haha, well, not unprompted / with no context; that would be pretty rude.

I was thinking more like if you already knew someone was trying to lose weight, or if someone were already on your case about eating a high-fat diet. In my case, a bunch of people have been asking me how I lost such a ridiculous amount of weight since they'd last seen me not much long prior.
This isn't about trying to defend iCloud's teething problems, so these links are irrelevant.

Yes, there are risks associated with using a 3rd party service. However if you don't use one, you are claiming that you can do better in architecture, implementation, and DevOps.

How many apps do you have? Let's say you have 30.

What percentage of the developers of these apps do you think will do a better job of sync than Dropbox or Apple?

Unless you think that number is in the high 90's, then your advice is a severe disservice to end users.
Don't worry, it's already happening in big ways.

http://krebsonsecurity.com/2014/05/experian-breach-tied-to-n...
UCSC tuition & fees have more than doubled since 2004:
http://www.collegecalc.org/colleges/california/university-of...
(And they had already increased by 41% in 2004.)
In other words, you agree that iCloud's attempt at vendor lock-in is bad for developers and consumers alike.
> Agreed, but I still don't see a reasonable replacement for it.

A reasonable replacement for it is for browsers to just expose appropriate functionality through JS APIs with appropriate security provisions and continue to optimize their JS engines.

Which is happening.
Same here, I disabled it, but they turned it back on apparently.
Ah, that must be Google Docs messing up my normal ascii quotes (I had a similar issue with some characters on my Android phone earlier). Thanks.
BTW, this is the right way to do it. :)
> hubot restart all on prod

oh shit i meant stag
fuckfuckfuckfuck
Surprisingly links to laut.fm can again be posted on Facebook. Less surprisingly Facebook did not tell us why that happenend.
I am the engineer at Facebook responsible for this mistake - my apologies, and I've already fixed it. The domain was blocked due to a false positive on one of our automated classifiers used to fight spam. While we strive to have 0 false positives, some do happen. We are investigating how this happened in the first place and will be adjusting the classifier accordingly.
It's true (and great!), but you can't see two conversations from two different organizations at the same time - have to click.
I think I'm more worried about erroneous correlations from collected personal data than the leak of the data in the first place.
The Android version has not been amazing for me. It crashes several times a day, switching rooms is clumsy and slow, and the push notifications arrive minutes after I've already replied to a message, so the phone is constantly buzzing for things I've already replied.

Additionally, there's no native Windows client.
Curate the Internet on #ZEEF
We're hoping that people will grow accustomed to having their Bitcoin shared across a number of different wallets and services.

We are not expecting people to keep any more in their wallets than they would with their real wallets.

Currently we recommend cold-storage for long term savings. We think there is a lot of middle ground for exploring different kinds of security and access privileges and how that affects the liquidity of your bitcoin.