skysight-inc/HackerNews huggingface dataset:
You don't really have to enter your payment information every time you create a website. Once you signup, you can make a deposit for $3 and we'll charge you only when you create a folder in your dropbox (that too 1 hour after you create the folder in case it was done by a mistake). Also, even if you don't have any funds in your account your websites will be live, we'll send you an email to clear your invoices :) In short, all you have to do to create a website is create a folder with an index.html file. I am also the creator of http://getsimpleform.com which is a service which allows simple contact forms with akismet integration for spam prevention, it also allows you to use templates for the email notifications on form submissions. websrvr will have all that functionality and a bit more :)
I did mobile contract work for 2 years and built most of my products on Parse.

The free tier goes a long way. In my experience, if you are thoughtful with the quantity of requests you send from the clients, it will take over 1000 users to push you into the paid tier. This really depends on the nature of your application though.

As for development, there are a few nuances that you have to get right to use Parse at full capacity. First, delegate as many operations to CloudCode as you can. I do this for separation of concerns (clients should focus on displaying data, not retrieving and formatting it) and more importantly, to make cross platform applications consistent and easier to write. Also, you can change behavior on the fly instead of creating new builds of your client when you just want to change a small detail, like the number of results to return.
When using CloudCode, take advantage of Parss's implementation of JavaScript promises. And avoid mixing promises with the "backbone-like" callbacks. There's a bug I've found when mixing the two that will occasionally cause the operation to finish before executing all the callbacks.

And speaking of bugs- the biggest drawback of Parse is the documentation and support. Some entries in the docs will actually be a one sentence reiteration of the title of a method. It's mind blowing how shitty some parts of the docs are.
The support is even worse. Looking through the help archives (they've now given up on internal support and moved their entire support platform to stack overflow) you will frequently find smug answers from the Parse team. It's common to see a Parse support teams response get tens of downvotes. It's bad.
I once found a bug in Parse's method to save multiple objects at once (if the first request failed, all subsequent requests would fail too) and getting a fix implemented was a huge pain. I had to go through Facebooks bureaucratic big reporting process only to be told the bug was a 'feature' weeks later. I resubmitted the bug with all kinds of proof and demo projects, and finally after a few months I got the email saying the big was fixed. Huge pain.

Overall, if a prototype backend will suit your needs, I highly recommend Parse. It's certainly not the pie in the sky it could've been, but it gets the job done and lets you quickly get to market.

The free push notifications, data dashboard, and analytics are some nice sugar on top too.

I will probably continue to build my products on Parse, unless I know I will need immediate scale, or a client requests a specific backend configuration.

Been wanting to try Firebase too. It's a Parse like BaaS where everything is done in realtime. Very cool, but still somewhat unproven and new. Has anyone used Firebase?
This entire article seems like a stretch. It goes from asking her about companies in their portfolio to sexual harassment and sexual advances.
Why Federal College Ratings Won’t Rein in Tuition
Recommended podcast both in general but for this particaluar episode too.

http://www.fromscratchradio.com/show/robert-hammond
Alternative method for high-profile startups: multiply number of employees by 0
I'm in the process of helping a client migrate a large data set (5m users) off parse due to the issues they've had. They had a fairly consistent rate of 1 in 100 requests return a ECONNRESET error in node. After over a year of haggling with the parse support team the errors finally disappeared about a month ago. They needed at least 10 fetches so you can imagine that 1 in 100 not returning doesn't bode well.

I don't have all of the specifics as to how or why the errors went away, but no changes in the client's codebase were made that relate to this.

Summary: seems brittle, tech support was useless, customer wrote huge checks to parse every month and didn't get traction fixing the problem. Even though things have improved we're continuing with the effort to help migrate the client away from parse.
I think that people often miss why people go to doctors in the first place and why they trust them. In society a doctor was historically always a very well respected individual. I think it's worth reflecting on that. Why were they respected? Did it help the patient that they were respected?

Considering the impact of placebo medicines, I can't help but wonder if there's an element of psychology that needs to be noticed and addressed here (and whether it is actually key that a doctor is respected (for the right reasons, obviously. Specifically: that they will be able to address the problem addressed to them)). My hypothesis is that a good doctor is someone who asks the right questions but also looks for questions that need to be asked for that individual's needs. Example: the patient has the symptom of a broken arm, but why is that. Is there something more here? Is there some form of domestic violence involved? Or... do they have a weakness in the opposite arm, and when cycling they are more likely to fall off.

One of my doctor friends said to me that they'd recently shown that the better the Doctor communicates with a patient, the lower the chance of lawsuits. I like to call it 'managing expectations', from the whole project managementy world although someone will shoot me for saying that!

It may well be the case that on paper checklists work best, but I assert that there's a lot more personality and social interaction to a doctor than anyone initially realises. The challenge in this space is marrying the two concepts.
I guess if ISPs would really go sniffing on whether they host them they would probably be able to find out (probably!). But then when you have couple of hundred VPS customer and give a tiny bit about their privacy then as long as you get paid and receive no complaints why would you really go look for them?
Sites with minimal or no JavaScript are faster than sites with lots of JavaScript. The volume of JS is often so large, especially with frameworks, that it can take a long time both to transfer and to execute. I've noticed the difference to be significant on older computers or slower Internet connections, but it's even perceptible on new systems with fast Internet connections. Studies repeatedly show that ordinary users care about the speed of websites. I think this is a very good reason to shy away from making a "full client-side application" unless the benefits from that approach are significant.
These are exactly the same feelings I've had, glad I'm not the only one who saw those answers as smug...
Hoovers and D&B numbers are incredibly inaccurate for new and privately held companies. I've seen them show $20m/year companies as $1m/year and vice-versa. They don't actually know, they estimate or allow companies to self-register, along with crawling public filings and the like.

Also, btw, I tried nuggety just now and got prompted to sign up for D&B for every search on their site.

The OP method is much simpler and at least as accurate.
With a SaaS solution you don't have to worry about uptime and having your own server. It's definitely not for every one :)
This tumblr doesn't quite live up its name: http://onethingwell.org/post/97725615916/busybox

