skysight-inc/HackerNews huggingface dataset:
As a health IT professional who did try, and will try again in 2013, this article is spot on.

There are differences between France and the US - especially in the mindset - but the payment system is very similar. In fact, the current french system (used for hospital billing since 2004, and tested for 10 years before that) was based on the US medicare DRG approach.

My job is to make patients pay as much as we can legally make them pay, using any mean necessary as long as it is legal.

In the past, my unit was the single most profitable in the whole hospital, by large. So I tried to sell things, and failed.

I would like to insist on the "incentives" topic with a quick example: I previously developed production analysis software to find and exploit the cases where an hospital could be more efficient and thus make more money (long story short, see one of my previous posts on http://news.ycombinator.com/item?id=4826314 for more details)

As I like to say, this is as good as printing money - I can say precisely what should be changed in a billing statement, why, how much it will gain, and the probability to find matching evidence in the patient file.

I can calculate an expected return, so that on small cases you can use unqualified personnel, while it might be worth to have a doctor study every page of the patient file for high profile cases (since, if you don't have evidence to back your billing claim, you are legally liable - it's not unusual for a large hospital to be fined sums with 6 digits if during an audit mistakes are found)

I tried to sell the software, with a commercial partner. In a year, we could only find a single client in the whole french public hospital system!!

Want to know why? The improved productivity - short term financial gains - can be used to demonstrate that the civil servants in charge were not as efficient as they should have been, or that they should hold to that level of efficiency in the future.

That's just like the OR example in the article - they don't want to be more efficient because basically, making more money is a liability to the top management personal career.

I was quite disgusted by this twisted way of seeing things. Medical credentials did not help me. Efficiency was not welcome. Improving one's profile, even at the expense of whole hospitals profitability, was.

I did not explore that much, but there seemed to be a demand for a service to selectively reduce profits, to maximize government subsidies in some units - something utterly disgusting for a libertarian. I didn't think I could do that, so I stopped.

I will try again very soon, but now I will make sure to carefully study the incentives, and do something I can morally agree with.
I'm in the 41st month of a Health IT startup and I'd be happy to give you a preview of the questions you havent even thought of :)

Honestly if you can't fund full speed (dev, QA, support, sales, mktg, ops, clinical studies) for a minimum three years before the first hospital sale, assuming you are selling to hospitals, then get out now.

Happy to shar war stories over a pint!
It is not clear if you just see "fbpurity.com" that this is parody, so it would be difficult to make that claim for the domain name, which kind of needs to stand alone as it is rendered alone. I do agree, however, that this person is unlikely to fall into trademark straights on this name (I maintain it was just thrown into the list of complaints to make them longer and more imposing, which would then lead to longer trials and larger legal fees arguing if it ever came to that). The argument, however, was out of place.
Show HN: Find/Sell used parts with car filtering (a school project)
Is it something like XAML?
4th challenge: what's legal in one state may not be legal in another and may change with every legislative session.

If your customers are physicians and other practitioners, the state laws are even more complicated as to who any data belongs to. In some areas, any data about patients is technically owned by their physician.

If you're contacting patients, your attorneys will debate at length whether something is legal under the rules of HIPAA. In the end, it will be a much ado about nothing, because HIPAA is barely policed or litigated over. So you'll end up with a large legal consulting fee, a confusing legal opinion, and no clear direction on whether to move forward or not. The next attorney will have a wholly different opinion.

Healthcare law in the US is absolute shit.
Medical credential will help, but not a whole lot.

There is some strong interest in the market to keep things as they are, even if they are less efficient. Incentives are not aligned at all.
Except it's impossible to prove the absence of prior art, while proving the existence of it is pretty easy.
I know it's non-trivial, but I think one-click effects would be amazing as well (reverb, chorus, distortion, etc). Think audio Instagram.
Sure, that's a like for like. Moving country - deleting Facebook account.
To the best of my knowledge Common Lisp methods (CLOS) already allows the ability to do things such as your rendering co-ordinate transformation example already without requiring extraneous abstract method definitions.

