-
-
Notifications
You must be signed in to change notification settings - Fork 815
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File transfer #23
Comments
It's an old XEP, now we have: http://xmpp.org/extensions/xep-0234.html |
I'd like to work on this. Any progress so far? @alkino that link says "WARNING: Consideration of this document has been Deferred by the XMPP Standards Foundation. Implementation of the protocol described herein is not recommended." |
Hi. Is it still valid, it's only that nobody proposed it as a draft. So it's the way to go even it's deferred. From jdev@conference.jabber.org
|
any updates? |
According to commit log there was no commits for a several month. |
+1 for file transfer support |
We also have SOCKS5 proxies. Both prosody (XMPP server) and pidgin (XMPP client) supports it natively. Perhaps Xabber could too? |
+1 for file transfer, the last "big" feature missing in xabber imho |
Which way? In the new way you need UPnP or meeting point if you don't use IBB. You |
Another way would be to use xep-0114 (http://xmpp.org/extensions/xep-0114.html) as Conversations does since 1.5.0. Siacs implemented a little plugin to serve this (https://github.com/siacs/HttpUploadComponent). The benefit is that you do not need the other client to support the file transfer xep, too. It's way more usable that way. |
I would go with the XEP-0114 that @tbeitter mentioned. I think pidgin uses this too? I have a SOCK5 file transfer proxy component set up in prosody on a subdomain that I use in pidgin. |
the xep-0114 is not the socks transfer. It's used to upload the shared file to the server and the recipient will only get the http/https link to the file. That way there is no need to implement a file sharing logic on the recipient's side. |
@tbeitter Ok. So does pidgin handle this all automatically, or does it use some other method? I can't send files to someone using Xabber currently because it tells me that the recipient doesn't support it. This suggests that it uses some other method, but as for what I have no idea. |
XEP-0363: HTTP File Upload allows us to share files in conferences and with offline contacts but requires an additional component on the server already implemented in a lot of servers thanks to Conversations. It works perfectly so maybe it should be the best option to include instead of Jingle and Legacy because it's not necessary to have another client which enabled the XEP (it just shows a link to download the file). |
@moshpirit thanks! Could you suggest several servers for testing? |
I'm on the street so I just can tell you that suchat.org allows it and works perfectly. Maybe mijabber.es too. Sorry for not telling you more servers :( |
If my server supports it, I can give you an account or two on it if you want :) Address: starbeamrainbowlabs.com I've just installed mod_http_upload - I think that adds support for XEP-0363 to prosody. Here's the relevant snippet from my server's config file: Component "filetransfers.starbeamrainbowlabs.com" "proxy65"
modules_enabled = {
"http_upload";
} Just ask and I will create you an account or two, and send you the login details by email if you provide an address. |
In new 1.0.51 version of Xabber Beta I've implemented HTTP file upload XEP-0363 (with new namespace, so server module should not be old). |
Awesome! Can't wait for the next beta release. |
@grigoryfedorov Done. No problem! Keep the test accounts and do whatever you like with them (except give the login details to anyone who isn't working on Xabber of course). Just contact me if you want a new module installing :) |
A different name? Why?? Thanks for the great work here, but changing actual XEPs while requiring that the servers use it too doesn't sound really good to me :( |
@moshpirit Different name? I assumed that the new mod_http_upload that @grigoryfedorov linked to was just an update. |
Oh, then I'm sorry, I've just woken and I probably I read it wrong. If that's the case, I'm really sorry for the misunderstanding. That's even better news!! \o/ |
@moshpirit I didn't read the diff properly.... so I don't actually have On 08/10/15 17:36, moshpirit wrote:
|
@moshpirit you can see this issue siacs/HttpUploadComponent#51 in the HttpUploadComponent (namespace was different from XEP, and was fixed not far ago) |
Oh, OK ;-) |
@moshpirit It's already been released in the beta channel! |
Yes, but AFAIK you need a Google account for it. |
@moshpirit Don't you need a Google account to install any android app? |
Of course not! I use F-droid. The only service I use from Google is YouTube and I use it from TOR browser. I've been living without any Google account for 2 or 3 years. |
@moshpirit I didn't know that. My phone asks me to sign in before I download apps. -------- Original message -------- Of course not! I use F-droid. The only service I use from Google is YouTube and I use it from TOR browser. I've been living without any Google account for 2 or 3 years. —Reply to this email directly or view it on GitHub. |
Now possible with http-upload in Xabber 2.0 |
If there would be a way to send files via xmpp, and to see them in-chat, we could push whatsapp to the trash bin.
XEP-0096 - http://xmpp.org/extensions/xep-0096.html
The text was updated successfully, but these errors were encountered: