skysight-inc/HackerNews huggingface dataset:
Very cool! This could be really useful for something I'm working on.

I noticed in the example queries on your site, the data that is returned looks like it is being piped pretty much exclusively from Amazon. For example, every image url is an Amazon url. Have you licensed this data from Amazon? Otherwise, any customers who use this info on their website are effectively ripping off Amazon's product data, and could be exposed to legal issues. For example, would it be kosher to download an image and use it on your own site?

I'm trying to understand the terms under which this data is being provided and whether it is worth it for me to buy a subscription to your service.
He needn't have spent a million dollars on top notch defense counsel to get a lenient sentence. By and large it looks bad to prosecute otherwise upstanding white kids for obscure crimes. If he'd played ball with MIT, JSTOR, and the DOJ from the beginning, he could've saved himself a lot of legal fees. But he didn't. As far as we can tell from the information we have, he wanted to fight it, to make a political point. Well, that sort of fighting is expensive.

As for "unspecified chance"--of course there is some unspecified chance of anything happening. You don't piss off the federal government and a key piece of the military industrial complex by knowingly breaking laws and then rest easy in the knowledge that there is zero chance of your getting in serious trouble. But based on previous cases we've seen, it's highly probable that nothing serious would have happened. Other young hackers who broke into networks but didn't cause any damage mostly got probation. Kevin Mitnick got 5 years, but for his second offense after spending 2.5 years as a fugitive.
Are you trying to say that kids always follow the religion of their parents?
Twipster
> That would be highly dependent on the quality of the company culture.

Bingo.

> You can argue that the former is useful to know, but I don't have ambitions of going the managerial route.

While there can be significant advantage in knowledge exchange, most of the big wins are from random moments of inspiration that come from interactions with people.

I think more importantly than that though, if you have a huge organization that has a dysfunctional culture you have a major problem of inertia that is only magnified if significant chunks of the organization disengaged from day-to-day interactions. Your odds of turning that ship around are tremendously improved if you have people interacting day to day.

By no means do I mean to let Yahoo's management off the hook: this decision is entirely the result of bad management, and I think upset employees would be perfectly justified in blaming poor management for the change. That doesn't make this decision a bad decision or one that reflects a lack of trust or respect for employees. If one has any respect or trust for employees, one ought to want to see them as part of the solution (something that I'd argue hasn't always been the case at Yahoo), and one ought to have the willingness to be take drastic measures to effect change, and be honest with them about what those measures are, in order to help the organization get out of its quagmire.
I started using Chrome in late 2010 and used it continuously until about 3 months ago. It started suffering the problem of tabs just freezing about every few minutes of browsing. This behaviour started happening around the same time on two different machines - one quad core desktop, another lenovo laptop. Since then I've gone back to FireFox, but this article is making me think I may just need to do a fresh install of Chrome.
It's incredibly appropriate that this appeal to manners and social mores would be posted by someone calling themselves, "pifflesnort."
In the beginning, there was Thistle. Thistle was, at best, a glorified regex that converted ASP to PHP. It was written by an intern, and it showed.

Later, Thistle was broadened out into an ASP to PHP compiler. Compiler was still a loose term; there was still a lot of regex magic that relied on you following Hungarian apps notation. That said, I'm fairly confident that this version of Thistle did build an AST for code generation, which does mean it qualified as a real compiler.