BusyBox is great and everything, but it's definitely not subscribing to the "One Thing Well"-philosophy, quite the contrary: everything in one.
This is skewed heavily by employee wages. In SV they can be 2x what they are in the midwest so adjust for location.
Really great read. One interesting point:

"What I’ve found, counter-intuitively, is that apps that embrace JavaScript actually end up having less JavaScript."

The example given is the Boston Globe with over a half megabyte of JavaScript for essentially textual content. I think this is a great example of why people are still using NoScript in 2014.
You need CyberBunker if you need your host to protect you.

If you have 20 servers in 20 different providers, who don't know who they are hosting, you don't need this.
From a business perspective, if you don't subscribe your opinion is probably irrelevant. You have 0 value to the author.
Fake ads suggest you can charge your iPhone 6 in a microwave
...which is why I prefer extensions like AdBlock, Privacy Badger, etc. to disabling JavaScript: they cut out ad/tracker cruft without destroying my experience.
I can't comment on anything but the Push notification service, but we've been super impressed; it's so much easier having our backend just call the Parse REST API and have our iOS clients register PFInstallation objects and assign themselves to channels than it was to setup enduring TLS sessions to APNS on App Engine.
Parse gets you up and running crazy fast. So it's extremely useful in that way. If you're making a mobile app the speed the SDK gives you in working with a pre-built backend cannot be underestimated.

Recently I started a project with Parse but eventually moved off it ( with some pain ). The pain points for me were random requests timing out or randomly taking 20+ seconds to respond. Also the SDK wasn't as flexible as I needed it to be ( which is typically the case with any ORM ). The forums/support isn't great so if you run into a showstopper, you're pretty much on your own.
From Wikipedia: A number of factors spurred states to require certificates of need in the health care industry. Chief among these was the concern that the construction of excess hospital capacity would cause competitors in an oversaturated field to cover the costs of a diluted patient pool by over-charging, or by convincing patients to accept hospitalization unnecessarily

