Change JID Command
If the backend sends us a command we recognize as a JID change, we
intercept it and replace it with ours.
Ours asks which JID we want to move to and then asks that JID if it
wants to do this. When they register we ask them to confirm they want to
swap, and then send the backend the actual JID change operation.
-O2 takes too much RAM for CI
Merge branch 'guix-no-tc'
* guix-no-tc:
Guixify
No more TC
Don't need to rewrite anymore
Merge branch 'cache-inbound-oob'
* cache-inbound-oob:
Intrument cacheOOB
Fetch any OOB URL from route and cache in jingle store
Set up structure to cache OOB coming from a direct message route
Fetch any OOB URL from route and cache in jingle store
Now we actually cache the data. Always assumes URLs are HTTP, but they always
are in practise and if one is not it will simply fail and in case of any error
we just pass the oob element through unmodified.
Update to work on latest Debian stable