Not quite related to the editor itself, but still contributing to the glossary is a good thing to do. Who knows, maybe the glossary will be integrated into the editor one day?

Channel
.attheme editor blog
@atthemeeditor
On this record: Growth · Engagement · Posts · Citations · Cite this entry
97subscribers
-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 | -1001133608059 |
|---|---|
| Type | Channel |
| Username | @atthemeeditor |
| Created | Between 1 June 2017 and 21 July 2018— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/atthemeeditor |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 16:18 | 97 | -1 |
| 9 Aug 2026, 11:31 | 98 | no change |
| 6 Aug 2026, 18:34 | 98 | first reading |
Engagement
20 posts held, back to 21 July 2018 — 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 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 1 November 2019. An engagement rate over an empty window would be a number about nothing.
Recent posts
Hi everyone! We've already launched the new glossary website at attheme-glossary.snejugal.ru. The Russian glossary is almost moved to the new website, but we need your help with moving the English glossary. You can do it by contributing to the glossary database on GitLab. It isn't a hard thing to do: you only need to sign up for GitLab and use Web IDE to add new sections to the glossary. As the glossary is getting m…
Finally, .attheme editor has updated! The most noticable change is gradient support for wallpapers: you simply start editing chat_wallpaper, choose Gradient and you can set a gradient background for your theme! Other changes are: — The variable list is updated to the latest version of Telegram; — Scrolling theme tabs is now a bit smoother. Hope you like the update!
Hi, devs! I've just released attheme-js@3.0.0. It now has support for the new default themes, including the ability to choose the accent color for the Mono, Dark and Arctic themes. Also, you can now use Attheme#fallbackToOther to fallback a theme to another one, and Attheme#fallbackToSelf that allows you to map new variables to already existing ones. Oh, and you can pass any iterable over [string, Color] to the Atthe…
Finally, .attheme editor is released with new variables! Great thanks to @twitface for doing most of my work
FInally, .attheme editor is now available in Spanish! Thanks to @DiegoCanevaro for translation 👍
A brief update: .attheme editor has been updated with new variables for the poll attachment button. Also I've seen that more people are facing this bug. I swear I'll fix it this weekend 🙏
We've released a new version of .attheme editor to fix one bug. The bug is that opening themes with @atthemeeditorbot failed with an error. Now it works as good as always 😉 Just a reminder: whenever you face a red dialog saying ”Whops, an error happened”, you should report it to @snejugal or on our GitHub repository. That error always indicates a bug in the editor that must be fixed or properly handled by the editor…
Telegram v5.0 has come out, and .attheme editor is already up to date with new variables! But v5.0 not also brought new variables, but also deleted a bunch of old ones regarding colored headers. .attheme editor will show those as Removed since v5.0 so you can upgrade your themes more smoothly. attheme-js and attheme-rs are also updated to v2.1.4 and v0.2.0 respectively with support of the new variables. Note that a…
A brief update for developers of .attheme tools: First of all, we've written a Rust crate for working with .attheme files. Check it out! Second, we've rewritten attheme-js from scratch: now it has a better API and provides you with many tools you'll need when working with .attheme. It's been rewritten in TypeScript, and we now provide you typings so you can develop tools in TypeScript easier. Third, attheme-defaul…
I've updated .attheme editor with new variables that were added in the latest 4.9.1 update of Telegram. Go update your themes! Also attheme-default-values is updated, thanks to @twitface.
Update: we've fixed that bug and another one regarding this preview
Showing the 12 most recent of 20 posts we hold for @atthemeeditor. 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 — 194,725 of 1,183,361entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“.attheme editor blog” (@atthemeeditor), 97 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/atthemeeditor.
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.