Telegram RegisterThe public register of Telegram

Channel

Таков webdev

@about_webdev

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

56subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001509443104
TypeChannel
Username@about_webdev
DescriptionПишу про свои проекты, делюсь полезными ссылками про webdev и мыслями о разработке
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/about_webdev

Growth

567 August 2026 — 56 subscribers10 August 2026 — 56 subscribers7 August 202610 August 2026
2 measurements spanning 2 days. 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 55–57 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 07:4656no change
7 Aug 2026, 20:0456first reading

Engagement

20 posts held, back to 1 April 2025the 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 19 November 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
32
Videos
2
Links
63

Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

42 reactions across 15 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2150.0%
👍1535.7%
🤯614.3%

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 15 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 42reactions 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 1 April 2025 to 19 November 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

19 Nov 2025, 07:00 UTC65 views2 reactionsread 10 August 2026

А куда делось слово «блокчейн» в описании и презентациях компаний?

👍2

30 Oct 2025, 15:24 UTC96 viewsread 10 August 2026
Photo

Задача из разряда «вроде изян» #aboutwebdev_мем

17 Oct 2025, 11:37 UTC114 viewsread 10 August 2026

https://vc.ru/dev/156552 Статья про то, как сделать идеальную форму регистрации! Какое-то время назад я писал форму регистрации с бэком и эта статья очень помогла бы мне сделать ее более юзер-френдли! #aboutwebdev_моярекомендация

15 Oct 2025, 11:13 UTC96 views1 reactionsread 10 August 2026

Новости В последнее время я больше занимаюсь мобильной фотографией, но про автоматизацию деятельности не забыл. К примеру, для своего канала @kadromomento я написал бота. Его функционал: - добавляет водяной знак на фото и умно сжимает ее, несильно теряя в качестве; - публикует пост, одновременно добавляя на все добавленные фото водяной знак и сжимает их, как в первом пункте. Постепенно постараюсь оживлять и этот к

👍1

7 Sept 2025, 10:11 UTC128 views4 reactionsread 10 August 2026

Подумываю написать статью о пути создания и закрытия проекта IT Meetups bot #aboutwebdev_анонс

👍4

14 Aug 2025, 08:22 UTC150 views6 reactionsread 10 August 2026
Photo

- статус по задаче пока не изменился. Она в работе #aboutwebdev_мем

👍3🔥2🤯1

14 Jul 2025, 19:35 UTC206 views6 reactionsread 10 August 2026

Отключение бота-агрегатора IT Meetups bot Я отключаю бота-агрегатора IT Meetups bot. 750+ пользователей подключили его с октября 24 года. Хорошая была история. В одного довольно непросто поддерживать бота в рабочем состоянии, с точки зрения отслеживания и добавления новых анонсов. Да и создавал его в не лучший для себя период, и как будто этот проект является напоминанием о том времени. Помню, Бот занял 4 место

🤯5🔥1

3 Jul 2025, 10:21 UTC223 views6 reactionsread 10 August 2026
Photo

На месте #aboutwebdev_митап

👍3🔥3

26 Jun 2025, 08:28 UTC251 views5 reactionsread 10 August 2026
Photo

База, проверенная временем и опытом #aboutwebdev_мем

🔥5

22 Jun 2025, 16:39 UTC220 viewsread 10 August 2026

Темная тема блога Мой знакомый и соратник по разработке Егор предложил сделать для моего блога темную тему. Я не стал отказываться от такого предложения и теперь в зависимости от системных настроек будут отображаться приемлемые стили. Ссылка на блог: https://sqlzzy.dev/ Подписывайтесь на канал Егора: @frtvt #aboutwebdev_блог

20 Jun 2025, 16:11 UTC169 views1 reactionsread 10 August 2026
Forwarded from @moscowjsPhoto

Много кто пользуется telegram, но не все знают, как научить его решать нужные вам задачи. Про это расскажет разработчик Серёжа Осипов в докладе «Свой бот — проще, чем кажется». Экосистема telegram развивается, и сейчас каждый может создать бота или Web App. А вместе они дают не только мощный инструмент для личной продуктивности, но и для бизнеса. 🤖 В докладе Серёжа поделится историей о том, как благодаря этому упр

👍1

Showing the 12 most recent of 20 posts we hold for @about_webdev. 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“Таков webdev” (@about_webdev), 56 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/about_webdev.

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.