skysight-inc/HackerNews huggingface dataset:
That's actually massively filtered most of the time. The colour corrections are done at scan time (just as they were at print time with standard photofinishing in times past). If you were developing/printing in a home darkroom in ye olde days, you'd expect a good print on the third sheet of paper (well, the 2.25th sheet, since you'd only use a quarter-sheet for the rougher adjustments) after fiddling with filter packs or the settings on a dichroic enlarger head. (Slide shooters needed to use CC filters at shooting time.)

Digital can give you pretty much the same skin tones as you'd get with a given film (Fuji's out-of-camera JPEGs are very close to the films they're named after); it's just a matter of matching the response curve of the film you want to emulate, and that takes some fiddling that most people don't take the time to do. (Capture One has much better default conversion curves than most raw conversion software, especially where skin tones are concerned. But you can profile your camera and create your own defaults in most software.) Film does have some advantages, especially when pulled to increase its dynamic range, but it's not fundamentally better than digital, just different.
nice user name
It sounds like what you have is an investment thesis :)

Put some money behind it! Maybe you're right..
I just asked the guy. He had self-taught himself programming on his own for a few months prior to attending the program, but attended in part to make a career change (had done startup biz dev / operations / whatnot prior.) Maybe that counted, or maybe they just tightened the restriction since then.

That said, this was spring of 2012. I'm sure Hacker School has changed a lot since then! Suffice it to say he's a fabulous programmer now. :)
Hey, digita, no problem. I'd love to connect and get some of your feedback.
my email is kt [at] efabless [dot] com
Beard trend is 'guided by evolution'
Microsoft broken definition update breaks systems running Security Essentials
Currently patching 13,000 POS systems in the field due to this. Thanks, Microsoft.

http://hothardware.com/m/News/Coincidence-Or-Accident-Microsoft-Security-Essentials-Bug-Rendering-XP-Machines-Hamstrung-Like-A-Virus/default.aspx
Is there anything from preventing people from encrypting their hard drive and uploading it as 10 10GB avi files?
I suspect that constant factor memory usage should go hand in hand with the criticality of constant factor cpu usage.

If a constant time cpu algorithm was not also constant factor memory, then the timing of cache misses (or gc, alike) would certainly be subject to side channel attacks.

If constant factor memory usage is attained, I cannot easily think of a way that a garbage collector could cause an interference that leaks information. (Though by all means, one ought think harder than I have.)
Marionette is a solid framework. It has everything you need to build fast, and clean: regions (which were a great step in the right direction and will be improved in V2), composite/collection views, layouts... the basics are there for you to work with how you would like.

You've made three points which I can't see much fault with. Why the hate?
We built Speedbar for django which does this as part of its summary information, but also provides full page profiles as well in production.

https://github.com/theospears/django-speedbar
Como oferecer um provedor de Internet sem fio com qualidade
Because the ads are usually relevant and useful. in your example, the second card is a nice summary of hotels with all the relevant info right there
TekSavvy is a fantastic company, but their business model is completely dependent on the big telcos who control the last mile. The UBB crisis a few years ago was a very close call, and it is bound to happen again in one form or another.

So if TekSavvy et al. try to resist the information leaking that the proposed legislation permits, I wouldn't be surprised if the MAFIAA took extralegal measures to force their hands. For example, Bell & Rogers might be persuaded to change the terms of their contract with indie ISPs the next time the contract comes up for renewal, unless the indies agree to some sort of "standard Canadian telco privacy policy" drawn up by the big telcos.

So Canadians might end up with a difficult choice: you can have privacy, or you can have 300GB traffic caps, but you can't have both.

> sivulving

I don't believe autocorrect is capable of producing words like that...
I don't think a modular phone factor like shown here solves any of those problems though

It may not, though I'd be surprised if nobody hacks together a sliding keyboard for this thing. It'll probably be bulky. The fragility issue can be solved by putting a good case over the whole thing. Assuming the overall platform works out to a limited number of sizes, I'd likely offer to sell cases made of various fiber-reinforced polymers[0] with cutouts in user-specified locations.

The Sony Z1 Compact is approximately the size of a Moto X despite having a smaller screen. I think the waterproofing adds some bulk. The Moto G also has a 4.3" screen and is so close to the Moto X in dimensions that it fits comfortably in a case molded around a Moto X, though some cutouts don't align correctly. All of these are a bit too wide for me to use comfortably one-handed, while the iPhone is not. I don't expect modular phones to address that problem effectively, but I wanted to point it out as a segment the current market does not address at all. Based on totally non-scientific anecdotes I've collected by talking to people online, it's the largest of the three segments I mentioned.

[0]http://i.imgur.com/wcLcKqG.jpg
> Google's version, on the other hand, works with only a single photo, so it's more versatile.

