You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We need to have a way to create our own user info abut a user, without forcing us to have our own token server as well. This is so the appbuilder front end can use our data to provide relationships between hosts, and between hosts and audience, and between audience members.
Describe the solution you'd like
We'd like a way to create our own User data that is made available within a conference; or to get read/write access to the user.go data; or create our own UID string, without having to create our own token server. Using the Agora generated UID increases our Daily Active Users when a user attends multiple events.
Describe alternatives you've considered
We have created our own User data structure in our appbuilder, and sent it around via RTM to all the conference hosts and audience. It is costly, and creates a lot of traffic.
Additional context
The text was updated successfully, but these errors were encountered:
Hey. If I understand correctly, you want the ability to create a per-user state on the backend, is that right? If I understand correctly, you should be able to just add a state string to the UserAccount struct to solve the issue. And you would need a query and mutation to get and set this state respectively for each user.
Is your feature request related to a problem? Please describe.
We need to have a way to create our own user info abut a user, without forcing us to have our own token server as well. This is so the appbuilder front end can use our data to provide relationships between hosts, and between hosts and audience, and between audience members.
Describe the solution you'd like
We'd like a way to create our own User data that is made available within a conference; or to get read/write access to the user.go data; or create our own UID string, without having to create our own token server. Using the Agora generated UID increases our Daily Active Users when a user attends multiple events.
Describe alternatives you've considered
We have created our own User data structure in our appbuilder, and sent it around via RTM to all the conference hosts and audience. It is costly, and creates a lot of traffic.
Additional context
The text was updated successfully, but these errors were encountered: