Telegram RegisterThe public register of Telegram
Telegram profile photo for BIRDCC - English Channel

Channel

BIRDCC - English Channel

@birdcc

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

10subscribers

+1 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002313134747
TypeChannel
Username@birdcc
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live4 October 2026
Measurements held3
Confirmed unchanged5 times, most recently 4 October 2026
On Telegramt.me/birdcc

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 2 October 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

9109.58 August 2026 — 9 subscribers12 August 2026 — 9 subscribers24 August 2026 — 10 subscribers8 August 202624 August 2026
3 measurements spanning 16 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 9–10 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 09:2710+1
12 Aug 2026, 13:029no change
8 Aug 2026, 15:469first reading

Engagement

13 posts held, back to 7 August 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 13 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1100.0%

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 1 of the 13 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 7 August 2025 to 29 July 2026, 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

29 Jul 2026, 19:50 UTC8 viewsread 12 August 2026

We have now released BIRD.skills (Beta), an all-in-one Agent Skill, open-sourced under the MIT license. This Agent Skill can help you: //01 Guide your Agent to quickly set up the birdcc toolchain for your environment  //02 Guide your Agent to automatically install BIRD syntax highlighting plugins for your Vim/NeoVim; automatically install LSP plugins for your VSCode/VSCodium-Fork IDE //03 Guide your Agent to quic…

10 Jun 2026, 14:59 UTC18 viewsread 12 August 2026

Key recent updates to BIRD grammar https://github.com/bird-chinese-community/BIRD-tm-language-grammar/pull/12 Summary: Protocol Config Syntax CLI Output Samples Tests ──────── ───────────── ────────── ─────── ───── BGP ✅ ✅ ✅ ✅ OSPF ✅ ✅ ✅ ✅ RIP ✅ ✅ ✅ ✅ RADV ✅ …

26 Feb 2026, 13:59 UTC60 viewsread 12 August 2026

🕊 A Call to Action: Help Us Bring Native BIRD2 Syntax Highlighting to GitHub! 🎉 First, some great news: The BIRD2 syntax highlighting library that we maintain has been merged into the main branch of the Shiki repository (#149)! This means that countless mainstream frontend frameworks and platforms—such as VuePress, Vitepress, Astro, and Nuxt—now natively support BIRD2 Configuration code highlighting out-of-the-box…

26 Feb 2026, 13:56 UTC33 viewsread 12 August 2026

🎉 Great news! The BIRD2 syntax highlighting library that we maintain has been merged into the main branch of the Shiki repository (#149)! Shiki is currently one of the most popular frontend syntax highlighting libraries, powering syntax highlighting across countless frontend ecosystems, including Vue and React. Notable frontend frameworks and platforms currently leveraging Shiki under the hood for code highlightin…

7 Sept 2025, 04:34 UTC69 viewsread 12 August 2026

🪄 Introducing bird2-autotype: A Lightweight Tool for Auto-typing Declarations Are you troubled by the following warning while using the latest BIRD2 (v2.17+)? <WARN>: Inferring function foo return type from its return value: bool To address the function return type warnings introduced in BIRD 2.17+, we’ve developed a lightweight Python tool that automatically and batch-adds return type declarations to functions in…

8 Aug 2025, 11:38 UTCviews —

BIRDCC - English Channel pinned «👩‍💻 BIRD2 Conf Syntax Highlighting Now Available for Vim & Neovim! Following our releases of: - 👩‍💻 BIRD2 Conf for VSCode - 👩‍💻 BIRD2 Conf for JetBrains IDEA we’re excited to bring full syntax highlighting support for BIRD2 Conf to both 👩‍💻 Vim and 👩‍💻…»

8 Aug 2025, 11:38 UTC57 viewsread 12 August 2026

👩‍💻 BIRD2 Conf Syntax Highlighting Now Available for Vim & Neovim! Following our releases of: - 👩‍💻 BIRD2 Conf for VSCode - 👩‍💻 BIRD2 Conf for JetBrains IDEA we’re excited to bring full syntax highlighting support for BIRD2 Conf to both 👩‍💻 Vim and 👩‍💻 Neovim users. With this update, the BIRD2 Syntax Highlighting Rules Library (details) now covers all major development toolchains — enabling network engineers and …

7 Aug 2025, 07:21 UTC38 viewsread 12 August 2026
Photo

👩‍💻 Import BIRD Conf syntax highlighting support into Jetbrains series editors 1. Prepare the language pack a) Open this link ▸ Resources in the lower right corner ▸ Download the latest .vsix installation package b) Use a decompression tool to directly decompress this .vsix file. c) Open the unzipped directory and locate the directory containing package.json. Keep it for future reference. 2. Open in IntelliJ …

7 Aug 2025, 04:06 UTC19 viewsread 12 August 2026
Photo

• BIRD Conf for VSCode — 0.1.0 released! 🆕 Features: - Added support for C-style block comments (/* … */) “comment style switching” feature. - Added implementation of automatic indentation rules for curly brace blocks ({}) - Added mark recognition for code block ({ ... }) folding. - Enhanced support for VSCode's automatic indentation engine (onEnterRules & indentationRules) ♻️ Refactor: - Optimized recognition …

7 Aug 2025, 03:57 UTC13 viewsread 12 August 2026

• Recent Work Summary: - ✅ BIRD Conf for VSCode syntax highlighting plugin — https://t.me/birdcc/6 - 🔄 BIRD Conf for IDEA syntax highlighting plugin — in progress - 🔄 BIRD Conf for Neovim syntax highlighting plugin — planned

7 Aug 2025, 03:49 UTC14 views1 reactionsread 12 August 2026
Photo

🚀 Native Syntax Highlighting for BIRD2 is HERE! Tired of hacking Nginx highlighting for complex BIRD configs? We were too! 🎉 BIRD Chinese Community (BIRDCC) open-sources TextMate grammar for BIRD2, the core internet routing daemon! • What's new: • VSCode Extension LIVE on Marketplace & OpenVSX • PRs submitted to GitHub Linguist & Shiki for native support • How To Use: - 👩‍💻 VSCode: https://marketplace.visua…

👍1

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

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

“BIRDCC - English Channel” (@birdcc), 10 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/birdcc.

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.