-
Notifications
You must be signed in to change notification settings - Fork 622
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Web server for multi-user sticker picker #7
Comments
As an alternative to including a webserver the potential bot could also provision all required static files into some subdir scheme like:
|
I copied
|
msrd0/docker-stickerpicker does also support multiple profiles |
I would suggest adding an "Edit Visibility" button to the settings section so users can decide wich packs are visible to them. When the button is pressed, the window goes into an "edit mode" where packs can be enabled or disabled with a switch, just like in Dimension. The state could also be saved in the local storage like the other settings. Here I made a small visual concept of how this idea could look in the UI: stickerpicker_edit_visibility_concept.mp4 |
Is it possible to add the sticker picker for all users or do they all have to add it to their |
I'm using https://heptapod.host/intevation/fac/synapse-modules#static-account-data for this purpose |
Does that automatically update existing user data, or is it necessary to have them change something about their profile before that's applied? Thanks. |
No, it's not applied to all existing users. You need to do that by other means (I'm sure I did that my self, but don't remember the details) |
Understood. Thanks for the help. If you do happen to remember what you did, please let me know. |
A cursory glance in the |
Currently the picker is just some static files, which means everyone has the same packs and they can only be configured server-side.
The project could include a simple web server which can serve different packs for different users, based on some identifier in the picker URL. Once that server exists, it could also have a bot or other interface that users can use to add packs to their own picker.
It shouldn't have any auth other than the unique ID in the URL, as widget authentication is a mess that's different on all platforms.
The text was updated successfully, but these errors were encountered: