-
|
Hello and huge thanks to @ReagentX for creating this amazing tool. Just curious if it would be possible to create an option to save the exported chats with the contact name instead of the phone number? I'm able to see the saved contact's name once I open the HTML file, but can't identify the conversation when sifting through the directory's files. (Example: save as "BobBuilder.html" instead of "8794356609.html"). Please let me know if this is possible already and I'm just missing it somehow. I did read through the reasoning in #64 for the requirement of unique handles in the output file naming, but I wonder if there is a way to handle this case differently? I imagine there may not be too many cases where two contacts have the same exact full name. Thank you again! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
There’s no built-in option to export using contact names as the primary filename; this is intentional for several technical reasons tied to ensuring the exporter remains reliable and avoids potential data issues. Contact names aren’t guaranteed to be unique in your address book or across exports. Even if rare, assuming uniqueness could break exports unpredictably for some users, and we’d rather err on the side of caution. Using inherently unique identifiers from iMessage’s database guarantees no collisions without extra logic. The exporter guarantees a 1:1 mapping between a conversation and a file. Once we allow non-unique identifiers at the filesystem level, we risk collisions and silent overwrites. |
Beta Was this translation helpful? Give feedback.
There’s no built-in option to export using contact names as the primary filename; this is intentional for several technical reasons tied to ensuring the exporter remains reliable and avoids potential data issues.
Contact names aren’t guaranteed to be unique in your address book or across exports. Even if rare, assuming uniqueness could break exports unpredictably for some users, and we’d rather err on the side of caution.
Using inherently unique identifiers from iMessage’s database guarantees no collisions without extra logic. The exporter guarantees a 1:1 mapping between a conversation and a file. Once we allow non-unique identifiers at the filesystem level, we risk collisions and silent…