Nick Johnson

less info
stack exchange network profile network profile
101 reputation
1
bio website blog.notdot.net
location Sydney, Australia
age 30
visits member for 2 years, 11 months
seen Sep 5 '11 at 4:46
stats profile views 11

Software Engineer at Smart Sparrow, a startup in Sydney, Australia. Enthusiastic about software engineering and computer science, especially when it comes to interesting algorithms and approaches to solving difficult problems.


7 Actions

suggestions reviews revisions comments badges posts accepts all
Sep
5
 comment Google App Engine [app]s - We are all on the same quota!
@systempuntoout I'm positive - it's always been the case that although you can set part of the user-agent string, you can't remove your App ID from it.
Oct
31
 comment Google App Engine [app]s - We are all on the same quota!
@systempuntoout In an ideal world with unlimited IPs and no cloud solutions with shared egress, I'd agree. As it is, the world isn't ideal, and anything that limits on IP either needs to special case large heterogenous sources of egress traffic, or implement keys/access tokens.
Oct
31
 comment Google App Engine [app]s - We are all on the same quota!
@Steffen That's correct - distinguishing on IP plus AppId is the right way to limit per 'user' for App Engine sources.
Oct
28
 comment Google App Engine [app]s - We are all on the same quota!
For reference, we (App Engine) include the App ID in the user-agent header, and we don't let users set the user-agent header on outgoing requests. If the IP comes from our pool (_netblocks.google.com), you can trust that the App ID in the user-agent is accurate.
Oct
28
 comment Google App Engine [app]s - We are all on the same quota!
AppID isn't trivially forged: We (App Engine) include the App ID in the user-agent header, and we don't let users set the user-agent header on outgoing requests. If the IP comes from our pool (_netblocks.google.com), you can trust that the App ID in the user-agent is accurate.
Jun
17
 awarded  Autobiographer
Jun
17
 comment How to get a User Id
First off, I don't see how exposing OpenIDs is a security issue. OpenIDs are intended to be public identifiers. More importantly, though, an API wouldn't need to expose the OpenID - just provide a way to get a user ID for an OpenID. This would be invaluable for integrating other OpenID-using sites with SO.