When did you authorized on the new tracker?

The thing is that if you:

1. register on GitHub without a (Gr)avatar)
2. register an jissues
3. change your (Gr)avatar

those changes would not be reflected on jissues, as the user data (and avatar) gets stored on the first log in.

Could that be the case ?

I think we can either run a cron and sync all users periodically, or create a Refresh button in the profile so every user can refresh her data from GitHub manually when she feels appropriate.
I'd prefer the latter

Hello,

After I linked my Github account with Jissues, I had no picture. This was added later on, so you are right with point 3, that I changed the picture afterwards.

A Refresh button in the profile is good enough for me. It is not something I will be doing all the time ;)

I think cron job is great for user experience, since I hate to click
buttons everyday ;( But that's only my personal thoughts

顺颂时祺 | Best Wishes

赵泽涵 | Allen Zhao

中国·对外经济贸易大学 / 信息学院2011级 / 电子商务(国际商务方向)
E-Business and International Business | School of Information Technology
and Management Engineering | Class of 2015
University of International Business and Economics, Beijing, P.R.China

Tel:+86 18810467408
E-mail: i@allenzhao.com / 201136040@uibe.edu.cn / cnallenzhao@gmail.com
地址：中国·北京市朝阳区惠新东街10号对外经济贸易大学汇智公寓457室
Address:Room 457, Huizhi Buliding, University of International Business

and Economics, No,10 Huixin East Street, Beijing, P.R.China

This message is a private communication. The information contained in this
message or attached to this communication may be protected from disclosure
and may contain information that is legally privileged, proprietary, and/or
confidential. If you are not the intended recipient, please do not read,
copy, use, or disclose it to others. Please notify the sender of the
delivery error by replying to this message, and then delete it and any

attachments from your system. Thank you.

2014-04-23 9:42 GMT+08:00 Nikolai Plath notifications@github.com:

The thing is that if you:

1. register on GitHub without a (Gr)avatar)
2. register an jissues
3. change your (Gr)avatar

those changes would not be reflected on jissues, as the user data (and
avatar) gets stored on the first log in.

Could that be the case ?

I think we can either run a cron and sync all users periodically, or
create a Refresh button in the profile so every user can refresh her data
from GitHub manually when she feels appropriate.
I'd prefer the latter [image: ]

—
Reply to this email directly or view it on GitHub#339 (comment)
.

The refresh button is not the ideal solution, but you don't change gravatar so often, don't you? :)

The problem with the cron job is, users will not see their image change immediately. So they wonder if something is broken. At least with a refresh button, they have something to click. Best would be if there is a trigger like onAvatarUpdate or something :)

If we chose cron job, we should add a tip or warning somewhere to make sure users don't regard this as a bug.

And I'm wondering can we do both? I mean can we add the refresh button and the cron job at the same time so if a user updates his/her avatar he/she could refresh it and the cron job makes sure that avatar will be refreshed anyway without users' clicking on the button.

Cheers,
Allen Zhao

ÔÚ 2014Äê4ÔÂ23ÈÕ£¬23:15£¬RolandD notifications@github.com дµÀ£º

The problem with the cron job is, users will not see their image change immediately. So they wonder if something is broken. At least with a refresh button, they have something to click. Best would be if there is a trigger like onAvatarUpdate or something :)

¡ª
Reply to this email directly or view it on GitHub.

Another problem with a cron job would be that we have a rate limit on GitHub and these operations do count ;)

Beside the avatar you can also change your "display name" and your (public) e-mail address, both are shown on jissues.

@allenzhaocn I think doing both the cron job and the refresh button would be the best "compromise". Running the cron weekly, or even monthly, shouldn't hurt the rate limit that much (hopefully)

We should setup cron job weekly and see will we hit the limit or not.

There is no trigger we can hook into? If not, both the refresh button and cron sound good to me.

Nope there is no trigger.