When I first signed up with CityStrides and linked Strava, it imported my Strava avatar. But then I connected my MMR account, which didn’t have an av, and now I don’t have an av on CityStrides I put an avatar on MMR, but it doesn’t appear. I also don’t see a way to manually change the avatar on either Settings or Profile.
And I want my smiling face up here since I 100%-ed Brookline this morning!
Oh yeah that whole area of the code is Weird
I think there’s a job that updates avatars from whatever the first connected service is, once a month. I also think I disabled this for Strava because it’s another API call.
I don’t like the avatar setup, it was just the least effort when I first started the site … also since some of the avatars are sourced from Facebook, they can be perceived by some plugins as spy pixels (probably rightly so).
It’s a thing I want to improve but there’s all this waves hands
other stuff to do as well
Whenever you get around to it will be appreciated, it’s certainly lower priority than all the other great improvements you’re doing. Maybe my avatar will be updated randomly since I now have an avatar on each of my linked trackers.
The job to update photos is enabled, but it takes a full month to get through everyone.
I looked into your account, and it’s using the image set in MapMyFitness because it just looks to your first connected service & grabs the photo from there. It’s possible that CityStrides has lost its connection to MapMyFitness (their tokens expire & there was a bug a little while ago where CityStrides didn’t refresh them - so some people have to log out of CityStrides & log back in via MapMyFitness to reset that … no data loss, just a pain).
Overall, the current system of handling profile pictures is not that great because:
Garmin doesn’t provide any images, so no Garmin-connected account can have a profile picture
Some profile pictures are stored in Facebook, so that image loading provides them an amount of tracking access that I don’t want
I think I need to overhaul this, to allow image uploading. It’s just not that high in my list right now.
I know I connected Strava first, but back in March/April before Garmin syncing I did some ill-advised disconnect/reconnects and when I linked MMR/MMF it blank’d my avatar and it has never come back despite having Strava reconnected. I don’t think I had an avatar on MMR/MMF when I connected, but I since added one.
Just adding this context in case it reveals what’s wrong since it’s been about 9 weeks since I first posted this, totally understand it’s low priority and not that big a deal to be a gray placeholder as long as my LifeMap is vibrant and sprawling.
Your disconnect/reconnect changed things around which pushed the MMR account to ‘first’ so now that’s the service CityStrides checks for the image. If you log out of CityStrides & log in via MMR, that’ll reset the connection. After you do that, you can log out of CityStrides and log back in with whichever service you prefer. Let me know after you do that, and I can force your account to update.
Mine is gone too on the CityStrides pages, but oddly is still here for the forum. I recall a post about saving the (Strava) API call for activities, not pictures, but can’t find that post, so picked this thread instead. Can’t one section of CS pull from the other?
Any changes to the avatar situation? I have an avatar in all three of my connected services, but I am currently only syncing with Garmin (I know you can’t get my avatar from there)
I am still perplexed as to why it isn’t pulling from Strava any more, though - did you re-enable that once the API limit increased or is it still disabled? Or is Garmin my primary now and therefore I won’t get an avatar under the current system?
Right now, it pulls from your first connected service. It seems like the only blocker for your account would’ve been the Strava API limits. It only updates photos monthly, so if it happened to get blocked while checking it wouldn’t come around again for another month. I just manually walked through the code to see if it would work & it got caught by the 15min API limit, but worked when I ignored that.
It’s trash, for sure, and I’ll either fix it after the global update is sorted or the global update stresses me out so much that I need to do anything other than that for a bit … and the latter is looking more likely.