This is jaw-droppingly offensive and contributes to an unmistakable pattern of deception and avoidance that makes it damn near impossible for me to conclude that Yale today is anything but a vilely misogynistic, self-regarding institution utterly lacking in moral compass. If the Yale community wishes to restore the good name of a once great American institution, it should demand the immediate resignation of the current leadership. It has been on their watch (as well as that of their immediate predecessors) that rape and sexual assault have been so thoroughly trivialized, so it is high time they are held to account.
Extremely well-deserved! We use ZenPayroll over at http://collections.me and it 100% lives up to the hype. It's going to be a true pleasure watching it grow into a titan of the industry.
Thanks, Brad, for the feedback. We addressed many of the bugs people found in prior releases, but will look into this spreadsheet issue (perhaps you could describe it in a bit more detail at feedback.collections.me?). As for the site, please refresh and it'll self-correct, but we're aware of that bug and are working to make sure it never happens.
Hi! Fair question. We're trying to build a universal Finder, a single point of entry to all of the digital content you have that's currently dispersed across an ever-growing number of cloud and web services. A bit of this was present in a TechCrunch article earlier today (http://techcrunch.com/2012/07/24/collections-for-mac-instagr...), but we're currently writing a blog post that will more fully explain what we're up to.
Hi Thomas, just following up on this. After fixing the security issue, we revoked access for all of the potentially affected user accounts and emailed users individually to apprise them of the situation and the steps we took to address it.
Hi bdittmer, we don't store any of your content, nor any of your passwords. We only store meta data that describes the organization of your documents and do so server-side so that we can add features in an upcoming release that we otherwise wouldn't be unable to add.
Hi Xb95, we first removed the heroku add-on and thought that it would automatically destroy the database, but that turned out not to be the case. So what we did to fix the issue was purge all of the tables from the database. Now the credentials still work, but they reach an empty database without any content. We're working on revoking the access token for all affected users right now. Thanks for helping us through this.