Telegram RegisterThe public register of Telegram

Channel

Hiddify

@hiddify

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry

123,175subscribers

+29 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001510827498
TypeChannel
Username@hiddify
DescriptionHiddify, Internet Freedom Solution Supporting: 🎯 xHTTP 🎯 HTTPUpgrade 🎯 Shadowsocks 2022 🎯 Wireguard 🎯 Reality 🎯 TUIC 5 🎯 Hysteria 2 🎯 Auto CDN 🎯 Trojan 🎯 VLess 🎯 Vmess 🎯 MTProto 🆘 @hiddify_board 🧑🏼‍🏫 @hiddify_teacher
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held8
Confirmed unchanged2 times, most recently 12 August 2026
On Telegramt.me/hiddify

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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

123,143123,204123,173.55 August 2026 — 123,146 subscribers6 August 2026 — 123,146 subscribers6 August 2026 — 123,148 subscribers7 August 2026 — 123,143 subscribers8 August 2026 — 123,150 subscribers9 August 2026 — 123,181 subscribers10 August 2026 — 123,204 subscribers11 August 2026 — 123,175 subscribers123,1755 August 202611 August 2026
8 measurements spanning 5 days, net +29. 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 123,134–123,213 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 08:48123,175-29
10 Aug 2026, 06:51123,204+23
9 Aug 2026, 09:53123,181+31
8 Aug 2026, 08:36123,150+7
7 Aug 2026, 07:31123,143-5
6 Aug 2026, 10:30123,148+2
6 Aug 2026, 01:32123,146no change
5 Aug 2026, 22:01123,146first reading

Engagement

20 posts held, back to 20 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof 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 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
120
Videos
10
Links
187

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

5,519 reactions across 20 posts, in 18 distinct kinds. The most used accounts for 71.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3,94871.5%
🔥4448.04%
👍3326.02%
🤔2474.48%
❤‍🔥971.76%
🏆931.69%
👌771.40%
🆒500.906%
👏420.761%
🙏410.743%
👀350.634%
🕊350.634%
😍300.544%
150.272%
😱130.236%
🤩80.145%
🤝70.127%
🥰50.091%

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 5,519reactions 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 20 February 2026 to 1 April 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.

Telegram Stars

Stars received
245
across the posts below
Posts paid on
20
of 20 we hold a reading for · 100%
Most on one post
61
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @hiddify. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 20 February 2026 to 1 April 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

1 Apr 2026, 21:28 UTC≈191,000 views831 reactions8 Starsread 12 August 2026

یه آپدیت جالبی روی vaydns دادیم و روی هیدیفای هم آوردیمش اینجوری هست که برای هر کانکشن دیگه میتونه از چندین dns استفاده کنه و حتی چک میکنه که اگه dns قطع شد از بقیه استفاده کنه و یک لودبالانس خیلی جالبی شد همینطور یک scanner خیلی خوب هم اضافه شد که خودکار واقعی چک میکنه که dns وصل هست و تو حافظه اش نگه میداره و هر بار که متصل میشه اتومات ازش استفاده میکنه برای این منظور کافیه resolve=auto را به لینک اضافه کنید اگه

640👍78🔥55🙏41😍17

5 Mar 2026, 18:16 UTC≈195,000 views452 reactions55 Starsread 12 August 2026

توضیحات مهم در خصوص dnstt پهنای باند dns بسیار پایین هست پس بهتره تا جای ممکن سربار کم بشه هرچی ساده تر بهتر socks+dnstt ساده ترین پروتکل هست هیچ نیازی به رمزنگاری پیچیده تر نیست خود dnstt رمزشده میفرسته و دیتاها امن خواهد بود در عین حال اگر اصرار به استفاده از لایه انتقال دیگری هستید میتوانید انجام دهید ‍‍‍ ssh://.... -> dnstt:// در هیدیفای میتوانید چندین لینک بفرستید تا اتوماتیک اونی که وصل میشه را انتخاب ک

276❤‍🔥81🤔56👍24🆒15

5 Mar 2026, 17:30 UTC≈176,000 views185 reactions2 Starsread 12 August 2026

مشکل گیتهاب حل شد نسخه دسکتاپ و موبایل https://github.com/hiddify/hiddify-app/releases

122🤔18👍16🔥15👀14

5 Mar 2026, 17:06 UTC≈176,000 views271 reactions4 Starsread 12 August 2026
File

نسخه ویندوز

197👍31🤔28😱12🔥3

5 Mar 2026, 16:54 UTC≈173,000 views325 reactions2 Starsread 12 August 2026
File

گیتهاب مشکل پیدا کرده فعلا این نسخه اندروید را داشته باشید

214🤔52🆒28❤‍🔥1615

5 Mar 2026, 15:36 UTC≈153,000 views134 reactions2 Starsread 12 August 2026

رویکرد ما استقلال کلیه ابزارها هست و در تلاشیم تمامی ابزارها مثل یک ماژول ساده در جاهای مختلف استفاده بشه هر پنلی دارید در داخل ایران میتوانید اوتباند را ساکس ست کنید و از کور هیدیفای مثل نمونه کانفیگ زیر استفاده کنید https://github.com/hiddify/hiddify-app/tree/main/test.configs/dnstt

