File: day_127__xmpp_syncs.mdwn

package info (click to toggle)
git-annex 7.20190129-3
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 56,292 kB
  • sloc: haskell: 59,105; sh: 1,255; makefile: 225; perl: 136; ansic: 44
file content (35 lines) | stat: -rw-r--r-- 1,349 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
I got full-on git-annex assistant syncing going over XMPP today!

How well does it work? Well, I'm at the cabin behind a dialup modem. I have
two repos that can only communicate over XMPP. One uses my own XMPP server,
and the other uses a Google Talk account. I make a file in one repo, and
switch windows to the other, and type `ls`, and the file (not its content
tho..) has often already shown up. So, it's about as fast as syncing over
ssh, although YMMV.

----

Refactored the git push over XMPP code rather severely. It's quite a
lot cleaner now.

----

Set XMPP presence priority to a negative value, which will hopefully
prevent git-annex clients that share a XMPP account with other clients from
intercepting chat messages. Had to change my XMPP protocol some to deal
with this.

----

Some webapp UI work. When showing the buddy list, indicate which buddies
are already paired with. 

After XMPP pairing, it now encourages setting up a shared cloud repository.

[[!img /assistant/xmpppairingend.png]]

I still need to do more with the UI after XMPP pairing, to help the paired
users configure a shared cloud transfer remote. Perhaps the thing to do is
for the ConfigMonitor to notice when a git push adds a new remote,
and pop up an alert suggesting the user enable it. Then one user
can create the repository, and the other one enable it.