This doesn't seem to be what everyone else is saying. Most people here are saying it takes multiple shots as you move the camera.
ESR: Down the feminist rabbit hole
"I don't think it's fair to say that "modern diets are the problem"."

Yeah, see, I didn't say that. You edited that to mean something completely different from what I said/meant. My sentence started with "perhaps", had no italics and I went on to ask how that could be tested. So I think this is a not great comment. It feels almost slanderous to me.

But I think it's fair to say that the many benefits of modern diets are accompanied by some serious negative side effects, and that the human microbiome has not yet had enough time to evolve into an optimal state for coping with them.

That's part of my assumption. But, also, it seems to me that the modern diet has chemical impacts that are pretty well-established as promoting disease. Not that we have to eat crap, but a lot of us do, in fact, live on rather crappy food -- microwave meals, food "products", etc. I think it's complicated and that the impact of food chemistry is not well studied or taken all that seriously. People who think relatively small changes may have big impacts tend to dismissed as quacks.
If you are truly an insomniac, no article will solve your problem. A doctor, however, is likely to help.
Google's letter to shareholders when they went public said that they would never give earnings guidance. Has that policy changed?

Edit: Various articles have suggested not:

http://www.marketwatch.com/story/google-investors-pay-the-pr...

http://www.mckinsey.com/insights/corporate_finance/the_misgu...
This emphasises precisely why it's not just having the idea that makes the difference. Execution is the secret sauce, not the original idea. All kinds of people will arrive at the idea and never progress it, so don't bet big on an idea alone without the implementation to back it up.

It's not unlike the phenomenon of independent parties arriving at the same discovery within very close periods of time. The idea itself is often relatively easy - it's the hard work to prove the idea that makes all the difference.
We solve the problem by paying over $1k/yr to Dropbox who are of the opinion that people do actually use Linux.

Of course then Dropbox mess up the multi-account thing badly even with the recent changes.
Thanks for responding. I am just spitting out questions and hypotheticals that jump to mind when a see a service like this offered.

How do you guys limit by file type? I imagine that is is something more advanced than simply looking at the the file extension. But if there is any advanced analysis, how does encryption come into play? Lifehacker suggests users should encrypt their sensitive data before uploading, but will you accept encrypted files? Seems like it would be difficult to impossible to tell the difference between encrypted home video and encrypted database backup.
We have a few advanced techniques that inspect the file data and ensure that the file is valid. So even if you rename your encrypted backup to to My_Home_Video.avi, it wouldn't pass our check and would fail to upload.
If nothing else, these improvements make HTC's gimmick of adding the extra lens while giving up OIS seem all the more silly.
Thanks for the tip!

I actually already use pyqtgraph extensively. Those plots I was talking about are pyqtgraph plots :)
It depends on your runtime and your scalability goal. 10,000 threads is possible in some circumstances but 1M is probably not possible.
Making hard rules like these seems to me like the only sensible solution. In fact, I'd go so far as to say that expecting to run a successful early-stage business and being a good parent to two young childen is impossible unless you lower your requirements on one or both fronts. If you don't lower the requirements voluntarily, nature will do it for you. (There are rare examples of people who have extraordinary endurance, but they are by definition extraordinary).

Burnout is not fun and it can put your out of business for months, or even years if you have a bad case. (In my case, it was a year and a half of zero productive work). One of my relatives, after a particularly rough Ph.D, claimed that she will never be able to perform at the same level again. It's okay to be ambitious, but I think too many young and ambitious people let their ambition get the best of them. Learning your limits by crashing into them at full speed is not advisable.

I don't mean to sound negative or dismissive, but I've experienced this myself and seen too many cases first-hand not to care. The Silicon Valley startup culture is in many places outright destructive when it comes to this aspect of life.

More constructively: Setting strict deadlines and schedules that you will maintain unless the sky is falling (change the definition to "no matter what" if the sky is "constantly" falling), balancing your time so you have enough sleep and enough time to yourself is a safe way to ensure that you are working sustainably. This will lower your productivity, though. At least make your sacrifices with both eyes open.
HyperLogLog visualization
Well, remember the 80-20 rule: it is likely that only a small number of your assets constitute the vast majority of your net worth. You're not going to enter _everything you own_. Simply entering the valuable things should be a sufficient approximation, which is what I think the user would be interested in, rather than a pedantic to-the-last penny assessment, since Trov itself returns merely _estimates_.
anyone else put off by the idea of having someone else inspect/pick out your fresh produce?
Google's probably under less pressure than many companies because the dual-class stock structure makes them immune to takeover attempts.

I think a lot of the problem is that the stock price has many spillover effects. Recruiting & retaining employees is much harder when the stock is in the toilet. There's less currency available for acquisitions. It slants everything the press says against the company.

