مرکز تخصصی شبکه و امنیت:هیواشبکه
شرکت هیوانوآوران داده گستر
آموزشگاه هیواشبکه
دوره های :
MCSA
CEH
security +
ISMS
TIA
مجازی سازی
استاندارد سازی اتاق سرور
01333550965
تبلیغ و تبادل: @HivaNetwork
http://Hiva-Network.com
کد ساماندهی: 1-4-61-696687-1-1
Created
Between 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 the other topics.
Growth
60 measurements spanning 92 days, net +79. 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 16,519–16,798 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)
Subscribers
Change
5 Nov 2026, 11:18
16,746
-11
4 Nov 2026, 12:25
16,757
-9
3 Nov 2026, 09:29
16,766
+33
2 Nov 2026, 09:06
16,733
+3
1 Nov 2026, 10:46
16,730
+26
31 Oct 2026, 09:36
16,704
-11
30 Oct 2026, 11:29
16,715
+2
29 Oct 2026, 11:41
16,713
+28
28 Oct 2026, 09:45
16,685
+8
27 Oct 2026, 09:46
16,677
+53
26 Oct 2026, 11:18
16,624
-16
25 Oct 2026, 13:14
16,640
-13
24 Oct 2026, 15:55
16,653
-9
23 Oct 2026, 12:36
16,662
-12
22 Oct 2026, 14:11
16,674
+17
21 Oct 2026, 09:20
16,657
-9
20 Oct 2026, 08:44
16,666
+20
19 Oct 2026, 10:49
16,646
-9
18 Oct 2026, 07:16
16,655
+10
17 Oct 2026, 06:16
16,645
first reading
Engagement
98 posts held, back to 25 July 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 68 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
3.03%
avg views ÷ 16,746 subscribers
Avg views / post
507
26 posts measured
Reaction rate
0.317%
reactions ÷ views · ER floor
Posts in window
26
of 98 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 19 of 26 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 5 November 2026
Posts held
98 (25 July 2026 – 5 November 2026)
Views total
13,192
Reactions total
32
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Nov 2026, 05:10 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
≈9,870
Videos
≈164
Links
≈7,490
Lifetime counters from Telegram’s own channel header, read 6 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
84 reactions across 47 posts, in 7 distinct kinds. The most used accounts for 66.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
56
66.7%
👍
15
17.9%
🔥
5
5.95%
😁
4
4.76%
🥰
2
2.38%
👏
1
1.19%
🤔
1
1.19%
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 50 of the 98 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 84 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 98 most recent posts we hold, published 25 July 2026 to 5 November 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
Telegram’s own ‘edited’ marker: 0 of 26 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🌐 نقش DNS در ارتباط کلاینت با Active Directory
یکی از دلایل رایج خطا هنگام Join کردن سیستمها به Domain، تنظیم نادرست DNS در کلاینت است. برخلاف تصور بعضی کاربران، برای اتصال به Active Directory صرفاً داشتن ارتباط شبکهای با سرور کافی نیست؛ کلاینت باید بتواند سرویسها و آدرسهای موردنیاز Domain Controller را از طریق DNS پیدا کند.
🔍 نکته فنی که باید بررسی کنید:
در زمان Join شدن به Domain، کلاینت از رکوردهای SRV برای…
✴️ آشنایی با کریو کنترلر :
هر مجموعه ای با هر تعدادی کلاینت ، نیاز به ابزاری برای کنترل ترافیک ورودی و خروجی دارند ، ابزاری بسیار ساده که به عنوان فایروال ، روتر ، سیستم تشخیص و پیش گیری از نفوذ IPS ، آنتی ویروس ، VPN ، ابزاری برای اکانتینگ و مدیریت محتوای ارسالی و دریافتی در شبکه ( content filtering ) مورد استفاده قرار میگیرد. در ادامه بیشتر با کریو کنترلر آشنا می شوید.
🚩 مطالعه مطلب:
👇👇
https://b2n.ir/u68192
با…
🔐 Zero Trust؛ چرا نباید به کاربران داخل شبکه هم اعتماد پیشفرض داشته باشیم؟
در مدلهای امنیتی سنتی، معمولاً کاربران و دستگاههایی که به شبکه داخلی سازمان متصل هستند، قابل اعتماد فرض میشوند. اما این رویکرد میتواند یک نقطه ضعف جدی ایجاد کند؛ زیرا اگر حساب کاربری یکی از کارکنان به خطر بیفتد، مهاجم ممکن است از همان دسترسی برای نفوذ به بخشهای دیگر شبکه استفاده کند.
مدل Zero Trust بر یک اصل ساده اما مهم تأکید دارد:
«…
🔥 نکته تخصصی در مدیریت فایروال: ترتیب Ruleها را دستکم نگیرید!
در بسیاری از فایروالها، قوانین امنیتی بهترتیب بررسی میشوند و با منطبق شدن ترافیک با اولین Rule، تصمیم مربوط به آن اجرا میشود. به همین دلیل، حتی اگر قوانین امنیتی درستی تعریف کرده باشید، چیدمان اشتباه آنها میتواند نتیجهای کاملاً متفاوت ایجاد کند.
🔍 یک مثال کاربردی:
فرض کنید یک Rule عمومی برای اجازه دسترسی (Allow) در بالای یک Rule محدودکننده (Deny…
🚀 فیبر نوری چیست؟ کاربرد، انواع، نصب و اتصالات فیبر نوری
آیا میدانید تفاوت اصلی کابلهای Indoor و Outdoor در چیست؟ یا چرا در پروژههای زیرزمینی نباید از کابلهای معمولی استفاده کرد؟
در مقاله جدید سایت هیو نتورک، از انواع کابلها گرفته تا نکات حیاتی در نصب و سربندی (Termination) را بررسی کردهایم.
✅ مناسب برای مهندسان شبکه و طراحان زیرساخت
🔗 مشاهده مقاله
با هیوا باشید:😊🌷
👇👇
@Hivashabake
🌐 یک نکته مهم در عیبیابی شبکه: MAC Address Flapping
یکی از نشانههای مهم بروز مشکل در لایه دوم شبکه (Layer 2)، مشاهده جابهجایی مکرر یک MAC Address بین پورتهای مختلف سوئیچ است.
در چنین شرایطی، سوئیچ نمیتواند مسیر ثابتی برای ارسال ترافیک به دستگاه موردنظر داشته باشد؛ زیرا جدول MAC Address آن مرتباً بهروزرسانی میشود.
🔍 نکته تخصصی در عیبیابی:
اگر با پیامهای MAC Flapping در لاگ سوئیچ مواجه شدید، بهتر است پیش ا…
✴️ مجازی سازی دسکتاپ چیست؟
👈👈مجازی سازی دسکتاپ روشی برای شبیه سازی یک سیستم کاری کاربر است تا بتواند از طریق یک دستگاه متصل از راه دور به آن دسترسی داشته باشد. با ایجاد یک دسکتاپ مجازی برای کاربر، سازمانها میتوانند به کاربران اجازه دهند تقریباً از هر نقطه با اتصال شبکه، با استفاده از هر لپتاپ، تبلت یا گوشی هوشمند برای دسترسی به منابع سازمانی بدون توجه به دستگاه یا سیستم عاملی که توسط کاربر راه دور استفاده میشود،…
🖥️ نکته تخصصی درباره مدیریت Snapshot در VMware
یکی از اشتباهات رایج در مدیریت زیرساختهای مجازی، باقی گذاشتن Snapshotها برای مدت طولانی است. بسیاری تصور میکنند Snapshot فقط یک نسخه از وضعیت ماشین مجازی است؛ اما در واقع، پس از ایجاد آن، تغییرات جدید در فایلهای Delta ذخیره میشوند و این فایلها بهمرور میتوانند حجم قابلتوجهی پیدا کنند.
🔍 چرا باید Snapshotها را مدیریت کنیم؟
- افزایش حجم فایلهای Delta میتواند فضا…
🔒 چکلیست امنسازی فایروال: قلب امنیت شبکه! 🛡
فایروال شما خط اول دفاع شبکه است! با چکلیست امنسازی فایروال از هیواشبکه، شبکهتان را در برابر تهدیدات ایمن کنید:
✅ بهروزرسانی و بکاپ منظم
✅ مدیریت دسترسی و احراز هویت قوی
✅ پیکربندی دقیق قوانین و حذف پورتهای غیرضروری
✅ مانیتورینگ و لاگبرداری برای شناسایی سریع تهدیدات
✅ تست و آموزش مداوم
🚀 چرا مهم است؟
یک فایروال امن، کلید محافظت از شبکه در برابر هکرها و حملات سایب…
🖥️ نکته فنی درباره تنظیمات RAID در سرورهای HPE
انتخاب بین Write Through و Write Back فقط یک تنظیم ساده برای افزایش سرعت نیست؛ بلکه مستقیماً با عملکرد، پایداری و امنیت اطلاعات سرور ارتباط دارد.
در حالت Write Back، کنترلر برای افزایش سرعت، ابتدا اطلاعات را در حافظه کش ذخیره میکند و سپس آنها را روی دیسک مینویسد. به همین دلیل، در بارهای کاری سنگین مانند دیتابیسها و سیستمهای پرتراکنش، میتواند تأثیر چشمگیری بر عملک…
✅ آشنایی با (Zero Trust Network Access (ZTNA
⭐️زیرو تراست Zero Trust یک الگوی امنیتی شبکه است که بدون توجه مکان، به هیچ کس اعتماد ندارد. نمی توان اعتماد را براساس این که کاربر “داخل” یا “خارج” از شبکه است ایجاد کرد. هر کاربر ،قبل و در حین یک ارتباط بررسی می شود. در ادامه بیشتر با آن آشنا شوید.
🚩 مطالعه مطلب:
👇👇
https://b2n.ir/m56995
با هیوا باشید:😊🌷
👇👇
@Hivashabake
🎥آموزش های ویدئویی
🔴 چگونه با Event Viewer زمان نصب و حذف برنامه ها را ببینیم؟
😊👈 همانطور که می دانید با استفاده از event viewer می توانید لاگ های سیستم را مشاهده کنید شاید برای شما جالب باشد که بخواهید بدانید چه کسی برنامه ای را در سیستم نصب و یا حذف کرده است و تاریخ آن چه زمانی بوده کافیست لاگ های مربوط به سرویس msinstaller را که وظیفه ی نصب و حذف برنامه های ویندوز را برعهده دارد بررسی کنیم
https://www.aparat.…
Showing the 12 most recent of 98 posts we hold for @Hivashabake. 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.
Posts edited after publishing
@Hivashabake edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
15 August 2026
Most recent edit
15 August 2026
Posts recorded as deleted after publishing
We recorded 17 posts on @Hivashabake as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
7 August 2026
Most recent seen missing
3 November 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
3
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 142 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
Handles this channel named that no longer answer
Dead references
7
handles named in this channel’s posts, vacant today
Evidenced gone
5
we ourselves saw one of these resolve, at some point
Never seen alive
2
vacant every time we have ever looked
@Hivashabake named 7 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@farsii_film named in 1 post, 2 September 2026 – 2 September 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@templates_wp named in 1 post, 2 September 2026 – 2 September 2026 · confirmed gone 21 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@farilensari named in 1 post, 2 September 2026 – 2 September 2026 · confirmed gone 27 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@karyabi_pooool named in 1 post, 2 September 2026 – 2 September 2026 · confirmed gone 3 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@proghe_eda named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 3 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@hivashabke named in 2 posts, 6 November 2026 – 6 November 2026
@hivashabak named in 1 post, 4 November 2026 – 4 November 2026
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.
مهندس سلام | HiEng.ir @hieng · 31,136 Telegram ranks this channel #11 of 84 here — alongside 83 others — read 6 September 2026
آموزش شبكه و امنيت @denait · 21,066 Telegram ranks this channel #12 of 79 here — alongside 78 others — read 24 September 2026
Computer Software @Software_computerr · 40,998 Telegram ranks this channel #18 of 73 here — alongside 72 others — read 29 August 2026
آموزش کامپیوتر @amuzesh_computer · 41,280 Telegram ranks this channel #24 of 79 here — alongside 78 others — read 29 August 2026
شبکه کاران @shabake_karan · 25,607 Telegram ranks this channel #25 of 82 here — alongside 81 others — read 14 September 2026
‹ NetWork & Security › @DrSecCom · 37,737 Telegram ranks this channel #25 of 50 here — alongside 49 others — read 1 September 2026
Computer Engineers @VIP30T · 19,643 Telegram ranks this channel #27 of 67 here — alongside 66 others — read 30 September 2026
شبکه و امنیت،تکنولوژی،هوش مصنوعی @Netwo0rk · 53,838 Telegram ranks this channel #27 of 63 here — alongside 62 others — read 24 August 2026
مای سکیور | Mysecure @mysecure1 · 29,449 Telegram ranks this channel #30 of 73 here — alongside 72 others — read 7 September 2026
Computer Help @P30_H3LP · 24,862 Telegram ranks this channel #33 of 76 here — alongside 75 others — read 14 September 2026
خانه موبایل و کامپیوتر @PcAndMob · 23,900 Telegram ranks this channel #40 of 73 here — alongside 72 others — read 15 September 2026
Black Security Team @Black_Security · 64,027 Telegram ranks this channel #44 of 64 here — alongside 63 others — read 21 August 2026
کالی بویز | ترفند | تکنولوژی @Kaliboys · 28,535 Telegram ranks this channel #48 of 77 here — alongside 76 others — read 9 September 2026
Computer & IT Engineering @Computer_IT_Engineering · 189,542 Telegram ranks this channel #52 of 76 here — alongside 75 others — read 11 August 2026
🇮🇷 سامانه استخدام جو @irankaryab · 23,037 Telegram ranks this channel #55 of 77 here — alongside 76 others — read 18 September 2026
آموزش انگلیسی به روش زبان مادری @hamidrezasotoudeh98 · 74,788 Telegram ranks this channel #55 of 89 here — alongside 88 others — read 20 August 2026
کافه مهندس @cofeeng · 112,492 Telegram ranks this channel #56 of 76 here — alongside 75 others — read 14 August 2026
برنامه نویسی | پایتون @Pythoni_Developers · 75,380 Telegram ranks this channel #59 of 82 here — alongside 81 others — read 19 August 2026
مرکز آموزش کامپیوتر @AmoozeshWebsite · 96,853 Telegram ranks this channel #63 of 75 here — alongside 74 others — read 16 August 2026
Android Developers @Android0to100 · 62,316 Telegram ranks this channel #64 of 65 here — alongside 64 others — read 22 August 2026
Learn Python @learnpy · 21,294 Telegram ranks this channel #66 of 90 here — alongside 89 others — read 23 September 2026
برنامه نویسی | Programming @Azad_Developers · 37,476 Telegram ranks this channel #66 of 88 here — alongside 87 others — read 31 August 2026
ژورنال آکادمیک @journalacademic · 26,544 Telegram ranks this channel #70 of 78 here — alongside 77 others — read 12 September 2026
کتابخانه مهندسی کامپیوتر و پایتون @programmers_street · 30,906 Telegram ranks this channel #74 of 87 here — alongside 86 others — read 6 September 2026
This channel appears in 30 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 5 November 2026 — this
entry's latest reading, not the date you are reading this.
“Hiva Network” (@Hivashabake), 16,746 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/Hivashabake.
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.