MessageGrabbers is a utility designed to download message and their associated attachments as raw content from various platforms, which include Discord and Telegram for now. This tool can be expanded by writing a plugin, which can be attached to the executable, allowing the expansion for other platforms outside Discord and Telegram.
Unlike tools that convert or reformat messages, this tool relies on preserving the original,
unaltered data as much as possible, such as raw JSON for platforms like Discord. The only
alteration for Discord is with attachments, where a little object called local_file is
attached, allowing rendering offline. A good example is with Discord, where authorizative
headers (ex, is, hm) are needed to have the file being rendered in the first place.
- Raw Message Downloads: Fetches messages in their original format, being unparsed as possible
- Attachment Grabbing: Automatically downloads any attachments visible within the message content.
- Platform Expansive: Originally to preserve content from Discord due to their simple APIs and using the Telegram APIs, this tool allows to be modified without altering the core coding itself
- Data Preservation: Ideal for archival, analysis or debugging, where the original message structure is crucial.
Many existing tools process messages into more "human-readable" formats, which are in web-page content (HTML), raw text formats (TXT) or even word-document things (DOCX, PDF). While useful for casual browsing, this often means losing certain valuable metadata or the precise structure of the original message. To avoid such issues, this tool focuses on fetching the raw contents, prioritizing in example of Discord:
- Deeper Analysis: Each message contains attachments, timestamps (creation, modification), pin information, the author, flags, type, and if TTS (Text to Speech) was enabled.
- Archival: These contents can be stored to preserve the data for future interactions, such as exposing someone (if someone even is willing to do that), while making sure that the data is not altered by the end-user.
- Discord (via the Browser APIs)
- This requires your own Authorization Discord Token. I am not designing a Login Phase, meaning that you need to know the Discord Token, Guild ID (if needed) and the Channel ID itself.
- Telegram (through the TDLib API)
Coming soon, this tool itself is still under development