Given that most servers have a 20mb file limit, and sharing some video doesn’t compress well, if at all, to that size, as well PDFs, multiple photos, etc. It would be very useful to have some kind of implementation of a multi-part attachment message. Like the “Sharer” XDC does not work for mobile platforms (Desktop only), and does not fall in to “media” section of UI, or allow for file deletion/organization.
Something like split the attachment into zip, and recombine in the receiving app? No change in UI needed, just backend handling of files that exceed message size limits. As it is there is no in-app advice for a user in what to do or why it went wrong except the technical error. This is not good for ‘everyday’ user.
This, along with the ability to edit/rescind messages is the #1 and #2 reasons this is not yet a viable messenger to switch to, at least in my sphere.
To clarify, it DOES work in mobile platforms but there is currently no way to export directly to filesystem (which is probably what you meant).
There is PR for iOS that might solve this, and in Android it will probably will be solved in the future.
I think there are plans to allow deleting updates which would allow the app to delete files.
And organization of files can be implemented later, it’s just a matter of doing it.
Also in the future there may also be some P2P WebXDC for file transfer using the new Realtime channels.
Yes, something to negotiate P2P transfer of some kind would be good = I’m thinking of trying to have onboarding be as lateral transfer as possible for those used to Telegram or WhatsApp, and it can be confusing to have the ‘well you need to install this other plugin that does unknown stuff to do the things you normally expect’
Element, which has fewer limitations than DC, is too complicated for many used to Telegram/Whatsapp et al. DC has the potential to be easier through the QR and links, but means that just ‘family communication’ can be stunted because of email attachment handling
I believe that ideally you don’t need to depend on something. You can also share at this share.xdc to refine. We need the following type of capability: For example, if the file download is above 25 MB or the download is rejected by the server because the file is large, then we need to send the file P2P. And it’s all in the vending machine. At the level of Delta Chat itself.
Well, the sharer xdc is a good start, but honestly, while technically fun, it is not something people I know would use. If it were backend (as I think you’re saying), then yes
If file <20mb, then send as attachment
If error b/c of files size, prompt with P2P or XDC solution is a step up. Ideally this could happen without showing in the UI as an XDC plugin… something added and auto negotiated in the UI?
Ah, is this app yours too?, really nice
I didn’t quite understand what it does in the background, does it actually send an email for each split part and bring it together bypassing to send messages in the chat window?
Got it, very nice application as well that the files remain well listed and accessible.
Although maybe it would be a good idea to make the size of the chunks customizable so you can optimize based on the maximum limit of the servers? for example typically the size is 20mb so it would be useful to be able to enter choose a value greater than 12 but less than 24, what do you think?
For this a problem arise, delete the file only on the interface or also all related emails?
Besides this makes me think that in chatmails after a while the files are deleted by themselves since the servers from what I seem to remember automatically delete the emails after a while
Ideally on all devices of the user. But that deletion would probably be asynchronous (delete my copy of a given file an all my devices, whether sent or received, but not impacting the recipient, unless “disappearing messages implemented” then multi-part file should also go away.
Again, was trying to send a video recording of a section of a parade today. while compression was nice (500mb to 40mb), 40mb was still too much, and meant file transfer needed to be unsecure cloud, which given the context and content, was fine, but for remains very poor for onboarding-- the recipient wanted to know why a link was necessary (WA/Telegram/Signal/Element all can handle fine).
Love the tech behind DC, but this is a challenging setback for regular comms, and group sharing.