We successfully are now able to write and read a profile json with an image, name and city to our private wn.fs app path. What is your current best intended strategy to make the profile data shareable, updateable and revokable so it propagates across all users, which have access or no access anymore to the profile resource.
We currently would like to give the user 3 options on their profile data:
- Keep the profile data completely private and only accessible to your own devices (in this case propagate the outside world an anonymous avatar and name, like in the screen below)
- Share the profile data with only the people you trust and know (with the option to revoke this access)
- Make the profile data completely public and pin it to the omo organisation service for public lookup
The goal for the first iteration, would be to create profile resolvers on this screen, according to the upper 3 options: