Standards-based instant messaging

[SteveRiley]

That fixed it.

[vinnywright]

That fixed it.

yup
VINNY

[Feathers McGraw]

We've been having fun with file transfers (Steve can send me files, but I can't send them back...)

News just in: I'm pretty sure this is telepathy's fault, not prosody. Using a different client (conversations on Android) I can send files both ways... but I still can't send files to a user on telepathy (I see conversations connect to the proxy in the prosody log, but then the transfer fails).

I need to do some more testing to work out what telepathy tries to do when it sends files, but I'm pretty sure it's not using the proxy provided by prosody. That file Steve managed to send me might have been sent via some other method (Jingle?)

[vinnywright]

News just in: I'm pretty sure this is telepathy's fault, not prosody. Using a different client (conversations on Android) I can send files both ways... but I still can't send files to a user on telepathy (I see conversations connect to the proxy in the prosody log, but then the transfer fails).

I need to do some more testing to work out what telepathy tries to do when it sends files, but I'm pretty sure it's not using the proxy provided by prosody. That file Steve managed to send me might have been sent via some other method (Jingle?)

I allso am using telepathy,,,,,,,you can hit me up if you want to try sending files back and forth ,,,,,,,I have been wandering if this had been fixed in telepathy yet .

last time I was trying this I had to resort to installing Kopete ,,,,,,it worked.

VINNY

[Feathers McGraw]

I allso am using telepathy,,,,,,,you can hit me up if you want to try sending files back and forth ,,,,,,,I have been wandering if this had been fixed in telepathy yet .

last time I was trying this I had to resort to installing Kopete ,,,,,,it worked.

VINNY

Another person to test with could be really useful! And it would be nice to chat too. I just added you (and later, installed that compatibility module steve was talking about). Let me know if you have trouble connecting!

I can't work out whether KDE Telepathy always connects to telepathy.im proxies (is it hard coded somehow?) or if it is trying to use a different method of file transfer (we're trying to send files as a SOCKS5 bytestream, but there's also the jingle protocol).

I might try Kopete but that would be like admitting defeat...

[SteveRiley]

Feathers, the file transfer from me to you did use the SOCKS proxy. Here's the log:

Mar 16 14:07:08 socket  debug   server.lua: accepted new client connection from 195.166.151.235:50249 to 5000
Mar 16 14:07:08 mod_proxy65     debug   SOCKS5 greeting complete
Mar 16 14:07:09 mod_proxy65     debug   SOCKS5 target connected for session 719345253ad8a201cbc24770ef5a2351d12a5e3d
Mar 16 14:07:09 s2sin175f9e0    debug   Received[s2sin]: <iq id='262458303404' type='result' to='steve@rileyz.net/kde-telepathy-489522' from='sam@samhobbs.co.uk/kde-telepathy-838227'>
Mar 16 14:07:09 socket  debug   server.lua: accepted new client connection from 192.168.0.212:33702 to 5000
Mar 16 14:07:09 mod_proxy65     debug   SOCKS5 greeting complete
Mar 16 14:07:09 mod_proxy65     debug   SOCKS5 initiator connected for session 719345253ad8a201cbc24770ef5a2351d12a5e3d
Mar 16 14:07:09 c2s18a3de0      debug   Received[c2s]: <iq id='197972230719' type='set' to='proxy.rileyz.net'>
Mar 16 14:07:09 proxy.rileyz.netroxy65        debug   Transfer activated (sid: 1426540001-1101837646, initiator: steve@rileyz.net/kde-telepathy-489522, target: sam@samhobbs.co.uk/kde-telepathy-838227)
Mar 16 14:07:09 socket  debug   server.lua: client 192.168.0.212:33702 read error: closed
Mar 16 14:07:09 socket  debug   server.lua: closed client handler and removed socket from list
Mar 16 14:07:09 socket  debug   server.lua: closed client handler and removed socket from list

The first line shows that your server connected to mine. Port 5000/tcp is the SOCKS proxy. And once I added proxy.riley.net to my DNS, those initial attempts to use proxies.telepathy.im went away.

What's confounding us is that Feathers and I have essentially identical setups. Yet while I can files to him, he can't send to me. We're perplexed!

[vinnywright]

I just excepted your invite samhobbs but you dont show as online right now ,,,,,steve dose .

my file transfer button in the chat window is grayed out ,,,but in the system tray it is not ?......strange.

VINNY

[Feathers McGraw]

Hmm yeah you're right. I can't remember if I checked my logs for that - does my client connect directly to your server or does my server connect to yours?

My proxy works fine for sending from conversations to conversations. I don't understand why I can't send to you (telepathy) a file from conversations though, when conversations to conversations works.

[SteveRiley]

When Vinny tries to send me a file, it also fails. The log:

Mar 16 16:18:19 c2s18a3de0      debug   Received[c2s]: <iq id='155672686668' type='error' to='vinnywright@kdetalk.net/kde-telepathy-275093'>
Mar 16 16:18:19 stanzarouter    debug   Routing to remote...
Mar 16 16:18:19 s2sout1697590   debug   going to send stanza to kdetalk.net from rileyz.net
Mar 16 16:18:19 s2sout1697590   debug   sending: <iq type='error' to='vinnywright@kdetalk.net/kde-telepathy-275093' from='steve@rileyz.net/kde-telepathy-489522' id='155672686668'>
Mar 16 16:18:19 s2sout1697590   debug   stanza sent over s2sout
Mar 16 16:18:27 s2sin1662e30    debug   Destroying incomplete session (unknown)->rileyz.net due to inactivity
Mar 16 16:18:27 s2sin1662e30    debug   Disconnecting (unknown host)[s2sin_unauthed], <stream:error> is: connection-timeout
Mar 16 16:18:27 mod_s2s debug   sending: <stream:error>
Mar 16 16:18:27 mod_s2s debug   sending: </stream:stream>
Mar 16 16:18:27 s2sin1662e30    info    incoming s2s stream (unknown host)->rileyz.net closed: connection-timeout
Mar 16 16:18:27 s2sin1662e30    debug   Destroying incoming session nil->rileyz.net: connection-timeout
Mar 16 16:18:27 s2sin1662e30    debug   s2s disconnected: nil->nil (connection closed)
Mar 16 16:18:27 socket  debug   server.lua: closed client handler and removed socket from list

[SteveRiley]

Hmm yeah you're right. I can't remember if I checked my logs for that - does my client connect directly to your server or does my server connect to yours?

From the log, it would appear that your server sets itself as a "target" and connects to my proxy. Then my server sets itself as an "initiator" and connects to my proxy. Finally my client streams the file to your client via my proxy. We should have checked your debug log during this same transfer to see what was happening on your end. I'm not sure if your proxy is also participating in this transfer.

[Feathers McGraw]

OK so since Vinny and I are both using the same version of telepathy, that must mean either it's a bug in telepathy that's fixed in the version you have, or there's something similar about the KDE server and mine causing the problem (did we ever compare prosody versions?), or it's and entirely different problem.

I will try sending from my gf's laptop to mine on my server tonight to see if that works. If it doesn't, I might just add that backports repo.. what else would that pull in? Would it update me to plasma 5 or is it just newer versions of applications?

[SteveRiley]

I will try sending from my gf's laptop to mine on my server tonight to see if that works. If it doesn't, I might just add that backports repo.. what else would that pull in? Would it update me to plasma 5 or is it just newer versions of applications?

Only a small collection of updated applications. In fact, it's mostly KTp 0.9 bits.

[Feathers McGraw]

OK, I've added the PPA and upgraded. Next time we get a change the testing is going to be interesting!