Kiosk mode #21
Comments
ghost
assigned 
|
Look at http://chat.efnet.org:9090/ |
Credits for name list: Data::Faker::Name, Jason Kohles
- /kiosk resource is always there - Add Convos::Core::Util::generate_login_name() - Replace CONVOS_KIOSK_MODE with CONVOS_KIOSK_SERVERS - Passing on exact values to add_user() and add_connection() - Use delete_user() the correct way - Remove temporary=>1. Need something more clever TODO: - Figure out a better way to logout an idle user
|
See also #89 |
|
My idea is to use JWT (JSON web tokens) with enough information for a user to register and automatically join a server/chat room. The payload of the JWT is a JSON structure with information, such as username, server and dialog/channel name. The signature is a checksum which the server can use to validate the payload. This means that unless the token was generated from a secure party, then Convos (or any JWT party) will reject the whole token. The last part about "kiosk mode" is that the actual user interface will be stripped down. Like not having any menus. I would do that part by another query parameter, like "?kiosk=1", or maybe even a list of elements to show, like "?kiosk=participants,heading". Using such a parameter will then make convos render nicely inside an iframe. |
Example: http://localhost:3000/?hide=header,menu,settings,sidebar This can also be set from config. Note that settings this will not prevent the user from showing the elements by fiddling with the settings. Additional backend code is required to prevent the user from doing illegal stuff.
|
Closing this in favour of #346. (Because of age) |
I would like to have a restricted version of Convos, which only lets you log in and join a channel, without settings or persistence. For running a demo mode and embedding in company pages.
The text was updated successfully, but these errors were encountered: