Updated Hackathon Feedback (markdown)
parent
9488b1681f
commit
b251ec3884
|
@ -1,25 +1,69 @@
|
|||
## Bots
|
||||
|
||||
* Access contact list of user you are friends with
|
||||
* Allow to add a contact
|
||||
* Allow whisper to automatically send messages on events
|
||||
* Add more RN bindings
|
||||
* Allow bots to send messages anytime
|
||||
* Add new APIs (XHR, promise)
|
||||
* Clarifiy `status.command` and `status.response` (and generally semantics)
|
||||
* Improve response format
|
||||
* Allow to generate QRcodes
|
||||
* Add custom components in `sendMessage` / more formatting
|
||||
* Add Token like button support
|
||||
* Allow to send and receive images
|
||||
* Add event loop support (e.g. react on chain callback)
|
||||
* Allow to remove global commands
|
||||
* Allow bots to participate in human-to-human/group chat
|
||||
* Support multiple clickable (actionable) inline pills in bot messages
|
||||
* Fix various bugs with global commands (incorrect formating receiver side, command name not displayed)
|
||||
* Allow to set bot status
|
||||
* Improve docs of available features
|
||||
* Improve APIs consistency
|
||||
> * Access contact list of user you are friends with
|
||||
|
||||
What information about users should be included?
|
||||
|
||||
Implementation options:
|
||||
1. Passing the whole list in `context` parameter can be enough (but not the best option)
|
||||
2. We could set that list using some method on `status-go` side, then define js function in otto vm which returns this list (better one)
|
||||
|
||||
> * Allow to add a contact
|
||||
|
||||
What exactly this means?
|
||||
|
||||
> * Allow whisper to automatically send messages on events
|
||||
|
||||
This will be possible when event loop will be added on `status-go` side.
|
||||
|
||||
> * Add more RN bindings
|
||||
|
||||
Is this about markup?
|
||||
|
||||
> * Allow bots to send messages anytime
|
||||
> * Add new APIs (XHR, promise)
|
||||
|
||||
Both depend on event loop
|
||||
|
||||
> * Clarifiy `status.command` and `status.response` (and generally semantics)
|
||||
|
||||
We need to add more info in docs
|
||||
|
||||
> * Improve response format
|
||||
|
||||
What exactly does this mean?
|
||||
|
||||
> * Allow to generate QRcodes
|
||||
|
||||
Allow to generate QR's and show them in messages?
|
||||
|
||||
> * Add custom components in `sendMessage` / more formatting
|
||||
What exactly custom components?
|
||||
|
||||
> * Add Token like button support
|
||||
|
||||
> * Allow to send and receive images
|
||||
|
||||
depends on swarm atm
|
||||
|
||||
> * Add event loop support (e.g. react on chain callback)
|
||||
> * Allow to remove global commands
|
||||
|
||||
We may want to discuss and add permissions management for commands/bots
|
||||
|
||||
> * Allow bots to participate in human-to-human/group chat
|
||||
> * Support multiple clickable (actionable) inline pills in bot messages
|
||||
|
||||
Are there any use cases?
|
||||
|
||||
> * Fix various bugs with global commands (incorrect formating receiver side, command name not displayed)
|
||||
|
||||
> * Allow to set bot status
|
||||
|
||||
^ that's easy to implement, we just need to add another method like https://github.com/status-im/status-go/blob/bug/whisper-on-geth1.6.1/geth/jail/handlers.go#L117 and handle signal
|
||||
|
||||
> * Improve docs of available features
|
||||
> * Improve APIs consistency
|
||||
|
||||
## DApp
|
||||
|
||||
|
@ -27,10 +71,16 @@
|
|||
|
||||
## Both
|
||||
|
||||
* Allow bots and DApps to communicate (share localStorage?)
|
||||
* Deeper DApp / bot interactions
|
||||
* Access device APIs (camera, GPS, ...)
|
||||
* Improve debugging story - reload, logs, Chrome Devtools (DApp, Bots). Allow webview debugging with release builds.
|
||||
> * Allow bots and DApps to communicate (share localStorage?)
|
||||
|
||||
Sharing of localStorage is not crystal clear thing, we will need to allow access to bot's localStorage only when exactly dapp's url is opened in `@browse` command. Also it's not clear how this will work in group chats.
|
||||
|
||||
> * Deeper DApp / bot interactions
|
||||
|
||||
^ are there use cases?
|
||||
|
||||
> * Access device APIs (camera, GPS, ...)
|
||||
> * Improve debugging story - reload, logs, Chrome Devtools (DApp, Bots). Allow webview debugging with release builds.
|
||||
|
||||
## General
|
||||
|
||||
|
|
Loading…
Reference in New Issue