Telegram RegisterThe public register of Telegram
Telegram profile photo for Логово верстальщика

Channel

Логово верстальщика

@webdevlair

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

7,934subscribers

-215 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001351279015
TypeChannel
Username@webdevlair
Created21 November 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live5 October 2026
Measurements held16
Confirmed unchanged1 time, most recently 5 October 2026
On Telegramt.me/webdevlair

Topic

Technology — 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 100% 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 6 other registered channels. 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
@webdevlair/4413 · this entry25 Jul 2026, 10:17 UTC@frontendnoteschannel_ru/568925 Jul 2026, 10:17 UTC1.00under a minute
@webdevlair/4418 · this entry26 Jul 2026, 07:37 UTC@frontendnoteschannel_ru/569226 Jul 2026, 07:37 UTC1.00under a minute
@frontendnoteschannel_ru/569627 Jul 2026, 19:27 UTC@webdevlair/4422 · this entry27 Jul 2026, 19:27 UTC1.00under a minute
@frontendnoteschannel_ru/570129 Jul 2026, 06:07 UTC@webdevlair/4426 · this entry29 Jul 2026, 06:07 UTC1.00under a minute
@webdevlair/4433 · this entry30 Jul 2026, 16:37 UTC@frontendnoteschannel_ru/570630 Jul 2026, 16:37 UTC1.00under a minute
@webdevlair/4435 · this entry31 Jul 2026, 14:37 UTC@frontendnoteschannel_ru/570831 Jul 2026, 14:37 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@frontendnoteschannel_ru9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (5–4)
@python_tesst9 (8/8 hand-verifiable sample passed)1.00under a minute@python_tesst (7–2)
@devsp9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (5–4)
@we_use_js8 (8/8 hand-verifiable sample passed)1.00under a minuteeven
@true_js7 (7/7 hand-verifiable sample passed)1.00under a minute@true_js (6–1)
@qa_logia6 (6/6 hand-verifiable sample passed)1.00under a minutethis entry (4–2)

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 27 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 17 comparable posts for this entry, running 24 July 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 7, the earliest publisher we hold is @devsp. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual · 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 6 other registered channels, 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.

Growth

7,9348,1498,041.56 August 2026 — 8,149 subscribers6 August 2026 — 8,149 subscribers7 August 2026 — 8,145 subscribers10 August 2026 — 8,125 subscribers14 August 2026 — 8,096 subscribers17 August 2026 — 8,082 subscribers20 August 2026 — 8,064 subscribers24 August 2026 — 8,047 subscribers27 August 2026 — 8,035 subscribers30 August 2026 — 8,027 subscribers2 September 2026 — 8,015 subscribers7 September 2026 — 8,005 subscribers11 September 2026 — 8,000 subscribers15 September 2026 — 7,987 subscribers27 September 2026 — 7,961 subscribers5 October 2026 — 7,934 subscribers6 August 20265 October 2026
16 measurements spanning 60 days, net -215. 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 7,902–8,181 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Oct 2026, 09:557,934-27
27 Sept 2026, 17:217,961-26
15 Sept 2026, 11:557,987-13
11 Sept 2026, 14:588,000-5
7 Sept 2026, 00:218,005-10
2 Sept 2026, 19:198,015-12
30 Aug 2026, 15:068,027-8
27 Aug 2026, 17:038,035-12
24 Aug 2026, 09:098,047-17
20 Aug 2026, 19:128,064-18
17 Aug 2026, 12:058,082-14
14 Aug 2026, 00:478,096-29
10 Aug 2026, 12:278,125-20
7 Aug 2026, 03:558,145-4
6 Aug 2026, 10:198,149no change
6 Aug 2026, 09:448,149first reading

Engagement

63 posts held, back to 24 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 25 pages 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 63 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
4m 56s
Average length
59s

Measured directly from 5 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

64 reactions across 31 posts, in 5 distinct kinds. The most used accounts for 39.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁2539.1%
❤1929.7%
🔥914.1%
👍812.5%
👎34.69%

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 34 of the 63 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 64 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 63 most recent posts we hold, published 24 July 2026 to 28 August 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

28 Aug 2026, 15:17 UTC146 views3 reactionsread 28 August 2026
Photo

Руки от релиза убрал 💥 xCode Journal

😁3

28 Aug 2026, 06:07 UTC279 views1 reactionsread 28 August 2026
Photo

💻 Айтишника развели на 200 тысяч под предлогом оффера Мошенники действовали по простой и давно обкатанной схеме. Соискателям просто кидают тестовое, в котором надо найти баги, а доверчивые и отчаявшиеся от рынка труда работяги без страха скачивают репозиторий, запускают код, а с ним вместе и вирус, который уводит данные счетов и криптокошельков. ✖️ xCode Journal

😁1

27 Aug 2026, 10:17 UTC384 views6 reactionsread 28 August 2026
Photo

