Telegram RegisterThe public register of Telegram

Channel

Всё об 1С:Элемент

@new_element_1c

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

455subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002561727161
TypeChannel
Username@new_element_1c
DescriptionИспользуем 1С:Элемент для развития бизнеса, своего, клиентов, партнёров... Опыт разработки, реальные кейсы, мысли вслух.
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/new_element_1c

Growth

4557 Aug 2026, 15:30 — 455 subscribers8 Aug 2026, 04:50 — 455 subscribers7 Aug 2026, 15:308 Aug 2026, 04:50
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 454–456 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 04:50455no change
7 Aug 2026, 15:30455first reading

Engagement

11 posts held, back to 15 December 2025the 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 11 posts for this entry, the most recent from 8 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
52
Videos
2
Links
29

Lifetime counters from Telegram’s own channel header, read 8 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.

Reaction mix

177 reactions across 11 posts, in 12 distinct kinds. The most used accounts for 50.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍9050.8%
🔥4223.7%
1810.2%
👏73.95%
42.26%
❤‍🔥42.26%
🤔42.26%
custom 539762980627364883821.13%
💯21.13%
🦄21.13%
🎄10.565%
😁10.565%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.

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

Measured over the 11 most recent posts we hold, published 15 December 2025 to 8 June 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.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
2
of 11 we hold a reading for · 18%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @new_element_1c. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 11 most recent posts we hold for this entry, published 15 December 2025 to 8 June 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

8 Jun 2026, 07:16 UTC417 views19 reactions1 Starread 8 August 2026
Photo

Книжный клуб v2 Давние подписчики в курсе, что мы работаем над проектом Книжный клуб Дениса Соколова. Рады представить новую версию, вот чем может сейчас похвастаться платформа: 1️⃣Улучшенный пользовательский интерфейс 2️⃣Свободная регистрация собственных клубов 3️⃣Планирование событий клуба и списков чтения 4️⃣Использование Системы взаимодействия для общения и проведения онлайн встреч 5️⃣Интегрированный каталог кни

👍9🔥6👏4

23 Apr 2026, 03:13 UTC≈1,310 views18 reactionsread 8 August 2026
Photo

Библиотека 1С:Элемент для работы с мессенджером MAX На базе библиотеки 1С для работы с Telegram подготовили библиотеку для MAX. Разместили на gitflic.ru, лицензия MIT, улучшения и предложения приветствуются. Автор разработки, Кирилл Стрельников, в комментариях может ответить на вопросы. Возможности 🟡Подключение бота MAX к опубликованному приложению через webhook. 🟡Прием входящих событий по HTTP endpoints приложен

👍8🔥64

3 Apr 2026, 07:14 UTC585 views17 reactionsread 8 August 2026
Forwarded from @it_lunchPhoto

😳 Запись созвона по разработке на 1С:Элемент с помощью ИИ В этом видео — запись созвона, где на живом примере показываем, как использовать ИИ в разработке на 1С:Элемент. В центре внимания Claude Code и Codex: как подключить MCP, работать со skills, создавать объекты конфигурации, формы, документы и доводить все до сборки и деплоя в 1cmycloud.com ▶️По ходу ролика: 🟣запускаем Claude Code и проверяем, как он понимает

👍11❤‍🔥4🔥2

3 Apr 2026, 03:01 UTC582 views19 reactions1 Starread 8 August 2026
Photo

1С:Элемент и VS Code? Да! Теперь удобней! Александр Волков опубликовал расширение для VS Code, которое подсвечивает синтаксис языка 1С:Элемент. https://github.com/avolkov-git/element-lang-vscode И в маркетплейсе расширений: https://marketplace.visualstudio.com/vscode Приятно, что экосистема 1С:Элемент обрастает примочками! #vscode #сообщество Всё об 1С:Элемент

👍11🔥62

26 Feb 2026, 07:55 UTC865 views16 reactionsread 8 August 2026