Generic functions and their associated methods allow :before, :after and :around qualifiers to be added to specify the order in which they are run without the need of creating secondary method names for each layer of subclasses. For base class methods that need code to be run before or after the more-specific subclass method is called, a :before/:after method(s) is written that will be executed before the more-specific subclass "overridden" unqualified method is called. The developer of the subclass doesn't have to care/know that the base class is still doing some work there.

Conversely, if this base :before method needs to be modified, it too can be overridden with a corresponding :before qualified method (with/or without a call back to the base :before method via call-next-method) or even totally shadowed by an :around qualified method in the subclass.

This seems to be the best of both worlds. The original base class developer can specify code that needs to be executed for
each overridden method without the sub-class developer needing to be aware of it without handcuffing the sub-class developer
in handling edge-cases that the base-class developer didn't foresee.

Here is the example code that implements this:

(defclass game-object ()
((x :accessor x :initarg :x :initform 0)
(y :accessor y :initarg :y :initform 0)))

(defmethod set-transform (renderer x y)
;; set the renderer coordinates here.
)

(defmethod draw-image (renderer image)
;; draw image here
)

(defgeneric render (game-object renderer)
(:documentation "Render GAME-OBJECT to display using RENDERER."))

(defmethod render :before (game-object renderer)
(set-transform renderer (x game-object) (y game-object)))

(defmethod render (game-object renderer)
(draw-image renderer game-object))

;; Class where the :before base class method just runs
(defclass scary-monster (game-object)
((image :accessor image :initarg :image)))

(defmethod render ((game-object scary-monster) renderer)
(draw-image renderer (image game-object)))

;; Class where the :before base class method is prevented from running
;; to prevent some undesirable action.
(defclass happy-monster (game-object)
((image :accessor image :initarg :image)))

(defmethod render :around ((game-object happy-monster) renderer)
(draw-image renderer (image game-object)))