❌ Разработчику отказали в собеседовании из-за нейминга файла с резюме Дело в том, что он назвал файл «resume_final_FINAL_final2.pdf» «К сожалению, мы решили продолжить сотрудничество с тем, кто разбирается в системе контроля версий.», - ответили бедняге. ✖️ xCode Journal

😁6

25 Aug 2026, 17:17 UTC425 views4 reactionsread 28 August 2026
Photo

🤣 Виндовый диалог. Волшебник с маком 💥 xCode Journal

🔥2😁2

23 Aug 2026, 17:07 UTC562 viewsread 28 August 2026
Photo

Иначе на джуна уже и не берут Иначе на джуна уже и не берут 👉 Логово Верстальщика

23 Aug 2026, 09:07 UTC544 views1 reactionsread 28 August 2026
Photo

DeepSeek снова крутит цены на API — с выходных весь день будет действовать один сниженный тариф. Компания официально предупредила (https://platform.deepseek.com/usage): с 23 августа схема оплаты в пиковые и непиковые часы меняется. По субботам и воскресеньям деление на периоды вообще убирают — сутки напролёт будет действовать единый тариф, и это цена непикового времени. Проще говоря, забудь про высчитывание непиков…

🔥1

22 Aug 2026, 13:07 UTC477 views2 reactionsread 28 August 2026
Video

Терминал теперь может притворяться VS Code В Х шумит terminal-code. Он превращает консоль в редактор, который выглядит как VS Code. Работает через SSH, совместим с VS Code CLI и сам цепляет тему терминала. Гиковее уже некуда terminal-code.com 👉 Логово Верстальщика

🔥2

22 Aug 2026, 09:07 UTC468 viewsread 28 August 2026
Photo

Codex перевалил за 20 миллионов активных пользователей. 🎉 И по такому поводу всем, кто сидит в Codex и ChatGPT Work, на выходные дают кнопку сохранённого сброса лимита. 🤓 Источник: t.me/vibecoding_tg/3723

21 Aug 2026, 17:07 UTC458 views1 reactionsread 28 August 2026
Photo

Какой-то разраб склепал ИИ-утилиту, которая выжимает из App Store дополнительную выручку. Скрипт adapt-appstore-prices-cli сам подгоняет цены под каждую страну: смотрит на экономические показатели вроде ВВП на душу населения и предлагает локальные ценники. Логика простая — не выставлять один и тот же ценник и в США, и в Индии. Автор говорит, что после такой подстройки доход может вырасти в разы. Денежки капают 🤑 — …

😁1

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

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 6 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.

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.

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.

Сайтодел | GitHub, Верстка, Сайты, Вайбкодинг
@sitodel · 25,662
Telegram ranks this channel #7 of 89 here — alongside 88 others — read 13 September 2026
Frontender's notes [ru]
@frontendnoteschannel_ru · 31,223
Telegram ranks this channel #9 of 95 here — alongside 94 others — read 6 September 2026
Frontend Portal
@FrontendPortal · 36,370
Telegram ranks this channel #9 of 90 here — alongside 89 others — read 1 September 2026
Code Ready | Frontend
@code_ready · 21,675
Telegram ranks this channel #11 of 89 here — alongside 88 others — read 23 September 2026
Вайб-кодинг
@vibecoding_tg · 63,609
Telegram ranks this channel #11 of 85 here — alongside 84 others — read 1 September 2026
Макеты для верстки
@figma2html · 45,301
Telegram ranks this channel #14 of 90 here — alongside 89 others — read 27 August 2026
Senior Frontend - javascript, html, css
@seniorFront · 23,852
Telegram ranks this channel #15 of 89 here — alongside 88 others — read 17 September 2026
Senior Frontend Developer | JavaScript, React, HTML & CSS
@senior_front · 19,233
Telegram ranks this channel #29 of 90 here — alongside 89 others — read 2 October 2026
FrontEndDev
@front_end_dev · 25,809
Telegram ranks this channel #30 of 95 here — alongside 94 others — read 13 September 2026
True Figma
@true_figma · 26,013
Telegram ranks this channel #33 of 88 here — alongside 87 others — read 13 September 2026
Веб-страница
@tproger_web · 22,373
Telegram ranks this channel #34 of 96 here — alongside 95 others — read 20 September 2026
Open IT | Архив
@openit_archive · 18,785
Telegram ranks this channel #39 of 59 here — alongside 58 others — read 5 October 2026
IT Portal
@IT_Portal · 99,777
Telegram ranks this channel #44 of 78 here — alongside 77 others — read 15 August 2026
Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js
@frontendproglib · 20,812
Telegram ranks this channel #48 of 93 here — alongside 92 others — read 25 September 2026
Английский для программиста | EnglishScript
@EnglishScript · 44,988
Telegram ranks this channel #52 of 82 here — alongside 81 others — read 27 August 2026

This channel appears in 15 seed channels' Telegram-generated recommendation lists in total. 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 October 2026 — this entry's latest reading, not the date you are reading this.

“Логово верстальщика” (@webdevlair), 7,934 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/webdevlair.

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.