Make it possible to retrieve user's public.json via their /on/elsewhere URLs

[joonas]

So basically to make it easier for @clone1018 to pull the correct data, we should also serve the public.json from /on/elsewhere URLs, because a user might not use the same username on every site.

For example, my username on twitter is prometheus, and thus the gittip-everywhere widget is unable to find my gittip public.json, because it's trying to pull it from https://www.gittip.com/prometheus/public.json rather than https://www.gittip.com/joonas/public.json.

Thus, I propose that we either:

1. make public.json available under /on/elsewhere URLs (/on/twitter/prometheus/public.json)
2. or have /on/elsewhere public.json requests redirect to the appropriate gittip.com profile public.json.

I would think that option 1 makes it easier for the javascript, but option 2 would be the canonical way to do this since it avoids duplication.

Thoughts? Takers?

/cc @clone1018 @whit537

[sigmavirus24]

I'm for #2 personally.

[rummik]

The second option seems like it should work fine

[rummik]

Can we get a little love for this? Gittip Everywhere is trying to pull things from http://www.gittip.com/iotasamurai on my Twitter account :P

[zbynekwinkler]

Shall this also depend on #505?

[rummik]

I don't really see why it should. It would be nice to have it done by magic in #505, but since much of the work is already done (ex: /on/twitter/iotasamurai/ → /rummik/), it doesn't necessarily have to depend on it.

[seanlinsley]

This has been added by #2129