telegram-export-explorer 0.0.2

A tool for parsing and exploring exported Telegram conversations

Telegram Export Explorer

A tool for parsing and exploring exported Telegram conversations

Like many families, mine uses Telegram to keep in touch. I was worried about losing that family chat history, though. Fortunately, Telegram offers the ability to export your conversations to HTML. You can find instructions at https://telegram.org/blog/export-and-more.

The exported files are a bit hard to navigate and search through. I've created this project to make it easier to browse through our chat history. It finds and parses the "messages.html" files and loads them into a SQLite database. In the future I'd like to build a Flask app to make exploration even easier. Until then, I'm using Datasette to browse our conversations. By using foreign keys in the database, Datasette makes navigation a breeze.

Hopefully other people can find this useful as well. If there are any features you'd like added, or bugs you'd like fixed, please file an issue in the repo. Note: If you include example data in your issue, please make sure to anonymize your example. I don't want to know what you and your family have been up to.

Warning: This project is still under very active development, and the API and database schemas will be changing. For the time being, you cannot rely on semantic versioning to keep you safe. (I'd be on release 100.0.0 by now if it were!)

Installation

pip install telegram_export_explorer

Usage

This package provides both a CLI interface and a Python library that can be used for parsing Telegram exports.

Assuming your exported chats are in ~/Downloads/my-family-chats/, and you want to create a SQLite database called messages.db, you can run:

build-telegram-db ~/Downloads/my-family-chats/ messages.db

If you want to generate the same database from your Python code, you could use something like this:

from telegram_export_explorer import build_db

build_db('~/Downloads/my-family-chats/', 'messages.db')

The generated database can be explored using Datasette:

datasette -o messages.db

Notes

• The following messages are ignored because they don't include a timestamp
  • Voice chat-related messages
  • Pinned message notifications
  • Group photo changed
  • Group converted messages, for when a conversation is converted from one type to another
• Invitation notifications are used to populate the members of a group chat, even if the inviter and invitee never post a message in the chat. This lets you know that your Aunt Dorthy was lurking but never posted.
• Similar to invitation notifications, messages about a user joining a group record the user as a member of the group even if they never post.
• Telegram messages contain a message id. This can't be trusted to be globally unique, or even unique within the same conversation if that conversation is spread across multiple files. The "messages" table contains a unique "id" field, and the Telegram message id is stored in the "message_id" field.
• Message timestamps are stored in ISO-8601 format as UTC
• If text is present in a message, its original html is stored in the "html_text" field, and the plaintext is stored in the "plain_text" field
• If a message contains a poll, the question is stored in the "media_poll_question" field, and the entire poll is stored as HTML in "media_poll_html"
• Some file attachments contain invalid unicode characters in their filenames. When these are detected, and error message is displayed and the attachment is not inserted into the database.

To Do

• Add support for group title changes
• Add support for forwarded messages
• Add support for message replies
• Improve argument parsing
• Create a Flask app to make this easier to navigate

Database Schema

erDiagram
    group_chats {
        integer id PK
        string title
    }

    group_chat_aliases {
        integer group_chat_id FK
        string title
    }
    group_chat_aliases }|--|| group_chats : "group_chat_id = id"

    messages_files {
        integer id PK
        integer group_chat_id FK
        string name
    }
    messages_files }|--|| group_chats : "group_chat_id = id"

    users {
        integer id PK
        string name
    }

    messages {
        integer id PK
        integer group_chat_id FK
        integer messages_file_id FK
        integer sender_id FK
        string html_text
        string media_poll_html
        string media_poll_question
        string message_id
        string plain_text
        string timestamp
    }
    messages }|--|| group_chats : "group_chat_id = id"
    messages }|--|| messages_files : "messages_file_id = id"
    messages }|--|| users : "sender_id = id"

    group_chat_memberships {
        integer group_chat_id FK
        integer user_id FK
    }
    group_chat_memberships }|--|{ group_chats : "group_chat_id = id"
    group_chat_memberships }|--|{ users : "user_id = id"

    file_attachments {
        integer id PK
        integer message_id FK
        integer size
        string mime_type
        string path
        string title
    }
    file_attachments o|--|| messages : "message_id = id"

    photo_attachments {
        integer id PK
        integer message_id FK
        integer size
        string mime_type
        string path
    }
    photo_attachments o|--|| messages : "message_id = id"