Telegram RegisterThe public register of Telegram

Channel

Blazor Community

@BlazorChannel

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

797subscribers

+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-1001222300222
TypeChannel
Username@BlazorChannel
DescriptionСтатьи, гайды по технологии blazor и webassembly Большая база знаний по Blazor: https://github.com/AdrienTorris/awesome-blazor Чат: https://t.me/BlazorCommunityChat По всем вопросам писать: @chesh111re
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/BlazorChannel

Growth

7977 Aug 2026, 00:33 — 797 subscribers7 Aug 2026, 00:47 — 797 subscribers7 Aug 2026, 00:337 Aug 2026, 00:47
2 measurements taken within a single day. 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 796–798 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 00:47797no change
7 Aug 2026, 00:33797first reading

Engagement

20 posts held, back to 17 July 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 27 October 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
22
Links
368

Lifetime counters from Telegram’s own channel header, read 7 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

170 reactions across 20 posts, in 17 distinct kinds. The most used accounts for 42.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍7342.9%
🔥3218.8%
1710.0%
🍾137.65%
84.71%
🥰74.12%
custom 524467345808373440742.35%
🤔42.35%
🥱31.76%
👏21.18%
👀10.588%
👎10.588%
🗿10.588%
😁10.588%
🙏10.588%
🤓10.588%
🤩10.588%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.

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 20 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 170reactions 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 17 July 2023 to 27 October 2024, 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

27 Oct 2024, 12:23 UTC≈2,840 views12 reactionsread 7 August 2026

29 октября в 19:00 (GMT+3 ) пройдет ASP.NET Community Standup на тему "Making DevToys 2.0 cross-platform with Blazor Hybrid", где разработчики DevToys расскажут о своем опыте перехода на кроссплатформенность с использованием Blazor Hybrid. YouTube: https://www.youtube.com/watch?v=8yM4jDooWcM DevToys: https://devtoys.app/ @BlazorChannel #Blazor

👍63🔥3

21 Oct 2024, 05:01 UTC≈2,490 views6 reactionsread 7 August 2026
Photo

Близится .NET Conf 2024, которая пройдёт с 12 по 16 ноября. По традиции публикуем расписание секций, которые затрагивают Blazor и смежные области. Время указано в GMT+3. 12 ноября: - 22:15 - 23:00 - What's New for ASP.NET Core & Blazor in .NET 9 (Daniel Roth) - 2:15 - 2:45 Build hybrid apps with .NET MAUI (Beth Massi, Eilon Lipton) 14 ноября: - 4:30 - 5:00 Using Blazor to manage data in SQL server and Microsoft Fab

🔥31🗿1🤓1

14 Oct 2024, 07:34 UTC≈2,070 views6 reactionsread 7 August 2026

Если вы работаете со связкой Blazor WASM + Яндекс Браузер, но дебаг не работает, то можно попробовать способ с переименованием процееса: https://habr.com/ru/articles/850234/ @BlazorChannel #Blazor

🥱3🔥21

27 Sept 2024, 07:35 UTC≈2,210 views10 reactionsread 7 August 2026

На днях прошел .NET Days 2024 от JetBrains. На двухдневном мероприятии было два доклада, касательно Blazor: - Crafting Blazor Components With Precision and Assurance от Mariekie Coetzee. В этой сессии рассматривался Blazing Story (storybook для Blazor), а также рассказывали как использовать playwright для тестирования компонентов. - Into the Rabbit Hole of Blazor Wasm Hot Reload от Andrii Rublov. В этой сессии было м

👍7🔥21

19 Aug 2024, 05:59 UTC≈2,120 views17 reactionsread 7 August 2026

Чего новенького в Blazor в ASP.NET Core .NET 9 Preview 1-7: - DI через конструктор в компонентах; - При использовании interactive server rendering по-умолчанию будет использоваться WebSocket compression; - В KeyboardEventArgs пояивлось новое свойство - IsComposing. С его помощью можно отслеживать composition state. Подробнее про iscomposing и composition state: https://w3c.github.io/uievents/#dom-keyboardevent-iscomp

👍8🔥4custom 52446734580837344074🙏1

5 Jan 2024, 11:49 UTC≈3,220 views16 reactionsread 7 August 2026
Photo

Хотим поздравить всех с Новым 2024 Годом❤️ Спасибо, что остаётесь с нами и следите за новостями! P.S. немного статистики

🍾133

14 Dec 2023, 07:22 UTC≈3,270 views3 reactionsread 7 August 2026

Статья на CodeMaze, в которой рассказывается, что такое AOT (Ahead of Time) Compilation, как использовать и использовать ли вообще: https://code-maze.com/blazor-webassembly-ahead-of-time-compilation/ @BlazorChannel #Blazor

👍3

5 Dec 2023, 05:42 UTC≈2,930 views7 reactionsread 7 August 2026

На .NET Conf 2023 показали проект eShop, который совмещает в себе различные технологии из мира .net, в том числе Blazor. 12 декабря в 21:00 (GMT+3) пройдёт ASP.NET Community Standup, где гости поговорят о проекте и ответят на вопросы. YouTube: https://www.youtube.com/watch?v=fkDSaIti_KU GitHub: https://github.com/dotnet/eShop @BlazorChannel #Blazor

👍5🤔2

27 Nov 2023, 11:14 UTC≈2,420 views6 reactionsread 7 August 2026

Думаю, что многие слышали про аббревиатуру TDD. Вашему вниманию вебинар на тему применения TDD при разработке проекта на Blazor: https://www.youtube.com/watch?v=aWY7R7Egm70 @BlazorChannel #Blazor

🥰3🔥1🤔1🤩1

15 Nov 2023, 07:17 UTC≈2,360 views11 reactionsread 7 August 2026

.NET 8 готов к установке: https://dotnet.microsoft.com/en-us/download/dotnet/8.0 Также прошёл первый день .NET Conf 2023. С 1:31:35 можно послушать Daniel Roth и Steve Sanderson, где они довольно быстро и подробно рассказывают об основных нововведениях в Blazor: https://www.youtube.com/watch?v=xEFO1sQ2bUc @BlazorChannel #Blazor

🔥72👍1😁1

10 Nov 2023, 08:16 UTC≈2,160 views14 reactionsread 7 August 2026

Вышел перевод книги "Blazor in action" от ДМК Пресс и сообщества DotNetRu. Подробности по процессу можно найти по ссылке (там же будет промокод на скидку): https://habr.com/ru/companies/jugru/articles/772646/ @BlazorChannel #Blazor

👍112🥰1

7 Nov 2023, 07:25 UTC≈1,770 views8 reactionsread 7 August 2026

В преддверии релиза новой версии .NET, предлагаем посмотреть на изменения Blazor WASM между .NET 7 и .NET 8: https://www.youtube.com/watch?v=2bEhiyqztwg @BlazorChannel #Blazor

👍51👎1👏1

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

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

“Blazor Community” (@BlazorChannel), 797 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/BlazorChannel.

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.