It seems this bill did exactly the opposite of what it intended to.
We have audited HIPAA compliant hosting, at a reasonable price:

https://www.atlantic.net/hipaa-compliant-hosting/
App Store Video Preview Is a Gamechanger – See Why
Accessible HTML5 Video Player by PayPal
Nice site. He hasn't covered yet some well known ones, or at least I cannot find them using the search field in his site:

* http://xmonad.org/

* http://tools.suckless.org/slock/

* http://software.schmorp.de/pkg/rxvt-unicode.html

* http://www.roaringpenguin.com/products/remind

* http://notmuchmail.org/

* http://www.djcbsoftware.nl/code/mu/

* http://isync.sourceforge.net/mbsync.html

* https://github.com/Tox/toxic

* http://mcabber.com/

* https://01.org/connman

* https://01.org/powertop
Uptime for an instance that will only serve static content? do we are not just delegating to much? We are talking about a Nginx configuration and a little of sysadmin work.
Value prop is obvious: do you change your car's oil yourself or take it to the shop? Some DIYs will set this up on AWS while others will find it 'convenient' to spend $3/mo and be done with it.
Interesting, but 1917-era is (late) WW1, not WW2.

Quite a difference, not because of the size of the ships (the WW1 Dreadnought at 45,000 tons was larger than many battleships at Pearl Harbor; http://en.m.wikipedia.org/wiki/Dreadnought has a nice plot of battleship size over time), but because they had radar.
You can still show ads with JS disabled at least some of the ads systems I have used have <noscript> tags following the JS include to show something still if JS is disabled. It's far less targeted for sure which in turn leads to less revenue from them. And I think it's fair for a free resource (This does not hold for news sites behind a paywall) to require JS so that they can make money off ads to in turn support the free viewing.
I never mentioned or meant to imply strings anywhere.

I'm saying that lisp abstractions: cons, car, cdr, eq*, if, lambda... are enough to write eval in a page. To me the only reason it can be so short is that the abstractions and the interpreter are close to some sort of fix-point, an almost infinite regression in desugaring, and that's what people are thinking about when talking about code as data and homoiconicity.
I agree, but that's something you really want to learn about anyway. To quote from a job ad I once came across: You'll "know when to hack and then to engineer". I guess knowing this is one of the most valuable things as a programmer, as I constantly see people (including myself) failing on that.
> The Internet will need a new protocol for apps, rather than documents.

A bit off-topic (sorry), but that's a good point. I believe it would be great for a future version of HTML to have two 'profiles', one for documents and one for apps. The document metaphor is great for, well, plain documents, but it is problematic for apps, like Gmail. For example it can be annoying if you have JS-heavy sites which break document-related features (navigation, resizing, printing, copying).

Have a document profile where you have all the markup features, but the javascript features are possibly restricted. This corresponds to a lean version of HTML5. You know HTML6-doc pages will look reasonable and load quickly on all devices, including on ebooks and printed out.

Then have a app profile where you don't even need a document - you can just draw on canvasses if you want, but you can also create HTML elements. I imagine that people write GUI libraries for it. You have access to all fancy modern JS features, like sockets, webcam, etc.. This would be the time to change the wierd security model of HTML - a page with the DOCTYPE HTML6-app would opt into a new model, where pages don't have access to all credentials and cookies by default, so it is reasonably safe to give them net access (they can't buy stuff if you are logged into amazon in another tab, for example).

The best thing is, we can start using these new paradigms today - and maybe have nice little badges to show we are following the new "best practice" :-). Restict yourself to minimal, presentational, progressive-enhancement JS for documents, use semantic markup, check that it looks good on all devices etc.. And when you are doing a (single-page) app, it doesn't have to look like a document, but heed all the advice for non-web desktop or mobile apps - and make sure your app doesn't break navigation.
Choice: not Silicon Valley
I think this is great as well, but alas, this kindle does not seem to be available outside of the US? Anyone know?
A free market does not mean impunity. You are a free to purchase a gun, but you cannot kill without consequences.
Forgive me for assuming you aren't a Haskeller and therefore aren't part of the target audience (maybe you are), but I'll try make up for the assumption by elaborating some general benefits.

The process arguments aren't type-safe, no. But the code that uses them can be. I can also use existing Haskell libraries mixed with this (which are type-safe). For example:

tail' "-f" "foo.txt" $= withRights (intoCSV def $= CL.map (\[a,b,c] -> b <> "\n")) $= grep "--line-buffered" "^4"

This line streams lines from foo.txt, parses each one with the CSV conduit parser[1], takes the second value and then feeds that into grep which spits out only columns which match the regex ^4. Or if I wanted to match only valid email addresses, I could import Text.Email.Validate and use this conduit:

… $= CL.filter isValid $= …

Which, again, comes from a normal Haskell package[2] which validates RFC 5322 emails with a full parser. I can also just extract the domain part of valid emails:

… $= CL.mapMaybe emailAddress $= CL.map domainPart $= …

I'm operating on structured, well-typed data in between normal UNIX pipes, in a streaming manner. I think that's pretty sexy.

Finally, when I decide this script is getting more complex than a mere script, I don't have to worry about maintaining it or refactoring it. I'm already using Haskell!

There's also the personal benefit to me, my editor support for Haskell is very good. Editor support for Bash is comparatively lacking.

I don't think it's more convenient than Bash if you take a myopic view of scripts that you write.

[1]: https://hackage.haskell.org/package/csv-conduit-0.6.3/docs/D...
[2]: http://hackage.haskell.org/package/email-validate-2.0.1/docs...
Agreed, 100%, about the tone of the "community advocates" parse has answering questions and supporting the forums (their internal + s/o). Huge turn off.
How about sending binary SMS such as SIM-RFM messages?
I'no authority on this but I think you are right and gave
the best explanation, even definition of homoiconity I have read so far: You can take the output of eval and pass it back as further input to eval. In other words input and output of eval must have the same data-type.

A good example is JavaScript, often called a "lisp-like" language. In JavaScript you have the function Function() which takes a String as input and produces a Function. Thus a JavaScript program can create another program which it executes within itself. But it is not homoiconic: input of Function() is a String, and its output is a Function. You can not pass the output of Function() as an input to another call of Function().
(Disclosure: I'm a co-founder of Aptible.)

As noted in other comments, most of HIPAA is not technical. Most of the requirements relate to risk assessment, policies, training, incident response, etc.

With that in mind, I'm going to quickly run down all of the major moving parts and then cover some of the technical considerations for setting up a server.

HIPAA has three main rules you need to comply with:

1. The Privacy Rule - Governs the use and disclosure of PHI (protected health information). Applies to all forms of PHI (verbal, written, electronic, etc.).

2. The Security Rule - Governs safeguards for electronic PHI

3. The Breach Notification Rule - Governs your responsibilities during a security or privacy incident

The Security Rule has a general security standard, some documentation/retention rules, and three sections of safeguards. They are:

1. Administrative Safeguards

2. Physical Safeguards

3. Technical Safeguards

Some of the safeguards are mandatory. Some are "addressable," meaning if you don't implement them you must document why you chose not to and what other safeguards you applied instead.

Most likely, you're going to start with something like the following for your servers:

1. Sign a BAA with any service provider who is going to touch PHI for you.

2. Restrict physical and logical server access to authorized individuals. Document how you restrict access and why the methods chosen are reasonable and appropriate given the risk posture of your organization. (There's a LOT packed into this step.)

3. Log all access and data modification events. If you use a logging service that isn't HIPAA-compliant, make sure you're not including PHI data you send them.

4. Encrypt data at rest and in transit, including inside the network perimeter. Document your network topology and access points.

5. Implement backups according to your organization's HIPAA contingency/disaster recovery plan. Document the backup scheme.

A few caveats:

- I haven't addressed application-level security. The same requirements apply, but the implementation differs.

- Your customers will demand additional safeguards that aren't in HIPAA.

At Aptible, we help with all of this, plus all of the other requirements (risk assessment, policies, training, etc.), so you can get a complete handle on your compliance status.
Show HN: Tweetd – link blog from links you shared on Twitter
Security, privacy, and bandwidth.
Nginx and Server Side Includes
And rightly so. G forces absolutely will kill you, just not from the speeds a car can attain. Why on earth WOULDN'T we be cautious with a new technology that we know has the potential to cause permanent damage?
Remote Manual Testing on Any Android Device
Here's how WetShaveClub grew a subscription box to almost $100k in revenue.
It's not just "the few" that browse with javascript disabled, though. It's also about making sure you play nice with assistive technology, that your content is visible to search engines, that you haven't broken URLs and browser history...

With HTML5, it's possible to do all this in a single page app. But it's a lot of work that you might not do or might get wrong, that you get for free when you treat web pages like web pages.
Totally agree. Of course there is going to be more backlash if this is described as a "replacement." What's wrong with just offering doctors better tools to do their jobs? We offer them surgical tools, why not software tools? That's a less threatening description...but also a less compelling headline.
True. I've seen very succint python eval, and my 'favorite' would be https://news.ycombinator.com/item?id=3511100
Legal Fiction
Founder of BitBalloon (https://www.bitballoon.com) here.

Always interesting to see more and more startups popping up in the static hosting space. Since we launched a year ago there's been at least 6 other entering the space.

Right now it looks like your main selling point is price.

Think carefully about whether that's the way you want to go. The real competitors here is the humongous shared hosting market, and the big players there have much deeper pockets and far better economies of scale than any startup.

With a $1/site price you'll pretty much never have a chance to make paid advertising a viable customer acquisition channel and as someone else mentioned, think about what the price of giving any kind of support will be. The lower end of the market will (in my experience) also be the place where people will need the most help with stuff like DNS setup, or basic issues such as not having an index.html file, etc, etc.

Good luck!
Yes, higher rank types are no problem for C# or Java generics. It's higher-kinder types that are unavailable.
The cliche "there is no country called Europe" very much applies in this case. Seed investment happens almost exclusively on the national level, with local investors and start-ups who's initial target is the local market, regardless of how big their long term ambitions are.

The local investment and startup scenes vary wildly across Europe. Not to mention the wildly different states of the various economies.
"Sheer gravity"? You're doing something that an enormous number of Americans do every year. Small business employment is a gigantic fraction of the economy. The difference between you and the owner of a barbershop is that the barber doesn't work in an industry that tricks him into believing he might be a millionaire in 4 years. The consequences of failure, on the other hand? Pretty much the same.
That's what I figured. Thanks for your input.
Regarding interactivity, here's a short demo of using shell-conduit as part of my Haskell shell called Hell:

https://www.youtube.com/watch?v=eaNr03yI4vE&feature=youtu.be

It's a REPL that will automagically run conduits if it sees them. And also provides function name and file completion via tab. So you can write ls S TAB and get ls "Scripts/", like I do in the video. It also tracks if the directory changes and updates the prompt, has a history, etc.

I don't use it as my main shell (yet), but it's available to me to experiment with.
For more background details, see http://plato.stanford.edu/entries/newton-principia/#NewLawMo... .
Did you really mean to write a comment that implies that entrepreneurship might be harder than caring for someone dying of Alzheimers?
iOS 8 jailbreak with Evasion jailbreak
Debt-financing route helps keep business in the family