Optional ability to specify WebSocket/REST URL as argument (Accessibility / Guest Keyboards)

[mdrejhon]

Mimiuchi now supports 3 modes (line-input keyboard, real-time keyboard, and voice dictation) and has both a WebSocket/REST server. This makes mimiuchi a perfect accessibility guest-keyboard client.

Example

accessibility-keyboard-site.com/?keyboard=realtime&hook=ws://192.168.0.213:7714

Use Case: Guest Keyboards by Scanning QR Code

1. Custom central chatting app with a QR code (television, conference room, laptop at end of table, etc)
2. People visiting can scan the QR code on screen.
3. It loads mimiuchi with the connection hook preconfigured (temporary config? permanent config?)

Some people can type on their phones, and some people can dictate into their phones, and all their text will show up on a central IRC-style or texting-style or splitscreen-style central display.

Personal Accessibility Use Case

I'm a deaf software developer, and I often use central chatting screens (with a Bluetooth keyboard), but it would be nice if all my friends/coworkers phones doubled as guest keyboards instead, and they could all chat at the same time to my screen.

Security Considerations

Perhaps for intranet use only (e.g. only when running mimiuchi in intranet). We have to think carefully about security implications to find ways to be maximally secure when letting a random URL specify a random REST/WebSocket URL.
Possible security solutions:

• Only allow when running mimiuchi on intranets, not for public mimiuchi
• And/Or display permission prompt dialog ("WARNING: Guest Communicator Mode activated. Your dictation and typing will be transmitted to [URL]. Do you trust this transmission? [YES] [NO]")
• Or alternate security solution