Пост для партнёрского семинара 1С Для участников партнёрского семинара и читателей канала подготовил этот пост с ссылками по тем ИИ-инструментов. Чем реально пользуюсь, что считаю полезным, использую в работе компании. Диаризация/транскрибация 🟡Сервис Follow-UP Поддерживает сервисы: Яндекс.Телемост, GoogleMeet, Zoom, SaluteJazz, MS Teams, КонтурТолк, JitsiMeet, ТруКонф, есть телеграм-бот. — Функциональность: транскр

👍74🔥41

19 Feb 2026, 05:21 UTC728 views22 reactionsread 8 August 2026

Я в порядке! Расскажу про небольшой учебный проект. Для поддержания и развития навыков работы с ботами телеграм сделали бота "Я в порядке", который реализует принцип свидетельства канарейки. «Свидетельство канарейки» (англ. warrant canary) — способ передачи информации, осуществляемый через молчание или отрицание. Термин возник как отсылка к практике шахтёров, которые использовали канареек в качестве сигнала о токси

👍10👏3🔥3🤔2🦄21🎄1

18 Feb 2026, 08:27 UTC531 views12 reactionsread 8 August 2026

Nginx как обратны прокси (дополнение) В инструкции по настройке обратного прокси на Nginx допущена ошибка. Нужно внести поправки, если кто-то её использовал, учитывайте этот момент. В конфигурационный файл нужно внести изменение: server { listen 88; server_name 1c-element.somesite.ru; location ^~ /.well-known/acme-challenge/ { default_type "text/plain"; root /var/www/letsencrypt; } location = /

👍84

19 Jan 2026, 05:22 UTC≈2,040 views19 reactionsread 8 August 2026
Photo

Как вайбкодинг влияет на квалификацию программистов Каждый, кто работает с кодом знаком с термином вайбкодинг. Я узнал этот термин от соискателя на вакансию программист 1С, это было забавно и поучительно. Времени с той истории прошло много, я пообщался с коллегами по 1С, с программистами из других областей, подумал и хочу обсудить с вами одну мысль. Применение LLM для разработки, упрощает для начинающего программис

👍11🔥5🤔2😁1

7 Jan 2026, 06:55 UTC782 views15 reactionsread 8 August 2026
Photo

Unknown problem when connecting to DB Знаете, как бывает - сидишь, никого не трогаешь, БАХ - ошибка! Так и случилось на этот раз с онпремом - ничего не предвещало беды, как вдруг, при создании нового приложения ошибка (скрин 1). После определённой даты создать новое приложение не получается (скрин 2). Все текущие работают: разработка, отладка, панель управления - всё хорошо, никаких ошибок. А новое - ни-ни… Обрати

👍103💯2

15 Dec 2025, 14:00 UTC652 views9 reactionsread 8 August 2026

Кому-то не хватает вакансий по 1С:Элемент, а кто-то усиленно ищет разработчика в команду! Попалась мне вот такая интересная вакансия. Может подписчик попадёт в команду 1С:Элемент? 🤔 #кадровое #вакансия

🔥6👍21

15 Dec 2025, 14:00 UTC780 views11 reactionsread 8 August 2026
Photo

💥Фирма 1С ищет Ведущего разработчика 1С для развития облачного продукта на базе 1С:Предприятие.Элемент. 🔸У кого точно получится: •Кто хочет и готов погружаться в 1С Элемент, заинтересован в его развитии и масштабировании технологии в Экосистеме 1С •По уровню старший разработчик / архитектор 1С с опытом продуктовой разработки •Глубокое знание платформы (уровень «Специалист по платформе» и выше) •Сильный опыт интеграц

🔥4👍32custom 53976298062736488382

Showing the 11 most recent of 11 posts we hold for @new_element_1c. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 1,111,691 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Всё об 1С:Элемент” (@new_element_1c), 455 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/new_element_1c.

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.