Channel
@akashaProxy
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,689subscribers
+2 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002126701488 |
|---|---|
| Type | Channel |
| Username | @akashaProxy |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 August 2026 |
| Last confirmed live | 18 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 18 August 2026 |
| On Telegram | t.me/akashaProxy |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Aug 2026, 13:47 | 1,689 | +2 |
| 17 Aug 2026, 14:45 | 1,687 | first reading |
20 posts held, back to 1 January 2026 — 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 3 June 2026. An engagement rate over an empty window would be a number about nothing.
19 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 89.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 17 | 89.5% | |
| 👏 | 1 | 5.26% | |
| 🥰 | 1 | 5.26% |
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 9 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 19reactions 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 January 2026 to 3 June 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.
New push to github! Merge pull request #98 from akashaProxy/dependabot/npm_and_yarn/webui/next-16.2.1 build(deps): bump next from 16.1.7 to 16.2.7 in /webui by Elysia For more architecture see action See commit detail here
dependabot推的安全漏洞全是ndoejs爆的
New push to github! Merge pull request #100 from akashaProxy/dependabot/npm_and_yarn/webui/types/node-25.5.0 build(deps-dev): bump @types/node from 25.0.9 to 25.5.0 in /webui by Elysia For more architecture see action See commit detail here
❤1
New push to github! Merge pull request #96 from akashaProxy/dependabot/npm_and_yarn/webui/npm_and_yarn-d13e90860a build(deps): bump the npm_and_yarn group across 1 directory with 4 updates by Elysia For more architecture see action See commit detail here
刷机需谨慎，安全不能丢 https://mp.weixin.qq.com/s/wxjrfGUBI1LdjAoJ2HT4Ig
题外话：某cpe但高级工具的mihomo插件做的一坨大粪 第一次见到不让用自己配置文件的gui
发现大部分gui都有一个非常明显的问题： 擅自覆写用户的配置文件🤔甚至没法关
akashaProxy ci channel pinned «服务控制正在转向使用go编写 shell还是太难维护了（ 可以点个star吗»
服务控制正在转向使用go编写 shell还是太难维护了（ 可以点个star吗
❤7👏1
New push to github! Merge pull request #93 from akashaProxy/dependabot/npm_and_yarn/webui/types/node-25.0.9 Bump @types/node from 25.0.3 to 25.0.9 in /webui by Elysia For more architecture see action See commit detail here
🥰1
New push to github! Merge pull request #88 from akashaProxy/dependabot/npm_and_yarn/webui/mui/material-7.3.7 Bump @mui/material from 7.3.6 to 7.3.7 in /webui by Elysia For more architecture see action See commit detail here
New push to github! Merge pull request #95 from akashaProxy/dependabot/npm_and_yarn/webui/npm_and_yarn-a415b051ba Bump next from 16.1.1 to 16.1.5 in /webui in the npm_and_yarn group across 1 directory by Elysia For more architecture see action See commit detail here
Showing the 12 most recent of 20 posts we hold for @akashaProxy. 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 — 113,162 of 1,569,089entries 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.
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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 August 2026 — this entry's latest reading, not the date you are reading this.
“akashaProxy ci channel” (@akashaProxy), 1,689 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/akashaProxy.
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.