David Hawley

+1 I am also looking use this to cleanly implement Accounts.onCreate on the client side

As far as I can see: - emit from server is received on server and client - emit from client is only received on client

The new Dropbox API is very different, so it will take a good understanding to change the cfs:dropbox shim. I might just wind up moving off cfs because of its...

The error of not loading files is not only images, it also happens for text and PDF with cfs:dropbox. It seems to be all small files are affected. The problem...

I have a similar problem, but for small files. I am deploying to meteor.com, and decided for the dropbox store for fallback access to the files. (Files uploaded to the...

I tested on a 9 byte text file and traced it through the cfs:dropbox and dropboxjs libs, then lost it somewhere in compress.js (part of npm connect module in meteor...

I have the same issue, same error message. The strange thing is despite the warning message, it works on development; it doesn't work on (<myapp>.meteor.com) production. My use case is...

Ok, I came up with a hacky workaround by wrapping `SimpleSchema [CreateSchema(defn)` instead of `new SimpleSchema(defn)]` so that I can specify the labels as `{key: .., message: ..}` which are...

No, the above dynamic approach doesn't work with the messageFormat's static scanning approach. None of the labels in the above appear in the /translate. So I added another syntactic marker,...