Telegram RegisterThe public register of Telegram
Telegram profile photo for ❌ Лента постов (с задержкой 1 день) Хабра (не обновляется)

Channel

❌ Лента постов (с задержкой 1 день) Хабра (не обновляется)

@sohabr_1d_delay

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Cite this entry

4subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001043651671
TypeChannel
Username@sohabr_1d_delay
CreatedBetween 1 January 2016 and 30 November 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live9 November 2026
Measurements held6
Confirmed unchanged3 times, most recently 9 November 2026
On Telegramt.me/sohabr_1d_delay

Topic

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 3 October 2026 and assigned it the closest of 31 fixed categories, at 81% 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.

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 in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@sohabr_6h_delay/5458512 May 2019, 21:54 UTC@sohabr_1d_delay/54583 · this entry13 May 2019, 15:54 UTC1.0018 hours
@sohabr_6h_delay/5458612 May 2019, 22:03 UTC@sohabr_1d_delay/54584 · this entry13 May 2019, 16:03 UTC1.0018 hours
@sohabr_6h_delay/5458712 May 2019, 22:04 UTC@sohabr_1d_delay/54585 · this entry13 May 2019, 16:04 UTC1.0018 hours
@sohabr_6h_delay/5459413 May 2019, 01:28 UTC@sohabr_1d_delay/54592 · this entry13 May 2019, 19:28 UTC1.0018 hours
@sohabr_6h_delay/5459513 May 2019, 01:36 UTC@sohabr_1d_delay/54593 · this entry13 May 2019, 19:36 UTC1.0018 hours
@sohabr_6h_delay/5459613 May 2019, 02:08 UTC@sohabr_1d_delay/54594 · this entry13 May 2019, 20:08 UTC1.0018 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@sohabr_6h_delay13 (8/8 hand-verifiable sample passed)1.0018 hours@sohabr_6h_delay (13–0)
@sohabr10 (8/8 hand-verifiable sample passed)1.0024 hours@sohabr (10–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 23 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 13 May 2019 to 14 May 2019. 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).

Of the group of 3 channels, the one whose matching posts we hold earliest is @sohabr. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 11 November 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.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.

Growth

3549 August 2026 — 4 subscribers13 August 2026 — 4 subscribers17 August 2026 — 3 subscribers24 August 2026 — 4 subscribers12 October 2026 — 5 subscribers26 October 2026 — 4 subscribers9 August 202626 October 2026
6 measurements spanning 78 days. 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 3–5 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Oct 2026, 08:154-1
12 Oct 2026, 23:405+1
24 Aug 2026, 14:374+1
17 Aug 2026, 11:153-1
13 Aug 2026, 09:474no change
9 Aug 2026, 10:504first reading

Engagement

20 posts held, back to 13 May 2019 — 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 page of 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 20 October 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

20 Oct 2022, 12:09 UTCviews —

Channel name was changed to «❌ Лента постов (с задержкой 1 день) Хабра (не обновляется)»

14 May 2019, 10:43 UTCviews —

❌ Лента постов (с задержкой 1 день) Хабра (не обновляется) pinned «Всё, лента здесь обновляться больше не будет. shbr.xyz теперь ведёт по умолчанию на Хабр, да и на СоХабре скоро для не спрятанных в черновики постов будет редирект на Хабр, так что все ссылки выше работают и будут работать ещё неопределённое время. Спасибо…»

14 May 2019, 10:43 UTC59 viewsread 13 August 2026

Чтобы продолжать следить за постами, Вы можете подписаться на официальный канал Хабра: @habr_com.

Signed Vladimir Solomatin

14 May 2019, 10:43 UTC59 viewsread 13 August 2026

Всё, лента здесь обновляться больше не будет. shbr.xyz теперь ведёт по умолчанию на Хабр, да и на СоХабре скоро для не спрятанных в черновики постов будет редирект на Хабр, так что все ссылки выше работают и будут работать ещё неопределённое время. Спасибо, что были подписаны на канал!

Signed Vladimir Solomatin

13 May 2019, 21:43 UTC55 viewsread 13 August 2026

