Add FAQ and Privacy Policy placeholders

.gitignore

@@ -32,6 +32,7 @@
 .pub-cache/
 .pub/
 /build/
+.pubspec.lock
 
 # Web related
 lib/generated_plugin_registrant.dart

FAQ.md

@@ -0,0 +1,7 @@
+# FAQ
+
+in progress
+
+## CONTACT
+
+in progress

PRIVACY-POLICY.md

@@ -0,0 +1,3 @@
+# PRIVACY POLICY
+
+in progress

README.md

@@ -1,4 +1,4 @@
-# Cross-platform Magic Wormhole graphical client
+# Destiny - Cross-platform Magic Wormhole graphical client
 
 ⚠ This project is still a work in progress, use at your own risk ⚠
 
@@ -11,9 +11,10 @@ with a Dart API. The plugin is implemented [here](https://github.com/LeastAuthor
 Supported platforms
 
 - [x] Linux
-- [x] Android
 - [x] Windows
 - [x] OSX
+- [x] Android
+- [ ] iOS
 
 ## Cloning
 
@@ -52,54 +53,6 @@ Builds for local instances:
 flutter build linux lib/main_local.dart
 ```
 
-## Signing Android AppBundle for Google Play upload
-Improtant! First time upload key is used for signing further builds. Key should be shared with other developers if more then one person is signing app
-
-Developer upload key is necessary for upload AppBundle to store. Find out [more](https://support.google.com/googleplay/android-developer/answer/9842756?hl=en#zippy=%2Cupload-key-requirements)
-1. Generate upload key with keytool (Note! store keystore.jks file outside project dir)
-```bash
-keytool -genkey -v -keystore ~/upload-keystore.jks -keyalg RSA -keysize 2048 -validity 10000 -alias upload-key
-```
-2. Create key.properties file and add your details (Note! key.properties should outside project dir and not be pushed to repo)
-```bash
-KEY_ALIAS=upload-key
-KEY_PASSWORD=<password>
-STORE_FILE=/Users/<my_user>/upload-keystore.jks
-STORE_PASSWORDP=<password>
-```
-3. Set key.properties path in gradle.properties file for parameter AndroidProject.signing=/your/path/key.properties
-4. Run build manually
-```bash
-flutter build appbundle --build-name=<build_version> --dart-define version=<build_version> --build-number=<build_number> -t lib/main_la.dart
-```
-Note: Google Play store requires unique or incremental build-number for every upload to store.
-
-## Usage with `wormhole-william`
-
-Send a file:
-
-```bash
-wormhole-william send <file_path>
-```
-
-Receive a file:
-
-```bash
-wormhole-william receive 33-leprosy-highchair
-```
-
-Transferring files with leastauthority.com
-
-```bash
-wormhole-william receive --relay-url="wss://mailbox.w.leastauthority.com/v1" --transit-helper="wss://relay.w.leastauthority.com:443" 33-leprosy-highchair
-```
-
-Transferring files with a local backend
-
-```bash
-wormhole-william receive --relay-url="ws://0.0.0.0:4000/v1" --transit-helper="tcp:0.0.0.0:4001" 33-leprosy-highchair
-```
-
 ### Starting the wormhole services locally
 
 ```bash

TERMS.md

@@ -0,0 +1,4 @@
+# TERMS & CONDITIONS
+
+in progress
+

doc/releases.md

@@ -1,5 +1,28 @@
 # Signing releases and verification
 
+## Android AppBundle for Google Play upload
+Improtant! First time upload key is used for signing further builds. Key should be shared with other developers if more then one person is signing app
+
+Developer upload key is necessary for upload AppBundle to store. Find out [more](https://support.google.com/googleplay/android-developer/answer/9842756?hl=en#zippy=%2Cupload-key-requirements)
+1. Generate upload key with keytool (Note! store keystore.jks file outside project dir)
+```bash
+keytool -genkey -v -keystore ~/upload-keystore.jks -keyalg RSA -keysize 2048 -validity 10000 -alias upload-key
+```
+2. Create key.properties file and add your details (Note! key.properties should outside project dir and not be pushed to repo)
+```bash
+KEY_ALIAS=upload-key
+KEY_PASSWORD=<password>
+STORE_FILE=/Users/<my_user>/upload-keystore.jks
+STORE_PASSWORDP=<password>
+```
+3. Set key.properties path in gradle.properties file for parameter AndroidProject.signing=/your/path/key.properties
+4. Run build manually
+```bash
+flutter build appbundle --build-name=<build_version> --dart-define version=<build_version> --build-number=<build_number> -t lib/main_la.dart
+```
+Note: Google Play store requires unique or incremental build-number for every upload to store.
+
+
 ## MacOS
 
 In order to build signed macos releases, a valid code signing certificate needs to be added to the key chain.