[Discussion] Tricky use case - public user profiles #1252
Replies: 1 comment 4 replies
-
The reason we don't allow access to the users list from the client-side is related to endless privacy and security concerns that might popup with such implementation. I think implementing a I see 3 main options here to allow this use-case:
For me both the 1st and 2nd options makes most sense, and seems like the |
Beta Was this translation helpful? Give feedback.
-
Problem
It doesn't seem like there is a good way to get a list of users client side.
There is no way to do it with client side account API. At first I thought I could just use the server-side API with only
users:read
permissions.However there is a major issue with this. All the users data is exposed this way. Things like emails, and preferences I don't necessarily want to be exposed.
And so if I want to store public user profiles, I would need to store them in the database? I would probably setup functions to listen to the account events to keep it updated.
Question
Is the solution outlined above for public user profiles acceptable and good enough, or should we explore or push for features that make this problem easier for the developer?
My thoughts
Some feature ideas I came up with for making this easier for the developer:
publicData
that is accessible from the client?userId
.I'm interested to hear @appwrite/core opinion as well as other Appwrite users/devs.
Beta Was this translation helpful? Give feedback.
All reactions