Password protect a presentation for remote control #67
Comments
|
Note: as the content of the presentation are going to be synced between deck and remote (see #450), this synchronization should only happens if the password is validated, no before ;) |
Signed-off-by: peterpeterparker <david.dalbusco@outlook.com>
Signed-off-by: peterpeterparker <david.dalbusco@outlook.com>
Signed-off-by: peterpeterparker <david.dalbusco@outlook.com>
Signed-off-by: peterpeterparker <david.dalbusco@outlook.com>
Signed-off-by: peterpeterparker <david.dalbusco@outlook.com>
…tion from the remote Signed-off-by: peterpeterparker <david.dalbusco@outlook.com>
Signed-off-by: peterpeterparker <david.dalbusco@outlook.com>
Signed-off-by: peterpeterparker <david.dalbusco@outlook.com>
Signed-off-by: peterpeterparker <david.dalbusco@outlook.com>
feat(#67): grant remote control access to presentations
|
Done. We are not going to use "password protected" presentation but the decks and their content is only going to be send to the remote if the presenter grand the request and access. Each remote will receive a random number. On each connection request, a popup will be displayed on the presentation with a text like "Can remote 11 22 33 access your presentation?" and then, it will be up to the presenter to accept or not. Again, until presenter accept the requests, no content beside the deck's title is transmitted. Moreover, as it was already the case, presenter can completely turn off the "remote control" and therefore even no titles are transmitted. I hope that's cool so. I personally find this way user friendlier as having to type code. Moreover I also think it is safer than having to save a password somewhere. |
Maybe it would be cool to be able to set a password to access a presentation thru the remote control
As every presentation are listed by the signaling server, maybe it would be cool to just add a small password (like four digits) to be a bit more sure to be the only one to be able to get access thru the remote control to his/her presentation
The text was updated successfully, but these errors were encountered: