0.3.0.alpha10

first alpha release of the completely rewritten remoteAudio application. Here the main new features:

• Transport has changed from MQTT to NATS (you need the gnatsd broker)
• Support for multiple audio servers
• Audio servers are detected automatically
• Server can start streaming on startup (via pflag)
• As an alternative to the WebUI a REST API has been incorporated into the client

breaking changes:

• no more MQTT (until v5 is supported)
• several pflags have changed. Please delete the config file and use the pflags until the final version has been released. Some of the pflags might again change until then.

how to use remoteRotator:

# start audioserver (with a public broker temporarily installed on a VPS)
$ ./remoteAudio server nats -u=195.201.117.206 -Y=ts480

# start client
$ ./remoteAudio client nats -u=195.201.117.206

**examples of the REST API:**

```bash
# get & set rx volume
$ curl localhost:9090/api/rx/volume
$ curl  -X PUT -d "{\"volume\":100}" "localhost:9090/rx/volume"

# get & set volume
$ curl localhost:9090/api/tx/volume
$ curl  -X PUT -d "{\"volume\":100}" "localhost:9090/tx/volume"

# get & set ptt
$ curl localhost:9090/api/tx/state
$ curl -X PUT -d "{\"on\":true}" "localhost:9090/tx/state"

# get list of available audio servers
$ curl localhost:9090/api/servers

# get details of audioserver "ts480"
$ curl localhost:9090/api/server/ts480

# start the audio stream from the ts480
$ curl -X PUT -d "{\"on\":true}" "localhost:9090/api/server/ts480/state"

# if you have several audio servers (e.g. ts480 and ft1000mp) you can select for example the ft1000mp
curl -X PUT -d "{\"active\":true}" "localhost:9090/api/server/ft1000mp/active