From a quick review of your blocks in your chat app, it appears you are storing a video, an audio, or an image to a specific tag for each type (using a separate cloudDB for each as well). The only issue I believe I can see is that these media items will overwrite the previous one when a new item is stored.
Also, given you are using the default cloudDB store provided by MIT, you/users may come under the heading of a "heavy user" and be blocked... (due to the use of large files such as videos/audio/images)
Please try to remain polite when asking for further help, typing in CAPITALS is considered rude and shouting.
Yes ... but I should delete those options ! They are ... fake ! Because they save olny the file position in the smartphone , and not the real file ( like in base64 ) ... So the user that has another phone cannot see correctly that image !
Personally, I would recommend that you use an online system designed to do what you want to do like Firebase to handle your chat (realtime database or firestore) and storage/delivery (firebase storage) of media files. Firebase can also provide user authentication and rules to handle privacy and security of data and media. In my opinon, cloudDB is not the best solution for what you want to achieve.
Ok , andd thank you ... but Firebase has a limitate storage , so I want to divide the base64 string into small pieces in different tags , and then I want to recompose it .
Can you , please , share to me a schreenshot of how should I use the blocks to make it real ?
I mean that I want a schreenshot of how should I use the blocks to make real the division of the base64 string into small pieces in different tags , that then it will be recomposed in the same blocks .
P.S. :
I want one solution that can make you share images , videos and audios from one phone to another using CloudDB and using this procedure