Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

So the Parse platform allowed me to get and implement my iOS app in under a month, getting my MVP out there. If you want to really assure users that they can be comfortable, and to not flee, make it so we have access to our user's password hashes.

Before, the Parse team said they were thinking of implementing it, but now there's no contest. Either you guys allow me to take my user data, or we're done, and I'm completely separating from you guys, and wouldn't recommend anyone building on the platform.

So, let me have ALL access to my user's data, and we can keep hanging. Otherwise, we're done.

As it is, I'm making plans already to move, on the assumption you guys won't let me get my user's data.



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


Nope, not from the last export I did a few weeks ago. Please check and make sure, because this is a crucial link to the level of trust with the continue support of Parse and FB


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" } ] }


Awesome! Thanks for checking and verifying, awesome to see the response.


It would be fun to see this aqcuisition cancelled because of a single comment on HN. Oh, well...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: