csmajorfive

These were all developed on the Parse team. Naitik is a huge contributor :)

I believe we're the only ones doing using Go in production at Facebook. Join us! https://parse.com/about#jobs

Thank you for your reasonable perspective. This open source criticism seems particularly endemic for developer tools that aren't backed by a cloud service. There are very, very few companies that have made money with open source tools in this space and they typically require huge VC investments to get to a place where the product is good enough to warrant large enterprise support contracts and professional services.

You can just watch it directly on YouTube. https://www.youtube.com/watch?v=Mp1hpMOjk6c

If you could direct some improvements to our docs, where would they be?

That's a totally fair assessment.

I just mean to say that we've prioritized it above all else and are really crunching to make it a non-issue for our developers. Our traffic has exploded in the last year so we need to rework some things.

Hey there, sorry to hear you're taking off.

I'd love to hear more about why you think we're nonchalant about downtime. We definitely need to improve reliability and are working hard to do so but also spend a lot of effort on writing up detailed postmortems (e.g. http://status.parse.com/incidents/j336l474l8h4) to be as transparent as possible even if it's painful.

You're right that there are some applications that are a good fit for Parse and others that aren't. We have many social-esque apps that are doing fine so I'd love to hear more. That said, we know it's not "one size fits all" and are working to productize/integrate some Facebook technologies that should make fanning out and other things way better.

Feel free to drop me a note at ilya@parse.com.

Hey there, I work on Parse. This is good feedback.

Improving reliability is our #1 priority right now. The bulk of our team is solely focused on it. We've made some good progress and hope to have things in a much better place by the end of the year. You can follow it all on our status page. We try to be very transparent with post mortems and such.

That bug sounds nasty. I'll take a look to see if it's still an issue but I believe it was fixed a while ago.

The Facebook bugs flow has its pros and cons but I believe it's been great for our community on balance. We have an awesome team of folks triaging and repro'ing bugs and interacting with the community thanks to our integration there.

Drop me a note at ilya@parse.com if you have more thoughts about the dashboard or anything else.

It's awesome. I have a DK2 at home and this is so much better.

$10/gb is for our database offering. Our file storage is the exact same price as S3.

"implementation of using the tags goes through Facebook"

No, it doesn't. You can use the SDKs without any dependency on Facebook.

Omnilinks are cool. I hope we can all work together to make mobile better.

Do you feel that way about all acquisitions? About Parse? About Facebook? We've invested a ton of resources into Parse post-acquisition and continue to do so.

Fair enough but what do you think about folks like Heroku that have stuck around for years post acquisition?

Sweet :-)

You could just use Parse. We're not going anywhere.

I came here to say this. A founding CEO should never have the highest salary in the company. Value your own equity more!

Are there any startups working on anti-piracy technology for drones? Imagine criminals targeting high value deliveries and knocking these guys out of the air with their own drones.

In my experience, it's neither. It's a series of conversations about a potential shared future. The most analogous process is dating.

Everything in those quote is correct. It wasn't part of our game plan at the time. It was never our "game plan" in general. In fact, at the time, we were planning the strategy for a fundraise.

We just tested it. Here's what it looks like:

{ "results": [{ "photoId": 0, "useLocation": true, "username": "Kdhddv", "createdAt": "2012-05-08T22:41:13.187Z", "updatedAt": "2012-05-08T22:41:36.454Z", "objectId": "zeAsRRxu61", "sessionToken": "y67zp3emfcpto44v4qp0mvqyf", "bcryptPassword": "$2a$10$6XZsksIvrUW5vW9j86pbK.spXCdJFDyhiQlqg/yFNhD8FkwEslwHu" } ] }

lol

We've had extensive discussions with Facebook about this. We (Parse) have a pretty strong view on the pain of breaking changes.

We're staying.

I apprehend it and it's an important issue to address. So, I'm addressing it.

We export password hashes right now, as far as I know. Is that not the case?

That was a talent deal top to bottom. This isn't.

I can't share revenue numbers but we picked this route over multiple Series B term sheets. So, that's a measure of viability.

We're not changing anything. We're not going to suddenly lock in your data, share it somewhere you don't want it to be shared, or anything like that.

Why? We're not going anywhere. Email me if you want to chat - ilya@parse.com

We won't.

Why? Email me - ilya@parse.com