status-im
/
status-cli-client
mirror of
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
Simple CLI utility for sending Status messages.
25 Commits 2 Branches 0 Tags 111 KiB
Go 98.3%
Makefile 1.7%
Go to file
Jakub Sokołowski 0c0637b4b1
add support for ENS name 
Signed-off-by: Jakub Sokołowski <jakub@status.im>
 		2020-02-20 15:54:41 +01:00
.gitignore ignore generated binary 2019-08-30 11:37:52 -04:00
LICENSE.md add Mozilla license 2019-08-28 11:33:05 -04:00
Makefile fix output name for Makefile target 2019-08-30 13:29:03 -04:00
README.md add support for ENS name 2020-02-20 15:54:41 +01:00
go.mod upgrade to v1 messages, use status-go v0.45.1 2020-02-20 15:04:03 +01:00
go.sum upgrade to v1 messages, use status-go v0.45.1 2020-02-20 15:04:03 +01:00
main.go add support for ENS name 2020-02-20 15:54:41 +01:00

README.md

Description

This is a dead-simple CLI client for sending Status messages.

It uses the status-go library and is essentially a very basic example of its usage.

Usage

 $ ./status-cli-client -help
Usage of ./status-cli-client:
  -addr string
    	Listening address for Whisper node thread. (default "0.0.0.0")
  -chat string
    	Name of public chat to send to. (default "whatever")
  -data string
    	Location for Status data. (default "/tmp/status-cli-client")
  -ens string
    	ENS name to send with the message.
  -key string
    	Hex private key for your Status identity.
  -message string
    	Message to send to the public channel. (default "TEST")
  -port int
    	Listening port for Whisper node thread. (default 30303)
  -timeout int
    	Timeout for message delivery in milliseconds. (default 500)

Example usage would be:

 $ ./status-cli-client -chat test-channel -message "Pretty cool!"

Known Issues

  • We're using time.Sleep() to let Whisper deliver the message, which is stupid
  • We're using an in-memory instance of SQLite that holds things like whisper keys