notes on possibilities

1 files changed, 14 insertions, 0 deletions

diff --git a/doc/design/assistant/cloud.mdwn b/doc/design/assistant/cloud.mdwn
index 0e1d0c851..653ebb460 100644
--- a/doc/design/assistant/cloud.mdwn
+++ b/doc/design/assistant/cloud.mdwn
@@ -28,6 +28,20 @@ been a change to Alice's git repo. Then he needs to pull from Alice's git repo,
 or some other repo in the cloud she pushed to. Once both steps are done,
 the assistant will transfer the file from the cloud to Bob.
 
+* dvcs-autosync uses jabber; all repos need to have the same jabber account
+  configured, and send self-messages. An alternative would be to have
+  different accounts that join a channel or message each other. Still needs
+  account configuration.
+* irc could be used. With a default irc network, and an agreed-upon channel,
+  no configuration should be needed. IRC might be harder to get through
+  some firewalls, and is prone to netsplits, etc. IRC networks have reasons
+  to be wary of bots using them. Only basic notifications could be done over
+  irc, as it has little security.
+* When there's a ssh server involved, code could be run on it to notify
+  logged-in clients. But this is not a general solution to this problem.
+* pubsubhubbub does not seem like an option; its hubs want to pull down
+  a feed over http.
+
 ## storing git repos in the cloud
 
 Of course, one option is to just use github etc to store the git repo.