From 0a834599c4ee8c1e86a03c894ba18f45115c3b86 Mon Sep 17 00:00:00 2001 From: Zack Date: Sat, 21 Oct 2017 14:55:49 -0600 Subject: [PATCH 1/3] Update README.md --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 66a5dbcd..db305f91 100644 --- a/README.md +++ b/README.md @@ -18,6 +18,10 @@ This is more or less (but mostly *less*) a Golang port of [@warner's](https://gi # Example +![send](https://user-images.githubusercontent.com/6550035/31855780-35140b88-b66f-11e7-86cb-c23e2cb4fa86.gif) +![receive](https://user-images.githubusercontent.com/6550035/31855781-3632b384-b66f-11e7-8b29-9ba61ec374d4.gif) + + **Sender:** ``` From 8ecd2c30b891f8490fc36877f71a8cad83b77dcc Mon Sep 17 00:00:00 2001 From: Zack Date: Sat, 21 Oct 2017 14:58:57 -0600 Subject: [PATCH 2/3] Update README.md --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index db305f91..114d354f 100644 --- a/README.md +++ b/README.md @@ -18,6 +18,8 @@ This is more or less (but mostly *less*) a Golang port of [@warner's](https://gi # Example +_These two gifs should run in sync if you force-reload (Ctl+F5)_ + ![send](https://user-images.githubusercontent.com/6550035/31855780-35140b88-b66f-11e7-86cb-c23e2cb4fa86.gif) ![receive](https://user-images.githubusercontent.com/6550035/31855781-3632b384-b66f-11e7-8b29-9ba61ec374d4.gif) From 54a5a8896dd7634f1cb9288d387bd5609e91caff Mon Sep 17 00:00:00 2001 From: Zack Date: Sat, 21 Oct 2017 15:22:32 -0600 Subject: [PATCH 3/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 114d354f..bbf67a34 100644 --- a/README.md +++ b/README.md @@ -67,7 +67,7 @@ Or, if you are like my good friend Jessie and "*just can't even*" with programmi ## Run your own relay -*croc* relies on a TCP relay to staple the parallel incoming and outgoing connections. The relay temporarily stores connection information and the encrypted meta information. The default uses my server, `cowyo.com`, which has no guarantees except that I guarantee to turn if off as soon as it gets abused. +*croc* relies on a TCP relay to staple the parallel incoming and outgoing connections. The relay temporarily stores connection information and the encrypted meta information. The default uses a public relay at, `cowyo.com`, which has no guarantees except that I guarantee to turn if off as soon as it gets abused ([click here to check the current status of the public relay](https://stats.uptimerobot.com/lOwJYIgRm)). I recommend you run your own relay, it is very easy. On your server, `your-server.com`, just run