about summary refs log tree commit diff
diff options
context:
space:
mode:
authorJune McEnroe <june@causal.agency>2019-10-26 22:55:08 -0400
committerJune McEnroe <june@causal.agency>2019-10-26 22:55:08 -0400
commit3edd75d21cf0dd7f93db74431dd73c23f6f9cc55 (patch)
tree80342c3dfde554ba32fc211af4ed7360c585d490
parentHandle nick collision (diff)
downloadpounce-3edd75d21cf0dd7f93db74431dd73c23f6f9cc55.tar.gz
pounce-3edd75d21cf0dd7f93db74431dd73c23f6f9cc55.zip
Document rationale
-rw-r--r--README.725
1 files changed, 24 insertions, 1 deletions
diff --git a/README.7 b/README.7
index 78bbb11..59220cc 100644
--- a/README.7
+++ b/README.7
@@ -1,4 +1,4 @@
-.Dd October 25, 2019
+.Dd October 26, 2019
 .Dt README 7
 .Os "Causal Agency"
 .
@@ -21,6 +21,29 @@ requires LibreSSL
 and targets
 .Fx .
 .
+.Sh RATIONALE
+As a former
+.Xr znc 1
+user,
+I was dissatisfied with the multi-client experience it offered.
+I wanted to connect from both my laptop and my phone
+and have full chat history on both.
+With
+.Xr znc 1 ,
+my options were either having both clients
+spammed with redundant history every time they connect,
+or having one client consume the buffer
+and the other get no history at all.
+.
+.Pp
+With a multiple-consumer ring buffer,
+each client has its own place in the history
+and can be brought up to date independently.
+Additionally,
+by expecting clients to implement the server-time extension,
+all events can be accurately replayed,
+rather than being limited to messages.
+.
 .Sh FILES
 .Bl -tag -width "rc.pounce" -compact
 .It Pa bounce.h