;; REPL session with the RENDER, SET-TRANSFORM and DRAW-IMAGE methods traced
CL-USER> (render (make-instance 'scary-monster :x 1 :y 2 :image 'a) nil)
0: (RENDER #<SCARY-MONSTER {2456D3F1}> NIL)
1: (SET-TRANSFORM NIL 1 2)
1: SET-TRANSFORM returned NIL
1: (DRAW-IMAGE NIL A)
1: DRAW-IMAGE returned NIL
0: RENDER returned NIL
NIL

CL-USER> (render (make-instance 'happy-monster :x 3 :y 4 :image 'b) nil)
0: (RENDER #<HAPPY-MONSTER {246A1689}> NIL)
1: (DRAW-IMAGE NIL B)
1: DRAW-IMAGE returned NIL
0: RENDER returned NIL
NIL
I will point this out though: this question does not make sense in a Marxist analysis. There is no 'middle class' or even 'upper class,' these are vulgar economists' terms.

Not quite true. I would label the middle class as the portion of the proletariat or petit bourgeoisie with some savings or even investment income to keep them afloat.

The issue being that the middle class and the "poor" proletariat have different relations to swings in currency and investment values. Inflation, for example, is good or neutral for the portion of the population who live month to month or remain consistently in debt. But the middle class have net savings, which inflation destroys. Likewise, low inflation or even slight deflation is good for the middle class, who have savings and small investments, but strong deflation is good only for the "true" capitalist class.
I am confused, how so? It is the same as any FPS.
Here are some things that I wish I could have shared with some of my people in the past:

1. I really cannot explain why there seems to be no long-term direction, and I'm leading you and the rest of the team on completely unrelated initiatives every single quarter. But I suspect it's related to the earnings calls.

2. I'm not thrilled either that there is no money this year for any office's annual Christmas party, despite the fact that the executive team just received huge bonuses.

3. Yes, it makes no sense that a company this small actually owns a private jet.

4. There's a very strong likelihood that in two weeks the company will announce an across-the-board 50% paycut for all employees for a period of four weeks, just so the company can meet some kind of payroll. And you and many, many others will of course resign. I, on the other hand, like a moron, will not resign.

5. You're absolutely correct. The CEO is quite possibly insane.
will you enable H.264 support only on desktops once you have working backends for Windows/Linux/OS X or will they be enabled by default as they are working? Just wondering if there will be stable releases of Firefox where some platforms have H.264 decodes and some don't.
The Anatomy of a Card Transaction
You won't be able to create an exception for software not to be patentable. It's over, get used to it and move on.
And if Apple had their way (and their patent) we would still be tapping that magnifying glass because nobody else could feature pinch-to-zoom.

And I'm not convinced Apple would license that IP to Samsung.
That's why I bought the bundle for $5. I hadn't heard of it much before but I knew it was a fairly new game compared to the others.
Genapp - plugin based PaaS applications
How could there not be room for innovation there? Anyone who has used SAP can see that.

A few years ago, one of my clients in an oil plant was trying to find parts (a certain type and size of carbon-steel pipe). They were on SAP, and all inventory was logged by the maintenance people in the various plants in this complex. The guy had to try inputting every combination of "3' diameter steel pipe" into their 90s-esque interface because they hadn't standardized the parts names.

3 foot, three foot, three ft, di, diameter, etc.

Is that SAP's fault? Well, I suppose it could have been avoided with training- training every single maintenance guy in a huge complex to standardize the name of every single part.

What bothers me isn't that they didn't solve that specific problem- I'm sure it happens everywhere. But 'implementing SAP' is a multibillion dollar industry because it's so configurable. There has to be a better way. (I've heard mixed things regarding OpenERP in this forum)
I recommend not trying - not for profit anyway - unless you directly influence (did they come to your birthday party?) multiple people at the C-Level at 2 or 3 major hospital prospective customers, ideally academic research centers, depending on your idea
Let me fix the title:

"The Sorry State of Typography Licensing"

It has always been, and will continue to be, a pain, because the foundries have the same mindset as recording labels, movie studios, etc.
How to plan a party for introverts
Stripe updates policy: free refunds and chargebacks
Beyond the First Idea
If the source video is deleted, Wavo simply skips that video and moves on to the next in the playlist.

And yeah, when we have the username/password pair sign-up, we'll simply have an option in the app preferences that will allow the user to additionally connect their facebook account if they like. If not - no problem.
> I'm saying that they shouldn't be able to patent something as easy to implement as that for 17 years, or whatever the patent age is.

If it was so "easy", why wasn't it invented a long time ago?
Archive.org: Only 12 days to reach the goal of $150,000
> the sad truth is that medical industry doesn't welcome software disruptions

This is a message that really needs to stop being regurgitated around the technology start-up space.

The medical industry DOES welcome software disruptions. The past two years have been the two biggest years in healthcare software disruption, in terms of VC dollars invested in that sector[0], the number of accelerators that have accepted healthcare related start ups (YC has now invested in a several) and the rise of accelerators focused on healthcare (e.g. Rock Health, Health Box) that have graduated over 100 'small and agile' teams that have established product-market fit, and raised institutional funding.

Healthcare is a space that does require a significant understanding of industry-specific knowledge (third party payment models and regulations are examples), but I feel that many other industries that are being disrupted have similar barriers to entry.

In my experience, most developers ignore the medical industry, citing similar complaints as yours, but neglect to mention the incredible growth that has been demonstrated in that industry for a while now...

[0] http://rockhealth.com/resources/rock-reports/digital-health-...
I celebrate the former first.
> I have a database of 1 million users.

Similar to Linkedin with 6.5m, we have a real-world case study.

> Regardless of what hashing algorithm I am using, if there is no salt I just need to hash the entire password space once, where the password space could be a dictionary attack or a brute force of passwords up to length 10 of letters, digits, and symbols.

When you say "entire password space" you're implying that there's a hard upper limit on the complexity of a user's password. Many sites do indeed restrict passwords to 8 or 10 characters, but that's horrifically broken.

Any not-completely-broken system has an password space so much larger than an attacker could search that it's effectively infinite. Note that even the silly system proposed here uses MD5 which accepts password longer than would even fit into available memory.

> If there is a salt, it means that after hashing the entire key space I only have the password for 1 user rather than all of them.

As described, the "key space" is effectively infinite, but luckily for the attacker some parts of it are far more richer to mine than others. This is where the easy-to-guess passwords lie.

So the attacker won't do anything as dumb as "hashing the entire key space". The attacker will search the most rewarding parts of the keyspace first.

> It means attackers must use targeted attacks and slows them down by a factor of # of users. Rather than having all my passwords in a day, an attacker gets access to one user's password per day (over the course of a million days). (Still not a good thing to happen)

For example, recent data breaches suggest that 50% of users will choose one of the 10,000 most-common passwords. So the attacker tries this set on all 1M of your users. That's 10,000,000,000 hash operations. A typcial rate for SHA-1 is 3.8 billion per second, per GPU. http://hashcat.net/oclhashcat-lite/

So our expectation is that the easiest 500,000 of your 1M accounts will be cracked in the first 5.2 seconds by a single GPU attacker. And this is approximately what happened with Linkedin, ISTR 60% of the passwords were reported cracked that first day.

But the rate of success slows down for the attacker and the remaining passwords begin to take exponentially longer. As of today, 90% of the Linkedin database is reported to have been cracked: http://arstechnica.com/security/2012/12/25-gpu-cluster-crack... So there are really only 65,000 hashes posing any difficulty at this point.

When a fast hash function is mis-used for password hashing, salt or no salt, there's not a case where "an attacker gets access to one user's password per day". The attacker cracks the majority of passwords in the first few seconds yet a small minority will never be cracked.

Salting doesn't save the database as a whole. Salting doesn't help the users with weak passwords. Salting doesn't even help the few users with very strong passwords, they wouldn't need salt in the first place. But for the users in the 60 - 90 percentile, it might buy them a few hours or days.
Your mom and dad (and the rest of your network) are almost certainly "unaccredited" investors. Soliciting their money will complicate the hell out of any subsequent fundraising, and exposes you to significant legal risk down the road.
Enterprise-Worthy Improvements in the 3.7 Linux Kernel
> 2. Good enough is not good enough

I don't think this really sinks in until you work in the industry. As an example, I knew of a developer who accidentally forget to make a list page scrollable and it got through QA that way. I heard rumors that ultimately the bug resulted in a patient being given the same immunization twice since the user was unable to scroll down the list page.

And that's a relatively benign example...
You are definitely right and we'll be continually looking at better ways to integrate seamless sharing into the app.

Seamless sharing is also a "band-aid." It gets users sharing your app at the beginning but there's definitely some users who are turned off by it.

So although this is where a lot of our referral traffic comes from at the moment there are undoubtedly better ways to do this and we're working on it. These are early iterations on the product and we'll be circling back very soon.
This article understates the issues delivering software solutions to patients, providers, or payers. The lack of data standards has completely crippled the ability for new companies/products to innovate and break through. When I worked at a healthcare VC, we deemphasized IT in favor of medical devices because the path for success is much clearer and easier to trod.

The reason I can be so confident that it's the data standards, BTW, is because the DICOM data standard exists for medical imaging. IIRC, the founder of Heartlab invented the format, it somehow escaped a proprietary home, and dozens of companies innovated on top of it. The existing EMR vendors - GE, Cerner, Epic, etc - all have proprietary data standards for storage and interchange. My due diligence on this revealed that the companies would each have to spend three years re-writing their software against a common data standard. Of course, they should have to. It would help patients immensely and all sorts of innovations would spring forth, just like after DICOM.
FWIW, I believe that it is more "you can lose it if you lose control of it"; just because you haven't enforced it is not a big deal if the people you haven't enforced it against are sufficiently small that they wouldn't have been noticed in a wide enough audience to undermine your trademark.

(In essence, the argument is not a technical one: it is only interesting in that it changes the dynamics of "could someone have been confused"; if people see the word "Facebook" as a moniker on products all the time that are not made by Facebook, then clearly they are not going to be confused by any individual one.)
I actually agree with you. The immediately preceding paragraph in my post said...

"Is it best to elect officials who we believe to be more knowledgeable that ourselves, and to defer to their judgment on issues that are outside of our understanding? Or is it better for an official to serve as a direct representative of the people?"

If the answer is the latter...in this framework, a representative exists as an "aggregator of wills".

I'm basically laying out the two options you highlight.
Including or excluding Santa and his elves?
Sure it is acceptable.
thanks! i will try, at least for a little while. honestly, at this point, i think a true disruption can only happen if diagnostic tests are put into the consumer's hands instead of being held hostage at the hospital, and we just aren't there yet.
UK Pirate party closes its piratebay proxy
I tend to agree with pretoriusB re the HuffPo. I also think bloggers/the new 'blogger-journalist' are more suited to investigative and opinion pieces rather than the breaking news o the day. Certainly you are right that there is a fine line between blogging and journalist.

With regard to 22 children stabbed, I agree that I don't think someone has made this up. But this is in china, not in the west, and as other posters have noted and I tend to agree having spent some time in china (well.. A couple kf weeks) that social media >> their state outlets. There are numerous instances of weibo being used to circumvent state censorship, despite being censored itself- the enterprising Chinese netizens use alliteration and 'read between the lines' to overcome this.
Provide incentives to publish innovations instead of trade secrets. Allow others to stand on shoulders of giants.
Way - vo - me
I don't even like pinch to zoom. It is hard/impossible to do when using the phone one handed. It is also annoying in apps like google's new maps for iOS because it is hard to not also rotate the map, which is hardly ever the desired outcome.
I actually never mentioned Android in my comment, I was merely stating that zooming functionality generally worked like that prior to iPhone. For example, on Blackberry, Pocket PC, etc.
what exactly have Cuban or Minecraft innovated?
USPTO denies over 90% of initial applications, and even with appeals factored in, less than 50% of applications end up getting approved (it was 48% in 2011).
Interesting. Reverb actually would be trivial since it comes built into the WebAudio API. The others maybe not so much. What use cases do you envision there?
He probably did it just to wind up the haters on HN.
I enjoy having colour variables at the top that are project specific blues or oranges which can then be set as the values of other variables such as @state-warning-text.
I think you're right, there's no reason not to explain our fee on the frontpage, and just link right there to the help page that goes into detail (update: added :)).

I'll also definitely add a csv export to the participants list, and do you mean some kind of mailchimp integration so you can send announcements and whatnot to your participants? That's an interesting idea we've thrown around a bit already.

As for Udemy's 30%, wow! Udemy is much more of a full-service sort of thing, it seems to me. More formal, they appear to do a lot of promotion and have a ton of community tools and so on. I think ultimately while both are about e-courses, they aren't really in the same market.
Can you share some links, this is very similar to something I am building with an old university buddy. FYI, we are focusing on verticals first; to conquer a large share of a small market before moving on.
You obviously misunderstand patents, as they have absolutely nothing to do with how easy something is to implement. They're awarded to companies that take risks, research, and invent something new.

It's a fundamental mistake to write off a "simple" invention as easy to come up with, obvious, a no-brainer, etc. Simplicity is difficult.
I like the idea of making sure your tasks have a certain amount of "stretch" (i.e. push yourself a little with every task you give yourself).

We focus so much on our skill level that we forget that the "flow" state requires challenging yourself:
https://en.wikipedia.org/wiki/Flow_(psychology)#Conditions_f...