tonyx

This is really cool. How do you handle changes of pricing with something like this?

Interesting! Is there an escape hatch to drop down to raw Stripe primitives if someone needs a feature you haven’t modeled yet?

This feels like something many teams eventually build internally — curious how you’re thinking about long-term API surface + compatibility with new Stripe features.

How does this compare to other open source integration platforms like Nango or Airbyte?

Hey everyone, we were doing some repo admin and briefly changed the visibility of the repo from public -> private and back to public, then discovered in horror that we lost ALL the github stars and forks! Googling suggests that others have ran into this issue too and github is not able to restore it (see https://www.qovery.com/blog/we-lost-3800-stars-on-github-in-...).

Could you help us by starring our repo and perhaps spread the word? Would really mean a lot! https://github.com/useVenice/venice

PSA: Never change a public repo to private, not even for a moment, because doing so means you will irreversibly lose ALL your github stars and forks, there is no going back! :(

Can you comment on cells and rows ? Document columns?

Congrats on the launch!!

if it's postgres, then 5 mins as shown in the video :) Otherwise what data warehouse are you thinking of and what's the use case behind it?

Can you clarify what you mean by "not out of box" API? We haven't built an integration with Argyle yet but once we do it would be the same experience as Plaid

This is a lesson that needs to be learnt and relearnt over and over again, with increasing level of clarity each time.

The largest size we tested was 150mb, that's why the x-axis of the graph ends at that point :)

Impact can exist regardless of the underlying cause for impact. It may be because someone's device is full, or does not want to download over cellular, or any other myriad of factors. But you'll still lose an install statistically speaking.

@CharlesW we mostly focused on the facts and running as controlled of an experiment as possible without bias or drawing conclusion on exactly why heavier apps get downloaded less. Though my personal guess from working years in the mobile app space is that users are surprisingly conscious of data & disk usage. Not everyone has unlimited data or 128GB storage iPhones.

We like to embrace different technologies and use each for its strength. MongoDB is excellent for a whole class of use cases and we like it a lot, but we also use other persistence solutions as well. Check out Polyglot persistence post by Martin Fowler, it's an awesome read. http://martinfowler.com/bliki/PolyglotPersistence.html

Hi troymc,

Interesting idea. We might look into that sometimes. Our current focus is on delivering a great experience to end users so we are integrating services ourselves one at a time. Don't want to get too far ahead of ourselves. :)

We actually checked out Jolicloud when they launched. Kudos to them that they have built a stunningly beautiful product. Our focus however is less on giving you one place to view all of your content but much more on organizing them, sharing them and making sense of them.

Kirsty is one of the most amazing people I have met while at YC. Low profile, high impact.

The KFC looks very delicious, haven't had a meal there in a long time. Yums.

Hi james, we just installed Mountain Lion and can confirm that this issue does indeed exist. We're working on getting it fixed and will get back to you.

Hi drobati, I'm not quite sure what you mean. Could you give us a bit more detail?

Hi jameswyse, thanks a lot for offering to help. We have yet to test our app on the latest Mountain Lion. We will install Mountain Lion tomorrow and test the app. Feel free to email us at support@collections.me and we'll drop you a note once we finish testing the product on mountain lion.

Hi jc4p, the product is still in beta. (If you go to the about page for the product you'll see that it says Beta2) The reason we removed Beta from the name of the app itself is that we started using Sparkle for auto updating the app, which seems to break if the app name changes. If we keep Beta in the name of the app, we won't be able to automatically update you to a full version later. That's why we removed it.

About spreadsheet, we know the experience is still not great and could use a lot of work. Stay tuned and we hope to have something for you in the next couple of days. As for security, since last launch we've consulted with Heroku security team, implemented password policy and done a great deal of other things to keep infrastructure secure. We have an upcoming blog post dedicated to security planned which will give you more details about how we keep your data safe. We'll let you know.

Hi newman314, we've consulted with Heroku's security team and implemented all the best practices suggested by them. We started enforcing a password complexity policy for all of our accounts (Heroku, Amazon, codebase, database, etc). We got an upcoming blog post on security planned in which we will inform you much more on how we keep your data safe. Stay tuned!

We should buy you a copy of Mountain Lion so you can test out our app :)

Try double clicking on either the preview or the list of documents. That will get you into the edit mode right away without having to click on the edit button

We are using Google's oauth2 protocol. No user password is stored or even ever transmitted to our server.

thanks xb95, it took a minute to take effect, but issue is now fixed.

Hi xb95, thanks for alerting us to the issue we've turned off debug mode and reset our database credentials. We are looking through the database server access log right now and going to make sure that 1) all connections were made from our own servers and 2) users in the timeframe affected will be notified of the issue access token revoked immediately.

We've turned off debug mode and reset our database credentials. We are looking through the database server access log right now and going to make sure that 1) all connections were made from our own servers and 2) users in the timeframe affected will be notified of the issue and guided to resolve it as soon as possible

Hi thomas-st, thanks a lot for bring this up. we just fixed the issue and changed credentials on the server as well. All transmission also happen securely through HTTPS and contents are only stored on Google's server, not ours.

Right click in the list of documents and you'll see the option to sort by title, date created and date last modified. Let me know if this is helpful.

Well said. I still go through that cycle every time I try to learn something new. Cocoa was really frustrating, especially as the debugger threw me into compiled assembly code. But once I got through the initial hurdle it became much more fun. Had that experience with Django lately too. The best (arguably only) way to learn seems to be learn by doing, reflect(which includes summarizing mistakes, reading tutorials, talk to expects, etc), and do some more. It tends to work out best when you have an end in mind, a real project that you are working on, which is what a lot of coding tutorial fails to deliver.

My intuition doesn't feel good about this. Whatever Tim Cook says, if apple draw attention away from product innovation into optimizing for financial markets and pleasing shortsighted loyalty-less public market investors, it would no longer be the Apple that we have come to know over the past decade.