There was another story on HN today about how Marc Andreesen was dying to fund something that disrupts the financial industry. This is probably a major reason why: they wield disproportionate power based on made-up numbers.
this is also can be done with tesseract or encog framework... i dont know whats news about this
they made a phenomenal amount of money That is exactly what I heard as well.
But one requirement of a captcha system is that it be easy for a computer to generate. The system you describe seems to require that humans build up a list of things with obvious-to-human answers, which doesn't scale, especially when they have to be designed under the assumption that "the enemy knows the system" (i.e. a worker on some "library of common knowledge" project could defect).

But if you could have an AI generate those problems, it would be capable of solving them too!

Current captcha systems exploit the one-way nature of problems, mainly "character distortion". This is what permits easy computer-generation but not computer-solution, and does not seem to be present in the class of problems you describe: it's just as easy to go from "noun -> adjective" as "adjective -> noun".
Stuck in the vicious loop with you. I can't imagine adding kids to the mix.
You're right -- we have an advanced way to actually inspect the file to ensure that it's a valid file. The encryption happens post-check.

Unfortunately, we don't have a way to let you encrypt your data and then upload it up yet (but have a few ideas on how to make this work for the future). Besides, if you did encrypt all your stuff, you wouldn't be able to take advantage of all our media features like video/audio streaming, photo/doc viewer, etc. :).
Thoughts on Vagrant
Australia's sports interactive statistics
Ember, Ember, Ember. Oh, how I love thee.

There are a few types of javascript styles that I've found are pretty common.

- Event Based (jQuery-esq)
- Class Based with router (backbone, marionette, et al)
- Declarative with routing (Ember, Angular)

Of those, I think the declarative applications tend to build out into easy to maintain systems. State management is easier, extending is easier, and most tend to build easy to digest components that are small and cohesive.

I've found that Ember scratches a number of itches for me when it comes to building out a declarative system. The biggest win for me is the fact that Ember's router is a really, really fantastic bit of engineering. The way that you can build out state into your router and have classes and components that react to those state changes is a super elegant way to develop web applications, for me. Combined with the outlet system for managing complex view trees, and it's a slam dunk.

Ember's system of routes, controllers, and views help me maintain single responsibility principles, because I have a clear definition of what a route does, what a view does, and what a controller does. Things are even easier when you get down to the refactor stage and start moving everything you possibly can into components (which are forward compatible with the upcoming specifications for web components).

The only reservation is that, because the style of MVC that ember follows, the learning curve can be a bit drastic. They've been solidly improving since 1.0 dropped and the wealth of materials out there that are outdated or old (pre RC days) are dropping off of the SERPs pretty rapidly.

Ember's a joy to work with. For 85% of the web applications out there, you probably won't need to venture out of the framework all that much. However, when you DO need to venture out of the framework, it can be a really frustrating experience. The primary example would be integrating something along the lines of D3 or Three.js, or honestly any library that expects to manipulate the DOM directly, as ember's reliance on handlebars is pretty complete. This means that having a view class manage user interaction events really can't be decoupled from the rendering of the view itself, which I feel like is ember's biggest issue right now. Secondarily, there is a personal need for better hooks for view lifecycle events, for providing things like animations / transitions in and out. animated-outlet is a potential solution, but I'd much rather do it the 'ember way' with hooks I can define in my controller classes rather than using a one-size-fits-all style solution (which is what I feel like animated-outlet is).

Don't let these things detract you from really diving into Ember. It's honestly a super refreshing and highly efficient way to build javascript applications. The state management of URLs within the router as well as the very clear and well enforced separation of concerns helps reduce code rot and smells before they even get started. Once you're past the initial learning curve, you'll be shocked at how rapidly you can develop robust, focused applications.
My initial thought on this was that it needs to be a combination of self-hosted/hostable, open source and community driven. At the very least, it users should be able to control where their data is stored. Now that I see that advertising is a major component, I feel even less confident this can work.

If one of the goals is a Series A, the only way this thing works if it goes big and goes big fast and investors can be convinced on the promise of a working advertising model. If advertising is a big part of the monetization strategy, the chances of success are low. Everything would need to go right. But it's just as likely that in a few years time the company stops work on it if the numbers don't look encouraging.

The problem with being funded here and already having some eyes on a Series A, and also looking at an ad model, these are all big pressures that are placed on a startup (i.e. go big, go bust or pivot into solving another problem). It also takes the focus away from the user. Of course the idea is to build as good a product as possible. But the user is now the product and the userbase is tasked with showing enough growth potential to convince investors for more funding. The startup pressures can create conflicts of interest between users and company goals (do we need yet another company that harvests data from users as their reason for being?).