66🔥42👍11🤔10🥰5

5 Mar 2026, 14:27 UTC≈133,000 views264 reactions8 Starsread 12 August 2026

نسخه ۴.۱.۰ هیدیفای منتشر شد 🎉 در این نسخه تلاش کرده‌ایم سرعت DNSTT را افزایش دهیم. با اضافه شدن چندین worker، در تست‌های سرعت توانستیم به حدود ۴ مگابیت بر ثانیه برسیم. البته به نظر می‌رسد ظرفیت بالاتری هم وجود دارد؛ چون هر اتصال از یک تونل جداگانه عبور می‌کند و در صورت استفاده از resolverهای بیشتر و workerهای بیشتر، احتمالاً سرعت بالاتری نیز قابل دستیابی خواهد بود. ⸻ 📥 دانلود نسخه اپلیکیشن (موبایل و دسکتاپ) مشکلا

206🤔24👀21🤝7👏6

24 Feb 2026, 05:01 UTC≈120,000 views224 reactions2 Starsread 12 August 2026

🔐 What is the Mieru protocol? It is a modern and advanced protocol that can be considered the new generation and evolved form of Shadowsocks. This protocol is designed with the goal of increasing stability, security, and reducing detectability, and it uses techniques such as advanced multiplexing, flow control, random padding, and time-dependent keys ⏱️. These mechanisms cause the traffic to appear more natural and

161🕊26🏆18🔥10😍9

24 Feb 2026, 04:58 UTC≈96,500 views188 reactions1 Starread 12 August 2026

🔐 پروتکل Mieru چیست؟ یک پروتکل مدرن و پیشرفته است که می‌توان آن را نسل جدید و تکامل‌یافته‌ی Shadowsocks دانست. این پروتکل با هدف افزایش پایداری، امنیت و کاهش قابلیت شناسایی طراحی شده و از تکنیک‌هایی مانند multiplexing پیشرفته، flow control، padding تصادفی و کلیدهای وابسته به زمان ⏱️ استفاده می‌کند. این مکانیزم‌ها باعث می‌شوند ترافیک طبیعی‌تر به نظر برسد و fingerprint کردن آن بسیار دشوارتر شود 🕵️‍♂️ یکی از قابلیت‌ها

144🔥15👍11🏆9🕊9

22 Feb 2026, 17:42 UTC≈85,500 views180 reactions4 Starsread 12 August 2026

⚙️ Which protocols should we enable in Hiddify Manager? Considering that Hiddify Manager supports a wide variety of protocols, at first glance it may seem logical to enable multiple protocols for each connection model. However, in practice, the best and most stable approach is to enable only one appropriate protocol for each connection model. 📌 This means for each of these modes, you should have only one selection:

132👍28🤔12🔥7😱1

22 Feb 2026, 17:35 UTC≈64,300 views206 reactions2 Starsread 12 August 2026

⚙️ چه پروتکل‌هایی را در هیدیفای‌منیجر فعال کنیم؟ با توجه به اینکه هیدیفای‌منیجر از پروتکل‌های متنوعی پشتیبانی می‌کند، ممکن است در نگاه اول فعال کردن چندین پروتکل برای هر مدل اتصال منطقی به نظر برسد. اما در عمل، بهترین و پایدارترین روش این است که برای هر مدل اتصال، فقط یک پروتکل مناسب را فعال کنید. 📌 یعنی برای هر یک از این حالت‌ها، فقط یک انتخاب داشته باشید: • Direct (دایرکت) • Relay (میانی) • CDN این کار باعث می‌ش

176🔥12👍7🤔7🏆4

22 Feb 2026, 13:30 UTC≈57,200 views149 reactions3 Starsread 12 August 2026

🌟 What is the Naive protocol? 🤔 The Naive protocol is a TLS-based method that exactly mimics the behavior of the Google Chrome browser 🌐 Unlike other protocols that use Go’s TLS system ⚙️, Naive uses Chrome’s actual TLS library 🖥️ Main goal: hiding traffic and preventing detection by DPI or smart filters 🔒 ⸻ ⚡ Why is UTLS not enough? ⚠️ 🔸 The UTLS library is a Go library that attempts to simulate browser TLS fi

60👌56🔥19👍13👏1

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 89,673 of 1,151,006entries 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.

Mentions

Named by 5 registered channels — 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.

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.

Appears in Telegram’s recommendations for other channels

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.

Outline VPN Official
@OutlineVpnOfficial · 223,478
Telegram ranks this channel #5 of 55 here — alongside 54 others — read 11 August 2026
فیلترشکن - VPN
@AzadNet · 254,440
Telegram ranks this channel #7 of 60 here — alongside 59 others — read 10 August 2026
بشکن Beshkan
@beshkan · 278,301
Telegram ranks this channel #9 of 87 here — alongside 86 others — read 10 August 2026
VPN CLUB
@wbnet · 230,462
Telegram ranks this channel #10 of 70 here — alongside 69 others — read 11 August 2026
DJ_MRMX
@DJ_MRMX · 350,525
Telegram ranks this channel #85 of 92 here — alongside 91 others — read 10 August 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Hiddify” (@hiddify), 123,175 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/hiddify.

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.