diff options
author | 2012-10-28 16:53:38 -0400 | |
---|---|---|
committer | 2012-10-28 16:53:38 -0400 | |
commit | 1a35e32c0702a554554d4d456b472db0286572bd (patch) | |
tree | 22d1a8b4a241cb2d773bdbe0cfee6fa9b13dee75 /doc/design/assistant/xmpp.mdwn | |
parent | c8cd4ec3082ac7dd24c0377d66c95cb05b51f0ba (diff) |
blog for the day
Diffstat (limited to 'doc/design/assistant/xmpp.mdwn')
-rw-r--r-- | doc/design/assistant/xmpp.mdwn | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/doc/design/assistant/xmpp.mdwn b/doc/design/assistant/xmpp.mdwn index 0241f09c0..291007f46 100644 --- a/doc/design/assistant/xmpp.mdwn +++ b/doc/design/assistant/xmpp.mdwn @@ -4,16 +4,8 @@ who share a repository, that is stored in the [[cloud]]. ### TODO -* Nudge user to enable XMPP account at appropriate times, ie, after configuring - cloud remotes. * Prevent idle disconnection. Probably means sending or receiving pings, but would prefer to avoid eg pinging every 60 seconds as some clients do. -* After pulling from a remote, may need to scan for transfers, which - could involve other remotes (ie, S3). Since the remote client is not able to - talk to us directly, it won't be able to upload any new files to us. - Need a fast way to find new files, and get them transferring. The expensive - transfer scan may be needed to get fully in sync, but is too expensive to - run every time this happens. Send transfer notifications using XMPP? * XMPP pairing ## design goals |