Telegram RegisterThe public register of Telegram
Telegram profile photo for Anscombe's Quartet

Channel

Anscombe's Quartet

@anscombes_quartet

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

508subscribers

-1 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001138907699
TypeChannel
Username@anscombes_quartet
CreatedBetween 1 March 2017 and 30 April 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live23 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/anscombes_quartet

Growth

508509508.56 August 2026 — 509 subscribers6 August 2026 — 509 subscribers23 August 2026 — 508 subscribers6 August 202623 August 2026
3 measurements spanning 17 days, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 508–509 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 06:58508-1
6 Aug 2026, 18:34509no change
6 Aug 2026, 04:29509first reading

Engagement

20 posts held, back to 2 April 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 20 May 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

79 reactions across 16 posts, in 4 distinct kinds. The most used accounts for 50.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4050.6%
🔥2430.4%
1417.7%
🤩11.27%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 17 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 79reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 2 April 2023 to 20 May 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

20 May 2025, 16:46 UTC465 views6 reactionsread 6 August 2026

В этом году буду (впервые) на Data and AI Summit 2025, да еще и сразу доклад + training! Мой топик в этом году - это Data applications, и наши Databricks Apps в первую очередь. Вместе с моим коллегой Giran Moodley мы подготовили 90 минут технического (в первую очередь) контента по следующим вопросам: - Frameworks & tooling — Pythonic (Dash, Streamlit, Gradio) vs. JS + Python stack - Development lifecycle — Debuggin

👍5🔥1

19 Mar 2025, 13:13 UTC496 views4 reactionsread 6 August 2026

27 марта буду в Берлине в рамках Data Intelligence Days рассказывать про AI applications on Databricks Data Intelligence Platform. Расскажу про e2e цикл построения и деплоя AI apps и агентов - от ingestion до деплоя и governance. Ну и конечно же не только я один выступаю - будут сессии про Unity Catalog и Databricks SQL, а еще есть возможность записаться на тренинг по SQL analytics and BI. Эвент бесплатный, а заре

🔥4

6 Mar 2025, 10:08 UTC553 views5 reactionsread 6 August 2026

Весеннее солнце потихоньку размораживает Берлин, и я даже нашел в себе силы выйти на улицу. Конечно же исключительно для того чтобы 10 апреля прийти на следующую Databricks Berlin User Group. Коллеги из dbt будут рассказывать про dbt + data quality with dqx. Я же расскажу про E2E RAG + sources retrieveal с кастомным чатом на Dash + Databricks Apps. Это довольно интересный проект, в нем полная начинка современных LL

👍5

11 Feb 2025, 21:14 UTC523 views4 reactionsread 6 August 2026

Я у мамы стример Наш новый product surface - Databricks Apps набирает популярность среди клиентов, и в целом открывает много возможностей как для Data/ML Engineers, так и для Software Developer-ов. Возможность хостить свои приложения в интегрированной среде непосредственно с данными и ML моделями - это классная вещь, ведь теперь можно имплементировать самые сложные сценарии с user feedback loop и прочим. Вот об это

👍4

24 Jan 2025, 15:41 UTC509 views1 reactionsread 6 August 2026

Закончил первый блок работы по добавлению документации к двум нашим Databricks Labs проектам - UCX и DQX. UCX это migration assistant для Unity Catalog, и для него уже была довольно большая (но не совсем удобная) документация в формате Readme файла. Я этот файл аккуратно раскроил на несколько секций, и получилось вот такое: - https://databrickslabs.github.io/ucx/ DQX - это наш новый фреймворк для Data Quality. Для

1

25 Dec 2024, 22:17 UTC617 viewsread 6 August 2026

Язык Python (как впрочем и любой другой) не без проблем и коммьюнити старается эти проблемы решать. Помню что где-то в 2023 Python Package Index присылали мне как package maintainer письмо с гигантским вопросником на тему “как нам улучшить project and dependency management”. С тех пор утекло немало воды, и появилась целая плеяда утилит для Python package management - poetry, hatch, flit, rye. Сравнительно недавно вы

19 Nov 2024, 16:44 UTC546 views9 reactionsread 6 August 2026

Fresh off the press - буквально только-только вышла наша e-book по теме Data Governance и Unity Catalog! Скачать ее можно вот тут - 🔗 Data Governance Architecture Patterns Я тоже поучаствовал в процессе и написал пару глав, описывая в деталях потенциальную структуру UC metastore и naming conventions.

👍6🔥21

6 Nov 2024, 21:15 UTC601 viewsread 6 August 2026

Закончил большой и обстоятельный пост про проект на нашей новенькой технологии - Databricks Apps, и рассказал в деталях по ссылке ниже. В целом очень рад что платформа за последние год-полтора обросла технологиями которые позволяют отстроить e2e data application - начиная от ingestion/etl, затем serving, а теперь вот еще и API + UI. https://www.linkedin.com/posts/ivan-trusov_databricks-databricksapps-react-activity-

7 Oct 2024, 21:47 UTC628 viewsread 6 August 2026

Решил написать небольшую серию постов про мое видение прошлого, настоящего и будущего архитектур данных. Первый про DWH и архитектуры 2000-начала 2010x годов. Если кто что интересное из того периода вспомнит - welcome в комменты 🙂 https://www.linkedin.com/pulse/aevum-data-digitalis-part-1-operations-facts-ivan-trusov-dmnlf

22 Aug 2024, 14:40 UTC589 views6 reactionsread 6 August 2026

Databricks User Group - это отличный способ узнать новое про современные DE/ML/BI решения, а так же нетворкинг (и пиво конечно же!). В этот раз мы проводим эвент в Кёльне. David Schenk, Lead Data Platform Engineer будет рассказывать real-life кейс от OBI. Я же скромно поведаю про наш обновленный Databricks Monitoring, с примерами и демо. 📅 Date: October 10, 2024 🕒 Time: 6 PM welcome reception, 6:30 PM starting with

6

9 Aug 2024, 10:11 UTC≈1,270 views11 reactionsread 6 August 2026

У нас в Databricks EMEA team открылись две позиции для Sr. Specialist Solutions Engineer по тематике DWH ⚡. Много интересных задач - как миграции так и greenfield проекты, можно работать на ремоуте (но возможен travel up to 30%). Рассматриваем кандидатов с EU work permit, преимущественно в Германии. 🔗 Полное описание позиции здесь 🤝 За рефером можно написать мне в LinkedIn

🔥83

3 May 2024, 13:30 UTC794 views10 reactionsread 6 August 2026
Photo

6 июня в Цюрихе буду рассказывать про CI/CD на Databricks on AWS. Буду показывать как использовать современный toolset для такой разработки (hatch, DABs, pytest with testcontainers, Github Actions with self-hosted runners). ссылка на регистрацию - https://aws-experience.com/emea/dach-cee/e/6c859/aws-builders-day

👍6🔥3🤩1

Showing the 12 most recent of 20 posts we hold for @anscombes_quartet. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 1,549,633 of 1,604,161entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 23 August 2026 — this entry's latest reading, not the date you are reading this.

“Anscombe's Quartet” (@anscombes_quartet), 508 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/anscombes_quartet.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.