bryanh

39 ms·

361.
3 Dudes from Missouri Built a Product, Found Paying Customers, and Got Into YC(zapier.com)
91 points by bryanh 14y ago|21 comments
362.
by bryanh 14y ago
It does, at least filtering and accessing them if they have a ForeignKey to User.
363.
by bryanh 14y ago
No worries, we love the ideas around your product. To be honest, its not even a direct need of "database level integration", that is just where it ends up. Going to the DB level removes the "crap, now we have to get all the data into X serv
364.
by bryanh 14y ago
Totally agree, it is crazy useful! Also agree it would be nice if it could be based off of something besides User (Django's ContentType framework might be the right bet there).
365.
by bryanh 14y ago
We have an open issue to work off of signals [1]. What would definitely make it more event driven, but might make it a lot less efficient. [1] https://github.com/zapier/django-drip/issues/1
366.
by bryanh 14y ago
Again, we would like to reiterate: we would have loved to buy this. But Wade outlined the reasons we couldn't scratch our itch with products like yours (or your competitors).
367.
by bryanh 14y ago
Absolutely, you have full Django templating abilities.
368.
by bryanh 14y ago
Drip will definitely have support for Django 1.5's custom User models.
369.
by bryanh 14y ago
The mechanism for doing this is a total hack on Django's ORM. We build a bigass list of all possible JOINs and concat them together: some_model__another__title some_model__another__date some_model__another__description You
370.
by bryanh 14y ago
In the spirit of GetVero, Intercom.io and Mixpanel, here is our done-is-better-than-perfect take on drip campaigns. Definitely check out the docs [1] and the demo [2] for a better idea of what it does (and doesn't do). My favorite feature i
371.
Show HN: we open sourced our Django drip email app(github.com)
126 points by bryanh 14y ago|33 comments
372.
by bryanh 14y ago
Some parts of the milk are discarded when making cheese.
373.
by bryanh 14y ago
Wow. That is definitely crazy. At least in the end the serialization is fairly straightforward. Some of the worst API's we've seen are definitely due to lack of proper documentation (or completely undocumented features). Hopefully we can st
374.
by bryanh 14y ago
Shameless plug! We just added support for this on Zapier: http://zapier.com/zapbook/github/ We'll add some links to specific templates, but some good examples of ways to use it might be: * Send SMS for specific mentions (we suppor
375.
by bryanh 14y ago
Same here! Even trying to boot up some replicas is painfully slow.
376.
by bryanh 14y ago
Us too. RDS bit the bullet for us.
377.
by bryanh 14y ago
Careful with the .io domain, though I've never heard of them shutting down a startup over content, their rules do state: No .IO domain may be used, directly or indirectly, for any purpose that is sexual or pornographic or that is
378.
by bryanh 14y ago
Writing code makes repetitive tasks easier: if you want to pump out hundreds or thousands or millions of variations on a graph (using different data, etc...) then drawing it by hand is infeasible.
379.
by bryanh 14y ago
I must say, SendHub and co have done a pretty remarkable job. Their product is superb, I highly recommend just trying it to see how to do onboarding on a fairly complex service (considering multiple people & phones are involved).
380.
by bryanh 14y ago
Really? Downvotes? Is HN becoming Reddit? He isn't spreading misinformation or misleading anyone, just offering a different viewpoint (and one of a hosting company, mind you).
381.
by bryanh 14y ago
Of course!
382.
by bryanh 14y ago
We're planning on releasing our drip campaign app for Django under the BSD license one of these days. I must admit, it is rather cool.
383.
by bryanh 14y ago
For the average user & developer, PayPal is the same mess today as it was 5 years ago. That is the stagnation.
384.
by bryanh 14y ago
Kind of disappointing how stagnant PayPal has become. I know innovators dilemma and all, but it seems like their peak was the ability to properly deal with fraud & security (a sort of a right of passage for all companies that deal with
385.
by bryanh 14y ago
Zapier co-founder here: its funny, but we get this sentiment a lot (for example, from Lu @ Ronin). Its pretty incredible to see developers get these working and we're truly humbled to see the sorts of guys developing on it (Hubspot, Podio,
386.
by bryanh 14y ago
For a while I was a bit worried that GitHub had just ran away with the prize and no one else was bothering. It is pretty obvious that Google isn't interested in improving Google Code and that Sourceforge hasn't aged a day (that's not really
387.
by bryanh 14y ago
Zapier (YC) - Mountain View, CA - full-time, remote possible - developers & designers We want to bring the power of APIs to the masses and make all web apps talk to each other. We're primarily Python & Coffeescript touching a bit of
388.
by bryanh 14y ago
I think a slew of strategic screenshots would help. Too bad that browser history inspection hack is a thing of the past, building a database of examples that rotate based on the web apps they use would be crazy useful.
389.
by bryanh 14y ago
It was released today, which is probably why this is making the rounds again. I wonder how many YC alumni bought it for their parents/family?
390.
by bryanh 14y ago
You should really play that up on the homepage, maybe a slew of screenshots of useful locations. Like for any of the 100 help desk softwares that exist out there... :-) For example, I immediately thought "how often will I run across a custo

More ›