periodically update user_info in elsewhere

[chadwhitacre]

We should be constantly updating the user_info we have for all the social networks. @emTr0 updated his avatar at Bitbucket and we didn't pick up the change.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[chadwhitacre]

https://twitter.com/emTr0/status/329397765698375680

[wyze]

+1 from kamal_ on IRC

[seanlinsley]

How often, though? Nightly? Are there web hooks we can listen for?

[zbynekwinkler]

This would also fix #1395. The apis for the updates are described there (github, twitter).

[zbynekwinkler]

Fixing this issue would also move us in the right direction to detect which accounts are in fact orphaned (#1807).

[zbynekwinkler]

I am adding this to my queue.

[Changaco]

@zwn It might be better if you wait (a few days at most) for me to update the elsewhere branch and start your work from there instead of master.

[zbynekwinkler]

@Changaco I'll do mostly weekends.

[chadwhitacre]

Looking at this with @BastianBerndsen, he's tracking down his username). My first thought on this is that we should make sure we use a different OAuth application for this than we use for logins, to make sure that rate limits for this worker don't adversely affect the rest of the site (especially logging in).

[zbynekwinkler]

Undocumented Github API to resolve user_id is https://api.github.com/user/:numeric_id. Github support staff considers it stable enough for use.

[zbynekwinkler]

This is waiting for #1369.

[chadwhitacre]

Closing in light of our decision to shut down Gratipay.

Thank you all for a great run, and I'm sorry it didn't work out! 😞 💃