graphql — подводные камни 🗂 Node.JS, JavaScript Наверное, не существует идеальных технологий. Не является исключением и graphql. Если у Вас еще не было опыта работы с этой технологией, то нужно хорошо представлять, какие проблемы могут у Вас возникнуть и заблаговременно к ним подготовиться. Читать далее ➡ https://shbr.xyz/hh451466

Signed Бот СоХабра

13 May 2019, 21:25 UTC31 viewsread 13 August 2026

ManualResetEventAsync 🏷 в черновиках 🗂 C#, .NET Возникла сегодня идея написать асинхронную версию ManualResetEvent, которая в задаче будет «ожидать» через await и при этом не занимать никакой поток. В теории все просто, для стейтмашины нужен объект, который имеет метод GetAwaiter, который вернет awaiter, в котором реализован INotifyCompletion с OnCompleted, свойство IsCompleted и метод GetResult. Awaiter: Читать …

Signed Бот СоХабра

13 May 2019, 20:24 UTC17 viewsread 13 August 2026

Дайджест свежих материалов из мира фронтенда за последнюю неделю №364 (6 — 12 мая 2019)⁠ 🗂 HTML, JavaScript, CSS, Разработка веб-сайтов Предлагаем вашему вниманию подборку с ссылками на новые материалы из области фронтенда и около него. Читать далее ➡ https://shbr.xyz/hh451468

Signed Бот СоХабра

13 May 2019, 20:12 UTC15 viewsread 13 August 2026

Frontend Weekly Digest (6 – 12 May 2019)⁠ 🗂 HTML, JavaScript, CSS, Разработка веб-сайтов This week we issue a really huge selection of all the essential news you might have missed on Front-end development. Make sure to check the latest updates on CSS, HTML, and JavaScript. Читать далее ➡ https://shbr.xyz/hh451464

Signed Бот СоХабра

13 May 2019, 20:08 UTC13 viewsread 13 August 2026

Пишем меньше дублирующего кода, используя биндинг в Laravel⁠ 🏷 Tutorial 🗂 Laravel, PHP, Разработка веб-сайтов Доброго времени, уважаемые господа. Не так давно столкнулся с явлением дублирующегося и повторяющегося кода при код ревью одного проекта на Laravel. Суть в следующем: у системы существует некоторая структура внутреннего API для AJAX запросов, по сути возвращающая коллекцию чего-либо из базы (заказы, пользо…

Signed Бот СоХабра

13 May 2019, 19:36 UTC13 viewsread 13 August 2026

Опыт создания позиционных карт для Википедии⁠ 🗂 Социальные сети и сообщества, Краудсорсинг, Creative Commons В течение нескольких лет я работал над картами, которые используются в русском и других языковых разделах Википедии. Всего мной было создано более 300 карт. Я не являюсь профессиональным картографом, и не имею специального образования в этой области. Видимо, мне просто нравилось делать карты :) В рамках этой …

Signed Бот СоХабра

13 May 2019, 19:28 UTC12 viewsread 13 August 2026

Docker контейнер для управления HP серверами через ILO 🏷 Tutorial 🗂 DevOps, Серверное администрирование, IT-инфраструктура, Системное администрирование Вы наверное может задаться вопросом — а здесь то Docker зачем? В чем проблема зайти на веб интерфейс ILO и настроить свой сервер как надо? Так и я думал когда мне отдали пару старых ненужных серверов, которые мне надо было переустановить (то что называется reprovisi…

Signed Бот СоХабра

13 May 2019, 18:23 UTC11 viewsread 13 August 2026

Изменяем содержимое нотификации приложения iOS 🏷 Из песочницы, Tutorial 🗂 Swift, Разработка под iOS Привет! В этой статье я хочу поделиться своим опытом использования одного не очевидного (по крайней мере для меня) варианта изменения текста уведомления приложения, отправкой дополнительных данных через UNUserNotificationCenter. Я надеюсь эта статья будет полезна для новичков в программировании под iOS на Swift. Пре…

Signed Бот СоХабра

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

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

“❌ Лента постов (с задержкой 1 день) Хабра (не обновляется)” (@sohabr_1d_delay), 4 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/sohabr_1d_delay.

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.