-
-
Notifications
You must be signed in to change notification settings - Fork 62
Open
Labels
support requestGuidance needed when running the toolGuidance needed when running the tool
Description
Thank you for this amazing and powerful tool!
I'm going to try importing a Messenger (Facebook/Meta) conversation into Signal using the "Telegram/JSON" method. I've exported the conversation in JSON format, and here's the schema (Fields marked with [] indicate that there can be multiple items.):
{
"participants[]": {
"name": {}
},
"messages[]": {
"sender_name": {},
"timestamp_ms": {},
"content": {},
"is_geoblocked_for_viewer": {},
"is_unsent_image_by_messenger_kid_parent": {},
"photos[]": {
"uri": {},
"creation_timestamp": {}
},
"reactions[]": {
"reaction": {},
"actor": {}
},
"share": {
"link": {},
"share_text": {}
},
"audio_files[]": {
"uri": {},
"creation_timestamp": {}
},
"gifs[]": {
"uri": {}
},
"files[]": {
"uri": {},
"creation_timestamp": {}
},
"videos[]": {
"uri": {},
"creation_timestamp": {}
},
"sticker": {
"uri": {},
"ai_stickers[]": {}
},
"call_duration": {},
"is_unsent": {},
"missed": {}
},
"title": {},
"is_still_participant": {},
"thread_path": {},
"magic_words[]": {}
}Is it possible to get the exact schema expected by signalbackup-tools in order to create a small script that will adapt the properties accordingly? I understand that it's inspired by the Telegram schema, but is there any flexibility in the method, and which fields are strictly required?
Thank you very much!
Metadata
Metadata
Assignees
Labels
support requestGuidance needed when running the toolGuidance needed when running the tool