yes, but with 50MB of monthly email quota and a slow connection, no one wants to send a big file using email anyway
That is true.
he is not Cuban so he hasn’t that problems
Let me re-frame the conversation based on what I’m hearing:
- Probably Delta.chat project would like to stick to email as a fundamental value to the vision of the project, which I understand and respect.
- At the same time, there are known limitations in terms of size and storage for most email providers that sooner of later can be a user experience issue for the app.
With that in mind: What would be the main characteristics that a file transmission system should have in order to align with the project vision? Once that is clear we might want to evaluate if there is already a solution that full-fit that or not.
- every further external dependency makes DC more complicated.
- as adbenitez says: Sending large files is not a good idea in slow networks.
- How stable is a direct p2p connection? I think sending reasonable file junks by mail could be the more stable solution.
- splitting files for sending them by email is commonly used with standard MUA and there is not really a problem when using this approach if servers have the space and bandwith.
I think the way to split files to several mails is the easiest approach because all technology is existing in DC.
A first approach could work without sync mechanism. This would at least serve for people with big enough space at server.
… and is usable by standard MUA too in a manual way!
This issue is not very important?
https://ipfs.io/ should fit the bill.
It is required an internet connection to use the ipfs network.
People in Cuba pay for mail only and using intranet a big part of the time. Internet connection is expensive in comparison with the intranet.
Upload multiple files with simple drag-and-drop and manage all your content from a beautifully simple control panel.
Respect your recipient’s email storage and isp bandwidth