Repository navigation
XEP-0363 HTTP Upload Implementation Progress #736
Description
Activity
Incoming link only messages should either have an obb-tag providing the same link or have the aesgcm:// scheme to be considdered as filetransfer (as opposed to a link just copy 'n pasted by the user).
Thanks a lot for your great work. You put a lot of effort into this project, and I am sure that many (including me) appreciate that A LOT. HTTP Upload is the most important feature I'm waiting for to use ChatSecure/XMPP as my main IM. Keep it up! 😄 And thanks a lot.
how , i can add the XEP-0363 Xmpp Extensions for image sharing and file uploading.
i Added XEP-0363 Extension into My Project.
But I Can't find specific solution about that.
Please give me solution to asap.
I am waiting for long time about this.How is the progress in this matter (on the way to 4.1)?
- Mostly works but needs to be finished up. Development on this was on hold for a bit.…On Sun, May 14, 2017 at 3:29 AM, therob84 ***@***.***> wrote: How is the progress in this matter (on the way to 4.1)? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#736 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAfqH29AniOSWHUaGnSThx9TBkedp4Awks5r5teDgaJpZM4M4GCp> .
- Good to hear good news, Chris. Plan ist still to come with 4.1? And you will manage to bring it togehter with inline image display and compatibility with conversations, right? Any rough date estimates (release)? Thanks for your continouing good work!
Sending and receiving now works! Still gotta clean it up though, so don't expect a release any time soon.
Reacted by therob84, afriedmanGlacier, Ludovic Terrier, Saad and Thilo MolitorIs this checked in to Github? The sending/receiving process.
What's the current situation of handling aesgcm:// received from Conversations on Chatsecure
- it works…On Tue, Nov 28, 2017 at 11:08 PM, Matt Suiche ***@***.***> wrote: What's the current situation of handling aesgcm:// received from Conversations on Chatsecure — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#736 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAfqH82lCUA9_U0kZSwJxqa_QPCUtcxSks5s7QLtgaJpZM4M4GCp> .
it works
…
On Tue, Nov 28, 2017 at 11:08 PM, Matt Suiche @.***> wrote: What's the current situation of handling aesgcm:// received from Conversations on Chatsecure — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#736 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAfqH82lCUA9_U0kZSwJxqa_QPCUtcxSks5s7QLtgaJpZM4M4GCp .Thanks alot @chrisballinger for providing a goot platform for chat on iOS and Android.
I am using ejabbered server.
Following is my findings...Android : Conversations
iOS : ChatSecure-iOSUnencrypted mode of file transfer works in all the scenarios ( iPhone <--> iPhone, iPhone <--> Android )
OMEMO Encrypted mode of file transfer works in the scenarios ( iPhone <--> iPhone, iPhone --> Android ). But in Android --> iPhone not works.I found Aes Gcm used for file's encryption and decryption. Is this make any problem with this ?
Please help me...
@skumarm Update Conversations to 2.3.5
If you use the F-Droid version, do install the F-Droid client so you get updates too.
Outgoing:
URLfrom secure storage instead of loading entire file into memoryaesgcm://scheme for OMEMO-capable clients. Use https for forced plaintext.What to do for OTR-only?DataShould we continue to support sending OTRDATA if 0363 is not available?Incoming:
aesgcm://scheme while downloading to media store.Original issue #681