Since CloudFlare does free bandwidth, I could cut a lot of costs by using them just as a CDN for image assets, but performance is a concern -- how long will they cache my files? :-/ Wouldn't it be funny if I did something like this:

upstream <=> nginx proxy cache <=> CloudFront <=> CloudFlare <=> visitor

:o

@height8 Awesome tool. I use it all the time. It's the only Java app that runs on OS X that I'd recommend.

//

@height8 (Not to mention the simplicity of installing your own root SSL cert and using a MITM proxy…)

https://www.charlesproxy.com

:)

//

Ah, I see, you're planning on banning bad clients based on how much spam they output, so using someone else's app token to spam is a concern.

// @height8

Honestly, I think you should have just gone with a more OAuth 2-compliant spec. It looks like you're trying to emulate it, but not really adding anything. I suppose you're skipping out on the authorization code juggling for simplicity?

What's wrong with having the client ID in the binary, as long as it isn't the only factor being used for service authentication (the client_credentials grant type in OAuth 2 terms)? This happens all the time especially with client-side JS apps. I'll have to take a deeper look in to the docs.

// @height8

Nowhere yet :-( The plan is to get it out by the end of next month. I can put together some screenshots sometime soon, though…

//

No, it isn't similar -- it's a private photo sharing service that will also keep your photos safe. For $40 /year you get 250GB of storage (it isn't released yet, though, so those numbers may change haha)

//

Once I get some crazy scale, though, I'm going to have to seriously consider building my own storage pod things. We'll see how things work out. :)

Honestly, if it weren't for B2 I wouldn't be able to get this off the ground. It's why I can offer a $40 yearly subscription instead of a $200 yearly if I had to use something like S3