I assume the Strava Webhooks will not notify us for those activities, but we should do some investigating to see what that might look like in the long run.
If a user does not opt in initially, how would they be able to provide us access after the fact?
Should we surface a message after OAuth if they do not allow Private Activities? How would we know?
Is there any other access that we want/need to request for full implementations? What are the repercussions of not having those access levels?
This implementation would require us to take the Titles, Artists and maybe Played At attributes from each UserSong for an Activity, and process it into a text block.
It appears the http://developers.strava.com/docs/reference/#api-Activities-updateActivityById endpoint allows us to add descriptions. http://developers.strava.com/docs/reference/#api-models-UpdatableActivity describes the aspect of the Activity we can change.
We should implement User management to allow Users to edit their names. Even though the User is created through our Strava OAuth process, we should still provide the functionality.
This applies to those who have changed their name for any reason, as it will not update automatically from Strava to our app.