mikeknoop

It's a great day to be NewsBlur -- good luck with converting the new traffic!

The reason this product doesn't exist "already" is because it's not the type of searching airline's preferred customer need.

Airlines prefer business class customers (routine flights, willing to upgrade to expensive business class tickets) and those customers typically search for small 1-2 day windows.

Can source maps handle source files in a different location than the compiled JS file? In my few minutes after installing, I didn't immediately see a way to do this.

After reading the docs and comments, this was the comment/explanation that made the light-bulb click.

I think this is just someone rehosting Json Blob (http://jsonblob.com/) and throwing an advert on the right-half column.

Or maybe the other way around?

https://github.com/josdejong/jsoneditoronline 200+ stars

https://github.com/tburch/jsonblob 50+ stars

Awesome stuff. Is there an authentication mechanism built in somewhere?

I'd to love to get this on Zapier, what can I do to help move things forward?

What's worse is when OAuth providers force the refresh tokens to be refreshed! Many OAuth providers are now requiring user-action (ie. re-walk through the oauth popup) every x months to get new refresh tokens.

Same with YC. A few founders don't make it through the three months, some companies merge, others dissolve completely.

I agree, the whole interview is really well done and worth watching.

After writing this piece and before it went live yesterday, I discovered a really interesting interview between Leo Laporte and Alexis Ohanian where Alexis shared their own co-founder dispute system at early Reddit:

http://www.youtube.com/watch?v=GjozYFToIM4&t=959s

tl;dr early Reddit used a technique mentioned: defaulting to the person with the most expertise.

Do you guys do mixed groups (2 guys, 1 girl -- etc)? In the future? Your messaging tries really hard not to label Grouper as a dating service but (3 girls) and (3 guys) is pretty transparent about what the intentions are for the two groups.

Lot's of growth avenues, looking forward to seeing this grow.

I've implemented something similar in the same manner (over-riding `new`). The original idea came from here: http://backstage.soundcloud.com/2012/06/building-the-next-so...

One implementation detail I ran into is how to detect dupes. When you have Backbone Models, this is easy: every model has an `id`. But say you want to apply this same singleton behavior to a Backbone Collection, which don't have natively have `id`s. I saw two options:

1. Assign an `id` to the collection when instantiated (could just be a string, so that you can force a singleton only when you desire it).

2. De-dupe based on `instanceof` checks. The downside here is you always get a singleton even if you might want a one-off instance of a collection.

Are there any other options? Can your Identiy Map handle collections?

Well that was unexpected, hit 1 billion and the site started redirecting to porn sites.

Haven't seen these mentioned yet, and I recommend both:

Powergrid: Unique because there are no dice involved; a game of economics

Steam: Unique because there is a bank (partly tied to your score) that you can borrow against to build pieces faster

I've gotten https://github.com/cyberdelia/django-pipeline working recently. It's a young project but it's supporting a heavy frontend asset pipeline for us now and working great.

I could see a ticking countdown timer being a nice addition to grab the users attention. Presumably if this widget is on the page, it is the main purpose of the page. Way to ship! Keep us updated on how it goes.

Sure. I'll start with this: as far as client libraries go, Braintree is doing it right. Because it's the only thing they support, they are incentivized to make sure it is feature complete and bug free.

SSL: It is not the onus of the vendor to ensure people are properly securing requests. I have seen horrendous things done in the name of "security" but it only adds headaches. Fix this at the client level. SSL everywhere is sufficient. By extension, vendors often introduce mechanics because they want to make the world better: http://xkcd.com/927/

Platform Support: I think the counter-argument is community client libraries, which the OP is correct: they are worse. The stability + scaling + support issues mentioned by OP can usually be solved by better API design and better architecture behind the scene.

Backwards Compatibility: OP claims you never have to update your code if you use their client library. This is likely true. Good API design would dictate not breaking exposed endpoints unless there is new functionality to be had. In this case, to take advantage of any new API features, you'd still have to update your code. No cost savings are had either way.

We (Zapier) are in a particularly good place to comment on this. We have implemented about 70 very diverse web APIs in-house. Early on, we used client libraries because they were easy and convenient. That decision bit us, hard. (Most) client libraries are un-maintained, opaque, and difficult to extend.

We spent many months ripping every client library out down to the raw requests. We are in a unique position because of how many APIs we have to support, but the overarching advise we give to people designing APIs:

If you are deviating from the norm, you're doing it wrong.

REST APIs are nice because you can infer how to communicate with the API out of the gate. APIs are a pain and you only introduce headaches by not doing things in a sane, conventional fashion.

Two things you can do together to help, but need Backbone edge version (master) for the second, at the moment:

  1. myModel.on('change:title', this.render, this); // inside `myView`
  2. myView.dispose(); // when you are done with `myView`

This will automatically remove all the referenced binds onto `myView` and simply removing the root view as OP mentions is sufficient.

Do I know you? I'd email but you don't have one listed in your profile, please consider adding one!

Lockitron also showcases the slider issue in their product video: https://www.youtube.com/watch?feature=player_embedded&v=...

So let's say I lose a limb at some point in the future. How does one go about applying for these "research" positions? It seems like it would be an interesting hack to get into a mind-controlled robot limb experimental program instead of the traditional prosthetic limb.

Someone noticed the spinner! Every time someone manually clicks "spin", we log it (we do not log the automated first spin):

http://i.imgur.com/LCFu6.png

We have so many apps and requests every single day we have to prioritize what people are willing to pay for first. Wappwolf does have better permissions here (which we'd also like to support) but they don't have 117 apps to support alongside it. Startups are not asking for this stuff maliciously -- there are only so many hours in the day and we have to prioritize.

Here is another article from a Silicon Prairie News which also has more details: http://www.siliconprairienews.com/2012/10/zapier-raises-1-2m...

We figured some people may appreciate the back story especially given the light-on-details funding announcement on TechCrunch.

Yup I highly encourage anyone interested in the back-story to give the above blog post a read. It is an overview of our last year (from inception till now).

EDIT: HN link here http://news.ycombinator.com/item?id=4723588

One of us is (me) for a while longer. Also we hired our first in Chicago: https://zapier.com/blog/2012/10/24/zapier-team-grows/

I know of at least one team that would appreciate this.