Support for proper HistorySync parsing and S3 attachment handling #231
Description
I would like to clarify whether there are plans to implement native parsing of HistorySync archives and full processing of synced messages, including automatic attachment handling and S3 uploads.
Currently, HistorySync arrives as a raw message payload, and the service does not parse its structure or process media attachments. As a result, we must manually parse the HistorySync data, extract messages, download media files, and then upload those attachments to S3 ourselves.