This product and the idea of it, from the outset, is about empowering users. Making their life easier. Giving them superpowers.

What gets me the most is that, technically, this is a product and an idea that doesn't require a funded startup and a cloud based service to succeed. For some products, having investors and a major push for growth is pivotal. But you could easily see a software that accomplishes the same things, but is either free and open source, or just a simple paid service or software. If the vision really is as good as you make it out to be, people should be willing to purchase it. That model is more compatible with the core concept of user empowerment.
It is perfectly reasonable to seek out other revenue streams. It is still a land grab. There are many other megatech companies that aren't innovating or acquiring and are slowly dying. The "tech platform" evolves every 10-20 years. Innovate or die. We already talk about the Internet of things. Mobile apps and mobile access are clearly eclipsing the PC. Odds are the next Facebook or Google starts as some mobile app not yet invented.
In Google's case, they make up numbers based on any publicly-available estimates of Google's business drivers they can find - traffic, CPC, etc. Google doesn't provide earnings guidance.
I'm not sure how that case is relevant to your point. In that case, Sega used a TMSS file as a hardware check to make sure games were properly licensed. Acclaim copied this file and included it in their games after reverse-engineering some demo games. This was eventually found to be fair-use since it was required to run their games but there was no technical reasons for the use of the TMSS file.

That's different from the point you were trying to make. The provision of email addresses and phone numbers are inherently necessary for an email provider or telephone service provider to provide those services. They aren't just incidental data--they're a fundamental part of the service transactions at issue.
Actually I think Webflow can be a useful tool for if you're a developer who wants to learn how to design a prototype. I struggle with visualizing a new site without a mockup or style tile for reference. Webflow's UI is intuitive - everything you do has immediate visual feedback and directly translates into clean CSS/HTML. The previews of media queries affecting content is nice too. So it's very easy to reverse engineer how to make a good design, the same way you would reverse engineer some source code.

But with that said, I am not a paying customer. When I need to make a site then I just sign up for a free trial and export the code to continue the project. Their individual plan doesn't really make sense for me and I think it's too expensive.
>> They are nestable
> trycatch is nestable as well.

By nestable I mean that you can fork a Zone, configure different values and handlers (for things like intercepting microtasks and timers), and run some code in the forked Zone. All async callbacks spawned from that code will run in the forked Zone.

>> intercept microtasks
> Care to elaborate?

Dart has an API for scheduling microtasks inside the event loop: scheduleMicrotask(callback). Zones can intercept this call to do things like keep track of the size of the queue and do something when it empties, or manually and synchronously execute the tasks for controlling time in tests.

>> wrap closures to be associated with the Zone
> Yup, similar to domains, though I do wonder when this is necessary?

It's useful for interacting with external systems and preserving Zone affinity. This is how dart:html ensures that event subscription callbacks are run in the correct Zone, it wraps callbacks (only if necessary - if there's an installed Zone) in the Zone and then hands them to the browser. The wrapper installs the correct Zone before executing the callback.

> Long story short, things like keep-alive sockets will retain a domain/context/zone(?) and their handlers will be called with the incorrect context.
>
> Do you fix this in your zone.js implementation?

Zone.js is a port of Dart's Zone, so I don't know how faithfully it reproduces it. In Dart, I don't know of any API that doesn't execute callbacks in the correct Zone, except for a bug in dart:js that's being worked on.
At one time, there was this effort on 4chan to spam recaptcha with "penis" for the second word. When this got to some online news site, they asked the recaptcha guys who confirmed that the traffic was irrelevant.

I suspect the nonsense won't matter. You're drowned out.
backbone's only hard dependency is underscore, it's also the lightest library on this list by a solid margin
Interactive visualization on "How much money would you have if..."
I always fear what will happen to all of Google's well-intentioned businesses and ethical thresholds when / if the river of money starts to narrow. Will they try to bring back their revenue with ever more desperate measures? Will they slash and burn their investments? Or will they stick by their guns and keep plowing money into new projects, continue walking the thin line between "creepy" and "useful" without ever erring across it, even while their kingdom crumbles?

We've never had to ask this question because on the back of an expanding internet Google has risen with the tide regardless of their own performance (and I'm not saying their performance has ever been poor, just that we have no way to know in absolute terms). This particular instance may be nothing, but every time they miss a mark I wonder whether we'll finally find out where their principles truly lie.
I would love to see a nicer language replace JavaScript as much as the next guy, but it seems rather unlikely especially given the changes that ECMA has approved in the past.

I am really hoping that some day, we will be able to do front-end devwork that isn't just an abstraction of JS/HTML/CSS.
Which goes back to Chief Justice Roberts statement on the ObamaCare ruling.
“It is not our job to protect the people from the consequences of their political choices,”
Station to Station: The Past Present and Future of Streaming Music