🕷 Automatically detect changes made to the official Telegram sites, clients and servers. https://t.me/tgcrawl
Go to file
GitHub Action ea8d1ff778 Update tracked links 2024-06-06 23:24:49 +00:00
.github return back web to macOS 2024-06-02 22:13:27 +02:00
.gitignore add Discord alerts 2023-06-08 17:48:58 +02:00
LICENSE add readme and license file 2021-04-24 17:34:55 +02:00
README.md Fix two strange typos 2022-07-02 17:36:46 +01:00
ccl_bplist.py add crawling of Telegram for iOS from TestFlight; 2022-05-09 12:05:55 +02:00
make_and_send_alert.py add android stable (from dl) 2024-02-20 09:21:36 +01:00
make_files_tree.py add android stable (from dl) 2024-02-20 09:21:36 +01:00
make_tracked_links_list.py control concurrent requests; a little optimization; upgrade python and deps 2024-06-02 16:06:24 +02:00
requirements.txt control concurrent requests; a little optimization; upgrade python and deps 2024-06-02 16:06:24 +02:00
tracked_links.txt Update tracked links 2024-06-06 23:24:49 +00:00
tracked_res_links.txt Update tracked links 2024-06-06 16:14:05 +00:00
tracked_tr_links.txt Update tracked links 2024-02-15 10:18:04 +00:00
unwebpack_sourcemap.py fix encoding 2023-09-15 22:57:06 +02:00


🕷 Telegram Crawler

This project is developed to automatically detect changes made to the official Telegram sites and beta clients. This is necessary for anticipating future updates and other things (new vacancies, API updates, etc).

Name Commits Status
Data tracker Commits Fetch new content of tracked links and files
Site links collector Commits Generate or update list of tracked links
  • passing new changes
  • failing no changes

You should to subscribe to channel with alerts to stay updated. Copy of Telegram websites and client`s resources stored here.

GitHub pretty diff example

How it works

  1. Link crawling runs as often as possible. Starts crawling from the home page of the site. Detects relative and absolute sub links and recursively repeats the operation. Writes a list of unique links for future content comparison. Additionally, there is the ability to add links by hand to help the script find more hidden (links to which no one refers) links. To manage exceptions, there is a system of rules for the link crawler.

  2. Content crawling is launched as often as possible and uses the existing list of links collected in step 1. Going through the base it gets contains and builds a system of subfolders and files. Removes all dynamic content from files. It downloads beta version of Android Client, decompiles it and track resources also. Tracking of resources of Telegram for macOS presented too.

  3. Using of GitHub Actions. Works without own servers. You can just fork this repository and own tracker system by yourself. Workflows launch scripts and commit changes. All file changes are tracked by GIT and beautifully displayed on GitHub. GitHub Actions should be built correctly only if there are changes on the Telegram website. Otherwise, the workflow should fail. If build was successful, we can send notifications to Telegram channel and so on.


Q: How often is "as often as possible"?

A: TLTR: content update action runs every ~10 minutes. More info:

Q: Why there is 2 separated crawl scripts instead of one?

A: Because the previous idea was to update tracked links once at hour. It was so comfortably to use separated scripts and workflows. After Telegram 7.7 update, I realised that find new blog posts so slowly is bad idea.

Q: Why alert for sending alerts have while loop?

A: Because GitHub API doesn't return information about commit immediately after push to repository. Therefore, script are waiting for information to appear...

Q: Why are you using GitHub Personal Access Token in action/checkout workflow`s step?

A: To have ability to trigger other workflows by on push trigger. More info:

Q: Why are you using GitHub PAT in make_and_send_alert.py?

A: To increase limits of GitHub API.

Q: Why are you decompiling .apk file each run?

A: Because it doesn't require much time. I am decompiling only resources (-s flag of apktool to disable disassembly of dex files). Writing a check for the need for decompilation by the hash of the apk file would take more time.

    # every rule is regex
    # empty string means match any url
    # allow rules with higher priority than deny
    'translations.telegram.org': {
        'allow': {
            r'^[^/]*$',  # root
            r'org/[^/]*/$',  # 1 lvl sub
            r'/en/[a-z_]+/$'  # 1 lvl after /en/
        'deny': {
            '',  # all
    'bugs.telegram.org': {
        'deny': {
            '',    # deny all sub domain

Current hidden urls list

    # 'corefork.telegram.org', # disabled




Licensed under the MIT License.