That matters because this version of Thistle was extended out with two additional features: it could compile VBScript to JavaScript, and it added some conveniences to VBScript, such as macros (called picture functions (don't ask)), lambdas, and simplifications to the declaration system. Don't laugh too much at the former; the motivation was the same as for RJS or Seaside's JavaScript support. All three technologies are dead now, and for good reason, but it was modish at the time.

Later, when .NET came out, and VBScript was end-of-lifed, that left us with the option of rewriting the whole thing...or making a "real" compiler that could compile VBScript to .NET. Wasabi was born. Wasabi was written as a proper compiler that could translate VBScript to C# and (for legacy reasons; see above) JavaScript. Wasabi, unlike Thistle, was a real, full-blown compiler, in a CS sense, so it was feasible to add type inference, lambda expressions, and several other niceties, without spending too much effort. That said, the goal here was to allow transition: new components, with restrictions, could be written in C#. The idea was that, at least hopefully, Wasabi would gradually be deprecated.

So no. It was never meant to be a new language. It was always intended to be a stepping stone, a translator between languages, not a real language in itself. While it gained some additional features, that was to make working in the damn thing palatable--not to be a real language in its own right. Emitting C# and .NET IL are actually about equally easy if you have a real compiler, but Wasabi always emitted C#, specifically so that we could one day ditch the whole thing.
I was replying to wting, but HN doesn't let me reply to a reply by the same author as a way to combat back-and-forth style arguments, I guess.

He said that experts doing that is "trained pattern matching gained through experience, i.e. machine learning."

But that's backwards: machine learning in this style is a model of something we observe in ourselves. The thing that's in us is the pipe, the machine learning algorithm is the picture.
Proud to be on the contributor list for this one - any of you considering contributing, it's not hard at all, the team makes it really easy.
Slightly OT, but the second image in that article is bogus. It's a photo of Fijian women on a Fijian mat (woven pandanus leaves). It's not Peruvian as claimed by the caption.
The evidence shows that there is no gender difference in how seriously people are taken in all professional situations? I look forward to you posting links.
If you fire the people who deserve to get fired you actually increase morale.
He could have also chosen not to enter an unlocked server closet...
A correction: the M1 Garand, designed before WWII, as issued originally fired .30-06; .308/7.62 NATO is a 1/2 inch or so shorter round, using much improved powder and a 147 vs. 150 or maybe 152 (Wikipedia) grain bullet to achieve the same exterior ballistics as M2 Ball I think. I've read that shaving off 1/2 an inch of overall length (the case was quite long because our powder in 1903 wasn't as good as the German's) allows decreasing the receiver length by about an inch ... but I'm now ashamed to realize I never measured them when I had my Garand and a couple of M14 semi-auto investment cast receivers "just in case" for legal grandfathering.

However, the gun will fire any round with .30-06 or .308 dimensions if the pressure profile is a good match. I had my Garand refurbished and rebarreled in .308/7.62 NATO, and it was quite reliable. The Navy started doing that sort of thing the earliest that I know of, with a sleeve fitted into the chamber (!).
Taubes has responded to the wholehealthsource critique (I have not read it, but it was referred to as a "thorough multi-part smack down"):

http://garytaubes.com/2011/09/catching-up-on-lost-time-ances...
I feel like we as nerds should think in the long term.

Communication should be controlled by the users. Think about all the companies who were screwed over by Facebook's "Likegate." Decentralization is why I prefer Tent and IRC. App.net seems acceptable as well because of the open nature, though it is centralized.
If testing psych students was smelly - this experiment is smellier.

Large amounts of cash = take whatever is offered.

Repeat experiment with a billion dollars. I offer you say 50 million, leaving 950 million to myself. Your move. You honestly going to reject 50 million?

It's actually quite rational that they took the money. Now, what would actually be interesting is that if they rejected the large amounts of cash.
Well, I used Safari before Chrome, came out... Firefox was dreadfully slow on my old computer. :(
Given the tone of the blog post and the various offensive remarks strewn through the post, it is likely that the author was being a dick on the plane and was given the broken seat by the flight staff deliberately.
You're a bit misinformed.

Both Joel on Software and Coding Horror readers formed the initial audience.

While Jeff wrote code for StackOverflow, and Joel did not, Joel provided and acquired the initial funding to pay for Jeff's work, and hired the other talent required to allow the site to launch. It was neither entirely Jeff nor entirely Joel's creation, and I doubt it would've been able to launch without both putting quite a bit of backbone into it.
I don't know, if it's true that their team is not very accountable and I was one of the top on-site folks I'd be relieved to see the dead weight go.
Have you thought about creating it as a Spotify app. Also have you thought of FB integration to add friends easily. Additionally once they have FB auth'd you could add in FB stories. There is always a careful balance with sharing, you don't want to be one of those auto follow sites or push to many spammy stories. It is amazing what people will share given the option. I like the site!
Shopify Private API's
App.net’s new direction
The first wave of accounts is up for renewal on April 14 — just seven weeks from now. So App.net has seven weeks to convince its early adopters that it’s worth paying more money for another year of service.

I'm pretty sure this is incorrect. Those of us that signed up for the $50/year deal got our subscriptions extended when the price dropped to $36. My renewal date is April 9th 2014 (i.e. more than a year away).

Setting aside that piece of nit picking, Marco's completely right that in order for App.net to be useful to both end users and developers it first needs to be popular. It's a chicken and egg problem in some ways (no users without interesting apps, no interesting apps without a lot of users). Opening the doors with invite-only free accounts goes some of the way towards solving that problem without the scaling issues that would come with unrestricted free accounts.
I wish I could upvote you more than once. People will look at this video and think "oh, they've solved the big problem!" when in fact they've solved half of the big problem. Distinguishing between intentional and unintentional gesture has been the academic elephant in the room for many years now, and no one has come up with a good solution yet.
We developed this in-house. We use additional sensor data and fairly advanced optimization algorithms to produce these videos (all done in real-time on your mobile phone!) Due to the lack of sensor data, and subpar camera models, you won't get results of this quality with desktop video editing software like Final Cut.
Lay out your .vimrc like a boss
APT Is Marketing
If restrict the tone of dicussion to calories, fat, carbs and proteins, it is just not going to work out.

If something has been learned in the last 10 years is that whole foods matter and that you cannot reduce them to their macronutrient profile.
Two foods with identical profile yield totally different results.I recommend to read Willet book on eat, drink and be healthy.
http://www.barnesandnoble.com/w/eat-drink-and-be-healthy-wal...
Thus the experiment.
Once you've downloaded and installed a native application and plan to grant it access to your google account you've decided you trust the application. If you install a malicious app and give it credentials it can fuck you about 50 different ways, even if there is a url bar indicating you're on a google.com server.

Any app that takes a ASP would otherwise be storing your main account password. Two step is still improving your security posture here - your main credential can't be used without the temporal pin so the ASP is actually much more valuable.

If you're still concerned about a native popup, just don't enter your correct password the first time. If it fails you're probably pretty safe - Phishing style credential captures usually won't pass it through and risk server side anomaly detection.
We think of Meldium as a tool for sharing accounts,
not for just sharing passwords.

Meldium seems to be a tool for sharing web app accounts. Some of the accounts my team shares aren't for web apps.

While there are a lot of password managers out there,
none of them are built for teams first.

What about Passpack, which is what my team uses? Passpack has worked well for us, but I'm interested in alternatives because Passpack doesn't seem to be actively developed (bugs I reported months ago haven't been fixed and Passpack's blog is rarely updated).
That's not really a fair question. Pennies aren't worth the hassle of having to carry them around. That's like asking if I'd be willing to let the other guy have the money if he offered me effectively nothing.
> This is not a good idea because it breaks years (decades?) of expected behaviour on desktops.

I don't think thats really valid.

How long have facebook and twitter (among others) been automatically updating the page with new tweets/feed content?

It seems to me that the expectation of 'static page state' is already gone for pages where this would be useful - sites with fast moving feeds of data. I'd really love reddit among others to have this feature.

I'd also add that there is a lot going on around 'push' technologies for many apps that also destroy the concept of a static page state, and many of those applications are loved by users and developers alike.
I'm not clear where people get this idea from. In the case of Wasabi specifically, it uses Code DOM, which can generate IL, C#, and VB.NET out-of-the-box, and can be extended fairly easily to target other platforms as well.
It's an appeal to rational (rather than emotive) discourse, not arbitrary manners or social mores.
First, let's do the experiment with a billion dollars and see if you really just offer me 50 million.
I was under the impression that 3 round burst was a waste and rarely used. The increased fire rate dramatically reduces accuracy compared to firing three rounds quickly. The army's recent RFP got rid of the 3 round burst requirement:

http://www.defensereview.com/u-s-army-issues-new-individual-...
New article from Business Insider with "inside information" for what that's worth:

http://www.businessinsider.com/ex-yahoos-confess-marissa-may...

"'For what it's worth, I support the no working form home rule. There's a ton of abuse of that at Yahoo. Something specific to the company.' This source said Yahoo's large remote workforce led to 'people slacking off like crazy, not being available, spending a lot of time on non-Yahoo! projects.'"

"Mayer saw another side-benefit to making this move. She knows that some remote workers won't want to start coming into the office and so they will quit. That helps Yahoo, which needs to cut costs. It's a layoff that's not a layoff."
Very cool technology!

Honest question : Is this area a patent minefield? Or are the Myo guys busily sewing it all up? (I'm glancing nervously at the may-be-more-tricky-than-anticipated 3d printing field, for instance).
Thanks for the feedback! I'm the lead developer on RaptorJS and I completely agree that the messaging needs to be improved and that is what we are working on right now. We haven't actually started actively promoting RaptorJS, so yeah, I suppose you could say that it was announced a bit prematurely (thanks zengr!). Nevertheless, the toolset itself is very stable and continuously being improved so can be presently used.

While I'm at it, I may as well take this opportunity to try to "sell" you on the merits of this toolset :)

RaptorJS is a collection of front-end tools and modules that work really well together, but each module/tool can be used independently. Everything is designed to be optimized and simple to use. There's a lot there so I always recommend that people look at each piece independently:

- RaptorJS AMD: Very lightweight (~1.8k gzipped) and optimized AMD implementation that integrates seamlessly with Node and Rhino on the server and works in the browser as well

- RaptorJS Optimizer: Extensible tool for optimizing web resources (bundling, minification, compiling resources, etc.) that can be used at runtime or at build time

- RaptorJS Async Package Loader: Uses information generated by the RaptorJS Optimizer to optimally download packages of any type of code (JavaScript, CSS, LESS, compiled templates, etc.)

- Raptor Templates: An extensible templating language that also works really well for UI layout (embedding UI components, etc.) and allows for really clean HTML templates. Best-in-class performance. Try it out: http://raptorjs.org/raptor-templates/try-online/

- RaptorJS Widget Framework: Simplifies the initialization of widgets associated with rendered UI components (regardless of whether or not they were rendered on the server or the client). Also provides a mechanism for binding widgets to HTML elements and inter-widget communication.

Sometimes the easiest way to explain things to developers is through sample apps so I would encourage you to take a look at the following Github repo:
https://github.com/raptorjs/samples

Feedback welcome and appreciated. Thanks for looking!
Only temporarily, i.e., until they die having had < 2 children of their own.
Neat tech from CES
> He needn't have spent a million dollars on top notch defense counsel to get a lenient sentence.

Sure, he could have just rolled over. After all that's much cheaper, justice is, after all, for those that can afford it.
JqMobi Is Now Intel's App Framework
Wasabi nowadays uses Mono, and until very recently, whether it was legitimately viable was a matter of opinion. Technically speaking, its garbage collector made it ill-suited to long-running processes (such as web servers), and its performance was far worse than the Microsoft CLR--frequently two to five times slower. Ideologically, we also met resistance; many Linux system administrators seem far more reticent to install Mono compared to PHP. Both have improved recently, but back in 2005, Mono was not a sane option.
The least they could do is get the name of the product correct.
The Google for design inspiration
>You can be convicted of a felony for expressing an opinion about how to improve goverment?

No, but I don't see why they can't use it as evidence in a different case. IANAL, but it seems relevant if they wanted/needed to demonstrate intent.
So the terms of service answer this question in a vague way. Basically, they say you aren't allowed to use this data for any commercial purpose. But who is going to want to use this data for anything other than commercial purposes?

How You Can Use the Service
Semantics3 grants you only a limited license to access and make use of the Service for your own personal, non-commercial purposes. This license is the only license to the Service granted by Semantics3 unless you have a separate written agreement with Semantics3 or there are Additional Terms applicable to your use of a particular feature, resource or other portion of the Service. This license does not include any resale or commercial use of the Service, its contents or any derivatives. You agree not to reproduce, duplicate, copy, sell, resell or exploit for any commercial purposes any portion of, or access to, the Service without the express prior written consent of Semantics3.

You may not download any data or other resource made available as part of the Service, except for temporary system caching necessary for your own personal, non-commercial use of the Service in accordance with the TOS and applicable Additional Terms, if any, and not for further distribution or transfer to others, without the express prior written consent of Semantics3. You may not--and you agree not to--modify, reformat, copy, display, distribute, transmit, publish, license, create derivative works from, transfer or sell any information, products or services obtained from the Service, except in accordance with the TOS and as set forth in applicable Additional Terms, if any, or otherwise agreed in writing with Semantics3. Additionally, except as set forth in applicable Additional Terms, if any, or otherwise agreed in writing with Semantics3, you may not: frame or mirror any part of the Service without the express prior written consent of Semantics3; forge headers or otherwise manipulate identifiers in order to disguise the origin of any content transmitted through the Service; create a database or dataset by systematically downloading and storing content from the Service; intentionally or unintentionally violate any applicable local, state, national or international law and any regulations having the force of law; use any robot, spider, site search/retrieval application or other manual or automatic device to retrieve, download, extract, copy, index, "scrape," "data mine" or in any way gather information, content or other materials from the Service or reproduce or circumvent the navigational structure or presentation of the Service. Any unauthorized actions taken by you or by any third party on your behalf automatically terminates any and all permissions or licenses granted to you by Semantics3.
And it's not a RDBMS. It's basically the same technology as RedShift, but not cloud based (yet).
Exactly, it's triggered way too easily. It should include a confirmation mechanism like the "release to refresh" on iOS. Desktop usability vs Touch/Mobile usability are quite different.
Because of tab sandboxing.
If you thought it was tough to find comments and documentation when it was called jqMobi/jqUI and google would always get confused between jqMobile and jqueryUI, how do you think just calling something an App Framework is going to go?
When it comes to browser benchmarks, there is a lot of emphasis on JS performance, page load time, and memory consumption. But one area where I've seen Chrome absolute fall apart is scrolling performance. Safari regularly gives me 3-5x the frame rate when scrolling, to the point where some websites are nearly unusable on Chrome (say, Reddit with RES) but are butter-smooth on Safari.
Wait, why would you ever refuse a gift?

I don't get that.

If someone offered me a dollar out of his million, I'd accept it and be very grateful.
DNSSEC doesn't prevent them from serving you false DNS results. DNSSEC doesn't protect the communication between your resolver and the DNS server. DNSSEC allows for signing DNS entries with keys.

Since a large portion of DNS isn't signed in order to function on the Internet most resolvers with DNSSEC enabled will still allow results from domains which aren't signed for instance google.com. The easiest thing for Comcast to do is to return their false result indicating that the domain is not signed.

Since they can intercept all DNS traffic you send they could actually emulate all the way up to the root servers and sign with keys they generated themselves. This is probably overly complex but is possible and would allow a false dns entry to be accepted even by resolvers configured to only accept responses for domains which are signed.
Will the QWERTY keyboard disappear?