Channel
@barrasihayetarikhi
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Cite this entry
964subscribers
+3 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001065132223 |
|---|---|
| Type | Channel |
| Username | @barrasihayetarikhi |
| Created | 5 July 2016 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/barrasihayetarikhi |
Other / unclassifiable — 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 98% 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.
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.
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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @barrasihayetarikhi/1070 · this entry30 Nov 2017, 01:35 UTC | @agenda/711 Dec 2017, 04:28 UTC | 1.00 | 11 days |
| @barrasihayetarikhi/1071 · this entry1 Dec 2017, 10:55 UTC | @agenda/913 Dec 2017, 23:03 UTC | 1.00 | 13 days |
| @barrasihayetarikhi/1072 · this entry2 Dec 2017, 18:44 UTC | @agenda/1014 Dec 2017, 21:58 UTC | 1.00 | 12 days |
| @barrasihayetarikhi/1073 · this entry10 Dec 2017, 20:44 UTC | @agenda/1322 Dec 2017, 06:59 UTC | 1.00 | 11 days |
| @barrasihayetarikhi/1075 · this entry20 Dec 2017, 03:08 UTC | @agenda/1631 Dec 2017, 17:14 UTC | 1.00 | 12 days |
| @barrasihayetarikhi/1077 · this entry22 Dec 2017, 21:47 UTC | @agenda/183 Jan 2018, 10:23 UTC | 1.00 | 12 days |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @agenda | 6 (6/6 hand-verifiable sample passed) | 1.00 | 12 days | this entry (6–0) |
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 18 comparable posts for this entry, running 24 June 2017 to 22 December 2017. 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.
Across the whole group of 2, the earliest publisher we hold is @barrasihayetarikhi — 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.
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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 21:28 | 964 | +3 |
| 6 Aug 2026, 13:37 | 961 | no change |
| 5 Aug 2026, 23:26 | 961 | first reading |
20 posts held, back to 23 June 2017 — 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 December 2017. An engagement rate over an empty window would be a number about nothing.
The account of the user that created this channel has been inactive for the last 5 months. If the account of the creator remains inactive in the next 7 days, it will be self-destructed and the channel will lose its creator.
The account of the user that created this channel has been inactive for the last 5 months. If the account of the creator remains inactive in the next 8 days, it will be self-destructed and the channel will lose its creator.
The account of the user that created this channel has been inactive for the last 5 months. If the account of the creator remains inactive in the next 10 days, it will be self-destructed and the channel will lose its creator.
The account of the user that created this channel has been inactive for the last 5 months. If the account of the creator remains inactive in the next 17 days, it will be self-destructed and the channel will lose its creator.
The account of the user that created this channel has been inactive for the last 5 months. If the account of the creator remains inactive in the next 19 days, it will be self-destructed and the channel will lose its creator.
The account of the user that created this channel has been inactive for the last 5 months. If the account of the creator remains inactive in the next 27 days, it will be self-destructed and the channel will lose its creator.
The account of the user that created this channel has been inactive for the last 5 months. If the account of the creator remains inactive in the next 28 days, it will be self-destructed and the channel will lose its creator.
The account of the user that created this channel has been inactive for the last 5 months. If the account of the creator remains inactive in the next 30 days, it will be self-destructed and the channel will lose its creator.
چرا باید زرین کوب خواند؟ برخلاف مرحوم دکتر زریاب که در دائره المعارف چند سالی با ایشان مراوده داشتم و از خدمت آن استاد گرانمایه بهره می بردم من با مرحوم زرین کوب ارتباطی شخصی نداشتم، جز چند باری و آن هم زمانی که اواخر عمر استاد هفته ای شاید یک روز به مرکز می آمد. با این وصف من خود را شاگرد آثار مکتوب استاد زرین کوب می دانم. درست به خاطر نمی آورم از کی اما نیک می دانم نخستین کتابی که از آن مرحوم خواندم کتاب فرار از م…
... جزئیات این بحث ها را در کتاب خودم درباره تدوین حدیث نوشته ام. آنچه تاکنون درباره حدیث از نویسنده این سطور به شکل پراکنده در تمام این سال ها چاپ شده محصولات پژوهشی است دراز دامن که برای تدوین این کتاب در طی سال های گذشته سامان داده ام. با وجود آنچه گفتم این البته نافی وجود شماری از تحریفات و یا تغییرات شکلی و یا محتوایی بسیار اندک در کتاب کافی و یا نسخه های اولیه آن نیست. به ویژه اینکه چنانکه در آن کتاب نوشته ام…
دوازده نکته درباره اصالت كتاب كافي مقاله اي را امروز دوستي فرستاد درباره تشکیک در اصالت كتاب كافي نوشته آقايي كه از نوشته اش پیدا است اهل اطلاع نیست. من معمولاً قصد پاسخگویی به هر نوشته ای را ندارم. اینجا به این نوشته پاسخ می دهم چرا که بحث مربوط است به اصالت کتاب کافی که مهمترین کتاب شیعه امامیه است. نویسنده بر اساس چاپ دار الحدیث قم از کتاب کافی این بحث را مطرح کرده که بخش بسیار زیادی از احادیث کتاب کافی در سه کت…
(ادامه از پست قبلی...) وانگهی کتاب هایی که از دوره قبل از سده یازدهم داریم از کافی نقل حدیث می کنند. طبیعی است که مجموع این نقل ها همه کتاب احادیث کتاب کافی را پوشش نمی دهد اما این به معنای عدم اصالت احادیثی نیست که در کافی نقل شده اما در منابعی مانند ابن طاوس و یا علامه نقل نشده اند. فرض اینکه تمام و یا قسمت زیادی از این احادیث دسته دوم را عده ای در فاصله میان علامه و شهید اول و سده یازدهم ساخته و در نسخه های مختلف …
Showing the 12 most recent of 20 posts we hold for @barrasihayetarikhi. 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“حسن انصاری” (@barrasihayetarikhi), 964 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/barrasihayetarikhi.
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.