Channel

Ꮺ ∘ ᏚᎬᎬᏀᏌᏒᎬ ϲσɳƒ + ɗᥲiᥣy

@SeeGure_cf

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry

330subscribers

+15 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID	-1003855593448
Type	Channel
Username	@SeeGure_cf
Created	Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	6 August 2026
Last confirmed live	13 August 2026
Measurements held	3
Confirmed unchanged	1 time, most recently 13 August 2026
On Telegram	t.me/SeeGure_cf

Topic

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 92% 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.

No sample pairs were kept for this entry. The counts below were measured, but without the pairs there is nothing here for you to open and check, so treat the relationship as recorded rather than demonstrated.

Every channel this entry shares post bodies with
Channel	Matching posts	Text overlap	Typical gap	Published first
@glitchconf	9 (8/8 hand-verifiable sample passed)	1.00	9.8 hours	@glitchconf (9–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. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 19 comparable posts for this entry, running 5 August 2026 to 6 August 2026. 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 @glitchconf. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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.

𝙂𝙡𝙞𝙩𝙘𝙝! 𝘾𝙤𝙣𝙛𝙚𝙨𝙨𝙞𝙤𝙣
@glitchconf · Channel1,305 subscribers

Growth

3 measurements spanning 7 days, net +15. 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 313–332 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
13 Aug 2026, 09:13	330	+15
6 Aug 2026, 22:17	315	no change
6 Aug 2026, 12:19	315	first reading

Engagement

20 posts held, back to 5 August 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.

ERR · 30 days: 7.53%; avg views ÷ 330 subscribers
Avg views / post: 24.9; 20 posts measured
Reaction rate: —; this channel exposes no reaction counts
Posts in window: 20; of 20 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.

What these figures were computed from
Window	Rolling 30 days · latest post in window 6 August 2026
Posts held	20 (5 August 2026 – 6 August 2026)
Views total	497
Reactions total	—
Forwards / comments	not exposed by the public surface — not measured, not estimated
Readings taken	6 Aug 2026, 22:17 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.

Recent posts

6 Aug 2026, 16:03 UTC17 viewsread 6 August 2026

Photo

🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🤩 — очᴇнь бᴇᴄяᴛ ᴛᴇ ᴄᴀʍыᴇ ᴩᴀндоʍы ᴋоᴛоᴩыᴇ ᴛоᴧьᴋо и дᴇᴧᴀюᴛ чᴛо ᴄᴨᴇциᴀᴧьно убиʙᴀюᴛ ᴨᴀциᴇнᴛоʙ 🤩 — ᴛᴀᴋ ᴛоɯниᴛ ᴄ ϶ᴛоᴦо ᴨᴇйᴩинᴦᴀ но нᴇ знᴀᴇɯь ᴦдᴇ ʙыᴄᴋᴀзᴀᴛь ᴄʙоё ʍнᴇниᴇ о нёʍ знᴀᴋоʍо? ᴛоᴦдᴀ добᴩо ᴨожᴀᴧоʙᴀᴛь ʙ.... 🤩 🔤🔤 🔤🔤🔤🔤🔤🔤🔤 🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤 [🍉🌸]здᴇᴄь ʙы ʍожᴇᴛᴇ ʙыᴄᴋᴀзᴀᴛь ʙᴄё чᴛо ʙᴀᴄ зᴀᴇбᴀᴧо ʙ ϶ᴛоʍ ᴋоʍьюниᴛи иᴧи иᴦᴩᴇ нᴀʙиᴦᴀция🤩 боᴛ дᴧя ᴛᴇйᴋоʙ🤩 нᴀ…