Hacking & security — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 84% 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.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Content that also appears on other registered channels
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Matching posts — open both and compare (2 of the pairs behind the counts below)
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 15 comparable posts for this entry, running 14 June 2020 to 31 August 2020. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Across the whole group of 2, the earliest publisher we hold is @alsaqqaftechnology — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
2 measurements taken within a single day. 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 730–732 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
6 Aug 2026, 17:18
731
no change
6 Aug 2026, 17:08
731
first reading
Engagement
20 posts held, back to 14 June 2020 — 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 22 June 2021. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
64
Videos
3
Links
159
Lifetime counters from Telegram’s own channel header, read 6 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.
كتاب pdf يشرح عن اهم البروتوكولات في عالم الانترنت وكيف تعمل ومافائرتها واختصاراتها استفدت انا منه بشكل كبير جدا بالتوفيق
▁▂▃▄▅▆▇█▇▆▅▄▃▂▁
⌘⇩للمزيد انضم إلينا على التيليجرام⌘⇩
➪ t.me/ERROR404VIGITAMHS
#لا_للاحتكار
#اذكر_المصدر
#شارك_ليستفيد_غيرك
#اترك_القول_وابدا_بالعمل
#انا_لست_هاكر
#انا_لست_مبرمج
▁▂▃▄▅▆▇█▇▆▅▄▃▂▁
🎲 - جيماكسوسبلويت 1.0.3 :
- أداه إختراق أجهزه الأندرويد البديل الأفضل من الميتاسبلويت و غيرها، تمت برمجتها بالكامل من قبل مبرمج و مختبر إختراق يمني - *جميع الحقوق محفوظه*
- المميزات:
١. واجهه رسومية سهله الإستخدام حيث انها تعرض كل العمليه عبر المتصفح ليس الترموكس أو منفذ الأوامر لكي تخلق بيئه سهله في التعامل ولا تحتاج لأي معلومه في البرمجه أو الإختراق.
٢. يمكنك الوصول لأجهزه الضحايا بسرعه حتى و إن كانو غير متصل…
🎲 - الداله add في البايثون ماهي وكيف تستخدم :
اذا قمنا بعمل set ونريد اضافه شيء بداخلها فنقوم باستخدام هذه الداله ولكن كيف ؟
لنعطي مثال :
لدينا متغيير اسمه E وبداخله set محتواها
@VIGITAMHS نقوم بعملها بهذا الشكل
E = {'@VIGITAMHS'}
الان نريد اضافه إلى هذه ال set مثلا
MR_AT
مقوم بكتابه المتغيير المراد الاضافه اليه ثم نقوم بوضع نقطه ثم نقوم بوضع الداله add ثم نقوم بتفح قوسين وبداخل هذه الاقواس قم باضافه الذي تريد…
🌪 - الداله union في البايثون ماهي وكيف تستخدم :
🎲 - هذي الداله تقوم بدمك بين اثنين set واذا كان كل set بمكان فهذه الداله تقوم بدمجهم لنعطي مثال :
لدينا متغير باسم E وبداخله ERROR و 404 سيكون ال set بهذا الشكل
E = {'ERROR',404}
ولدينا متغيير اخر باسم R وبداخله VIGITA و MHS وسيكون بهذا الشكل
R = {'VIGITA','MHS'}
الان شاهد كود الدمج :
print (E.union(R))
🎭 - قمنا اولا بطباعه المتغيير E ثم قمنا بوضع نقطه ثم قمنا ب…
- دورتين على اليويتوب لتعلم قواعد البيانات بواسطه البايثون🎲 :
https://www.youtube.com/playlist?list=PLMYF6NkLrdN81QmQL5Eur5xrEcqtKkDtK
https://www.youtube.com/playlist?list=PLyWZPIXpx03k2c2s3RoSy8Pu0NuUuvMGF
🎲 - كود ☰ ماذا يعني ؟
تاتي اكواد بهذا الشكل في المواقع لان بعض النصوص لا تقبلها المواقع فمثلا الكود الذي في الاعلى اذا اضفته على html فانه سيقوم بعمل نص على شكل القائمه الجانبيه واذا غيرت الارقام ستتغير عده اشكل وهكذا🎃
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Showing the 12 most recent of 20 posts we hold for @alsaqqaftechnology. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 14 June 2020 to 22 June 2021. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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
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.
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 6 August 2026 — this
entry's latest reading, not the date you are reading this.
“programming&HACKER” (@alsaqqaftechnology), 731 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/alsaqqaftechnology.
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.
