Telegram RegisterThe public register of Telegram

Channel

axenov.dev

@axenov_dev

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

53subscribers

+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-1001726463694
TypeChannel
Username@axenov_dev
DescriptionКанал о разработке, FOSS + кросспост из блога Навигация: https://t.me/axenov_dev/11 🚀 https://t.me/axenov_dev?boost ✍️ @axenov_blog — оффтоп 🤕 @anthonyaxenov 🌐 https://axenov.dev
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/axenov_dev

Growth

537 August 2026 — 53 subscribers10 August 2026 — 53 subscribers7 August 202610 August 2026
2 measurements spanning 3 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 52–54 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 09:4553no change
7 Aug 2026, 20:2053first reading

Engagement

20 posts held, back to 12 May 2023the 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 3 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
26
Links
101

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

21 reactions across 12 posts, in 2 distinct kinds. The most used accounts for 85.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1885.7%
🔥314.3%

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

Measured over the 20 most recent posts we hold, published 12 May 2023 to 3 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 20 we hold a reading for · 10%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @axenov_dev. 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 20 most recent posts we hold for this entry, published 12 May 2023 to 3 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

3 Jun 2026, 08:08 UTC53 views2 reactionsread 10 August 2026
Forwarded from @orgprog

Митчелл Хашимото (создатель HashiCorp и Ghostty) написал важный пост про агентное программирование. Он хорошо подсвечивает проблему, того, что будет происходить если использование агента не будет подкреплено пониманием происходящего. tldr; нас ждет медленный и бажный софт. Дальше вольный перевод. Я запустил агента в цикле оптимизации рендерера. Цель была снизить время рендеринга кадра. Для измерения были тесты. Аг

👍2

29 Mar 2026, 15:37 UTC102 viewsread 10 August 2026

📝 Домашний сервер на Ubuntu. Часть 2: применение, развитие Продолжение первой части о домашней машине. О железе и софте, что не пригодилось из первой части и добавлено нового. https://axenov.dev/домашний-сервер-на-ubuntu-часть-2-применени/ #блог #моё #Ubuntu #околоNAS #MiniDLNA #Cockpit #Gitea #OpenGist #Железо 👨‍💻 @axenov_dev 👍 @axenov_blog

27 Nov 2025, 15:47 UTC223 views2 reactionsread 10 August 2026

Иногда надо программно получить ссылку на свежайший релизный ассет с гитхаба. Методов API для получения последнего тега нет. Часто хватает привычного https://github.com/owner/repo/releases/download/latest/filename.ext Но ведь в названии ассета может указываться версия: https://github.com/owner/repo/releases/download/latest/filename_1.2.3.ext Так-то можно было бы подставить её в урлу и вперёд. Но для этого надо будет

👍1🔥1

21 Nov 2025, 17:15 UTC192 viewsread 10 August 2026

📝 Gitea Actions: как обойти ошибку 403 от docker.io при сборке образа Что будет, если попытаться захотеть построить docker-образ через Gitea Actions на сервере в РФ? Ошибка 403 от докер-хаба. Рассказываю как решить. https://axenov.dev/gitea-actions-как-обойти-ошибку-403-от-docker-io-при-сборке-о/ #блог #моё #Docker #gitea 👨‍💻 @axenov_dev 👍 @axenov_blog

29 Oct 2025, 09:43 UTC207 viewsread 10 August 2026

📝 Gitea не даёт скачать репозиторий архивом, как исправить? Мне тут написали на почту с проблемой, мол, хочу скачать архив репы, а не качается -- ни через веб-морду, ни по API. Я о такой проблеме даже не знал, потому что просто не приходится пользоваться этой фичей. Фича безусловно полезна, поэтому такая проблема неприятна. Как она проявляется: https://axenov.dev/gitea-не-даёт-скачать-репозиторий-архивом/ #блог #м

20 Oct 2025, 10:23 UTC155 views2 reactionsread 10 August 2026

📝 Как из РФ получить доступ к зарубежным моделям ИИ? Короткий справочник по некоторым моделям и сервисам с ИИ, которые можно использовать в РФ бесплатно или за рубли. Пользуйтесь! https://axenov.dev/ai-from-rf/ #блог #моё #API #LLM #ollama #openai #ИИ 👨‍💻 @axenov_dev 👍 @axenov_blog

👍1🔥1

28 Sept 2025, 18:37 UTC155 views1 reactionsread 10 August 2026

Как обещал, пост обновлён. Добавил туда не только инфу о раннерах, но и исправил своё упущение по поводу юзера git и работы по ssh. Однажды успешно настроив на одном сервере, я споткнулся на тех же шагах на другом сервере, а решение оказалось простым, но хорошо спрятанным. Так что этот вопрос я решил скриптом. Теперь можно спокойно пользоваться всей связкой.

👍1

8 Apr 2025, 05:42 UTC380 viewsread 10 August 2026

В тот же репозиторий я добавил раннер для работы Gitea Actions и описал в README несложную настройку. В скором времени буду запускать, обкатывать и шлифовать это на сервере git.axenov.dev в нескольких проектах. Обновлю пост в блоге, когда буду уверен в сетапе. Но если настроить и запустить окружение локально, то демка отработает исправно, так что я заранее доволен.

22 Feb 2025, 14:54 UTC438 views1 reactions1 Starread 10 August 2026

📝 Миграция self-hosted gitea в docker Перетаскиваем Gitea в docker-окружение на новый сервер и поднимаем рядышком Opengist. https://axenov.dev/gitea-to-docker/ #блог #моё #Docker #gitea #MySQL #Ubuntu #Резервирование 👨‍💻 @axenov_dev 👍 @axenov_blog

👍1

8 Jan 2025, 05:35 UTC544 views0 reactions1 Starread 10 August 2026

С тех пор утекло много воды. Вышло 9 версий среды разработки NetBeans, пыха дошла до 8.4, вот-вот релизнется мажрная версия xdebug 4. Я решил вернуться к мануалу и актуализировать его. NB взял 24, пыху 8.3 и xdebug 3.3.2. При этом был немного удивлён: хотя NB всё ещё не готов к пыхе 8.4 и отладке через docker-контейнер, других действительно серьёзных ломающих изменений так и не произошло, поэтому многие скриншоты я

30 May 2024, 15:53 UTC471 views2 reactionsread 10 August 2026

📝 Docker Hub заблокирован, как исправить ошибку 403 Краткая рабочая шпаргалка по решению ошибки 403 в докере для России https://axenov.dev/docker-hub-заблокирован-как-исправить-ошибку-403/ #блог #моё #Docker #Linux 👨‍💻 @axenov_dev 👍 @axenov_blog

👍2

3 Apr 2024, 15:36 UTC447 viewsread 10 August 2026
Forwarded from @misha_writes_codePhoto

Зацените, какой прикол Вот тут подробнее можно посмотреть: https://unix.stackexchange.com/questions/73713/how-safe-is-it-to-cat-an-arbitrary-file Создать такой же файл: echo -e '#!/bin/sh\necho "...doing something bad here..."\nexit\n\033[A\033[Aecho "Hello dear reader, I am just a harmless script, safe to run me!"' > demo.sh chmod a+x demo.sh

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

Forward network

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

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

“axenov.dev” (@axenov_dev), 53 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/axenov_dev.

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.