krallin

Lots of very useful tips there!

There's one that I think could be improved on a little:

    Uploads should go direct to S3 (don't store on local filesystem and have another process move to S3 for example). 

You could even use a temporary URL[0,1] and have the user upload directly to S3!

[0]: http://stackoverflow.com/questions/10044151/how-to-generate-... [1]: http://docs.aws.amazon.com/AmazonS3/latest/dev/PresignedUrlU...

Seems like Blizzard might be coming to mobile with their latest game, so those higher quality, richer games may eventually come to mobile as AAA studios get on board (with the actual games they are also pushing on other platforms).

I think you hit the nail on the head here: offering the option to buy less server time if you don't need to wipe data is probably reasonable.

Now, the problem here is that DO turned that choice around, and are therefore not providing security by default, but offering you the option to pay more to get it.

Additionally, this is poorly advertised (the API docs do not clearly state "Your data may be accessible by other users!"), and that explains why many customers are (reasonably) a bit pissed at DO.

If you e.g. try "gmail.com", it's blocked. Same for nytimes.com, or stackoverflow.com. I think this has to be the point.

Now, of course, this doesn't prove the "majority" of the internet is blocked.

Also, some twitter links are broken

e.g. http://availability.is/for/sebinsua links to http://twitter.com/http://twitter.com/sebinsua

Or CloudStack? Eucalyptus?

Or look at Glue : )

https://glue.readthedocs.org/en/latest/

Well, that's what our software does too, so I didn't really have an incentive to do so!

Now, judging from how busy the engineers are here, I'd say this is a bit harder than it seems!

To add a bit of context to Anthony's post here (I'm the guy who wrote the blog post on the Eurovision).

GCE Load Balancing uses a single IP address, you can point your DNS there and forget about it.

What Anthony's post shows is that this IP address will be able to serve 1 (upwards?) of 1 million requests per second.

This matters because you have control over scaling your backend (design properly, add more instances), whereas you don't have full control over scaling your frontend.

Indeed, a problem we had during Eurovision was that mobile providers (it was a mobile app) would cache the IPs of our frontend Nginx servers, so scaling those wasn't as easy.

So this new GCLB essentially "solves" scaling your frontend. That's something I'd care about ;)

Hope this helps shed some light here!

Google Compute added an ELB equivalent (the "GCLB"), but it doesn't have autoscaling built-in.

To get autoscaling, you can either roll your own — Google explains how here[0] —, or use a multicloud autoscaling solution (disclaimer: I work for such a provider).

[0]: https://cloud.google.com/resources/articles/auto-scaling-on-...

I thought pypy had a sandboxed mode, did you get to experiment with it? if you did, what did you think?

Same on United — we actually got to watch the full boot sequence (^ ^)

I'm not an expert in embedded displays, but I assume you'd simply run a webserver on localhost.

It's not, but I came here to ask the same thing before it finally loaded!

Even if they did, would they actually award the bounty even though the bug was directly taken to a blog post, and not reported to them first?

I may be mistaken, but I was under the impression that there generally was a tacit agreement that you only get the bounty if you don't go public with it before it's fixed.

I think that what they wanted to say is one of: cookies don't really work for in-app tracking, cookies don't carry over from laptop to smartphone.

Cookies obviously work in mobile browsers, but browsers are only a part of the picture on mobile.

It's amusing that you could replace "UX" with "Marketing" in that article, and it would make sense!

(except for the 4th myth, which may need a little bit of rewriting)

Well, that's only if you understand the risks! ;)

The invalid certificate was a cloudflare one, so probably acceptable : )

(and it's always better than accessing over HTTP)

If you get the SSL warning on Chrome, you can enter "proceed" and then press enter at the keyboard.

Even if there's no "I understand the risks, let me proceed" button, this will work.

Ha! Nice to see you here : )

The except clause is in the "dropbox_auth_finish" view. That might be personal paranoia, but I'm sure that every single timeI think "It's OK to put a `except:` here", it eventually comes back to bite me (without exception ;) )!

I do understand the motivation to keep it minimal (and I think the Flask boilerplate is indeed well understood), but putting together the sample without the Dropbox SDK imports (specifically without an IDE) might end up being a bit more bothersome than optimal : )

Just personal opinion, of course!

I wonder whether it's intentional that the tutorial isn't "copy-pastable".

Specifically, it does not spell out any of the imports, and uses very large except clauses.

Doesn't quite exactly work on a non QWERTY keyboard : (

Still awesome, though!

Looks more like support content for the book than the source code itself, or am I missing something here?

Facebook actually has an option to "memorialize" accounts: https://www.facebook.com/help/150486848354038

For larger companies that usually don't rely on VPS providers and the like, AWS can still be a compelling offering for new ventures, as you don't have to commit resources (capital) to in-house infrastructure for a project that might not work out (as it's opex, not capex, just shut it down if it fails).

Or you can just dynamically launch an EC2 instance just when you need a VPN : )

Is there a list of todos / easy picks for new contributors to get started with?

I would be surprised by Guido Van Rossum left Google to work on "some Python duct tape" at Dropbox ; ).

This is meant to be a series, so the second article (which talks about the Image Store) is found here: http://blog.scalr.com/post/55282745486/cloud-native-the-imag... (Didn't want to spam post!)

I would personally recommend the new one (but take this with a grain of salt: I work on it). I use it daily to build www.scalr.com.

It's got more tests, and it succeeds at building the Cactus examples like the old one. The only thing that's not stable in it is the "serve" mode.

I'm working with Koen (the original author) to get this into the main repo.

--- If you use it, and run into any issue, get in touch with me: thomas [at] orozco.fr