Hi mvo! I made the first few changes per your recommendations and retested.
Regarding your comment:
> - could we simply assume that if there is a uuid generated, that
> means that the user requested a opt-in? or is the seperate
> recommender_opt_in_requested config needed (e.g. to make things
> simpler)? like just generate the uuid on opt-in?
The uuid is used to indicate a successful opt-in, so as such it is not set until the profile upload and initial recommendations download is complete. The recommender_opt_in_requested is specifically for the case where opt-in is requested but network connectivity is not available, so it is there only to track the case where an opt-in is pending. This is reset once the opt-in is successfully completed and the uuid generated.
The last couple of recommendations that you made are a bit more involved, so I will hold off on those for another branch.
Hi mvo! I made the first few changes per your recommendations and retested.
Regarding your comment:
> - could we simply assume that if there is a uuid generated, that opt_in_ requested config needed (e.g. to make things
> means that the user requested a opt-in? or is the seperate
> recommender_
> simpler)? like just generate the uuid on opt-in?
The uuid is used to indicate a successful opt-in, so as such it is not set until the profile upload and initial recommendations download is complete. The recommender_ opt_in_ requested is specifically for the case where opt-in is requested but network connectivity is not available, so it is there only to track the case where an opt-in is pending. This is reset once the opt-in is successfully completed and the uuid generated.
The last couple of recommendations that you made are a bit more involved, so I will hold off on those for another branch.
Thanks as always for your detailed review!