Канал фулстек‑разработчика. Коротко и по делу про современный CSS, дизайн и фронтенд, практики Next.js/Node, инфраструктуру (Docker, Nginx), автоматизацию и производительность. Без воды, с примерами.
Created
Between 1 September 2025 and 17 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
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 37–39 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
10 Aug 2026, 21:00
38
no change
7 Aug 2026, 21:15
38
first reading
Engagement
17 posts held, back to 17 November 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 4 March 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
35
Videos
1
Links
18
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.
Video runtime
7s
Average length
7s
Measured directly from 1 video 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
107 reactions across 17 posts, in 13 distinct kinds. The most used accounts for 30.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
33
30.8%
👍
18
16.8%
❤
16
15.0%
🤝
10
9.35%
👏
7
6.54%
⚡
6
5.61%
💯
5
4.67%
😁
4
3.74%
👌
2
1.87%
😢
2
1.87%
🥰
2
1.87%
🆒
1
0.935%
🦄
1
0.935%
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 17 of the 17 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 107reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 17 November 2025 to 4 March 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
12
across the posts below
Posts paid on
4
of 17 we hold a reading for · 24%
Most on one post
8
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @gooselabs. 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 17 most recent posts we hold for this entry, published 17 November 2025 to 4 March 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.
📱 WebHaptics — тактильная обратная связь для мобильного веба
👩💻 JavaScript-библиотека, которая добавляет вибрацию в веб-приложения на смартфонах и планшетах. Раньше такое было доступно только для нативных приложений, либо в телеграм мини-аппс.
Простая интеграция, работает на мобильных браузерах, добавляет приложениям тот самый "ощутимый" фидбек, как в нативных приложениях.
https://haptics.lochie.me
👩💻
npm …
2 года назад
В январе 2024 простая игра в Telegram взорвала крипто-мир.
Notcoin — как tap-to-earn игра стала феноменом
Сама механика не нова — помните ВКонтакте времён Счастливого фермера? Но 11 ноября 2023 на конференции The Gateway в Дубае эту идею показали миру.
1 января 2024 — официальный запуск:
• 1 млн пользователей за 2 дня
• 20 млн за месяц
• 35+ млн к листингу
Залетел в Notcoin на старте. С тех пор идея…
GooseUI теперь в официальном Registry Directory shadcn/ui
Наша библиотека компонентов добавлена в официальный каталог shadcn — это значит, что установить любой компонент можно одной командой:
npx shadcn add @gooseui/toast
Что внутри:
→ Анимированные компоненты
→ Кастомные toast-уведомления
→ Красивые эффекты
Каталог: ui.shadcn.com/docs/directory?q=gooseui
Сайт: gooseui.pro
🎠 Карусель без JavaScript-библиотек
Выпустил новый компонент для GooseUI — Carousel на нативном CSS.
Почему это круто:
• Без Embla, Swiper и прочих библиотек
• CSS scroll-snap — работает в 96.4% браузеров
• Размер: 0 KB дополнительного JS
• Keyboard navigation из коробки
• Auto-play с паузой при наведении
Что под капотом:
scroll-snap-type: x mandatory
Просто нативный скролл, который браузер умеет делать идеально…
📋 Подал заявку в официальный реестр shadcn/ui
GooseUI теперь на рассмотрении у команды shadcn\!
Если одобрят — можно будет устанавливать компоненты так:
npx shadcn add @gooseui/button
Вместо длинного:
npx shadcn add https://gooseui.pro/r/button.json
Следим за статусом: github.com/shadcn-ui/ui/issues/9244
🦆 gooseui.pro
🦆 Запустил GooseUI — свою библиотеку компонентов
Сделал open-source UI kit на базе shadcn/ui. Серьёзный проект: документация, CLI установка, Tailwind v4
Функции:
- установка компонентов одной командой прямо в проект
- компоненты для работы с текстом
- кастомные компоненты карусель с использованием scroll snap
- модальное окно с применением view transitions
Установка одной командой:
npx shadcn add https://gooseui.…
Сидел как-то вечером и искал идеи для проекта. Потом вспомнил про бесплатный API с покемонами PokéAPI и решил реализовать данный проект. Удалось это сделать буквально за вечер с помощью Claude Code.
😳 Pokedex — интерактивный каталог покемонов
Что внутри:
• Каталог 1025 покемонов с бесконечным скроллом
• Фильтрация по 18 типам + поиск по имени
• Детальные карточки: статы, эволюции, описания
• Сравнение по…
Друзья,
Мы будем очень рады вашей обратной связи по докладам Frontend Night — это поможет нам делать следующие мероприятия ещё сильнее.
🐾 Пройти опрос можно тут (всего 3 шага), а в конце забирайте ссылку на фотографии!
Записи и презентации тоже скоро опубликуем 🎁
Sber провёл потрясную конференцию «фронтенд найт»! Это лучший митап в плане организации и атмосферы! В основном затронули AI в разработке в позитивном и негативном ключе! Все зрители сделали выводи и многие поучаствовали в воркшопах!!!
P.S. Ждём фотки и запись выступлений
🖥 Ссылки на инструменты, представленные в презентации Фронтенд найт
Wispr Flow - инструмент для перевода речи в текст
wisprflow.ai
Claude Code - CLI инструмент от Antropic
claude.com/product/claude-code
Gemini CLI - CLI инструмент от Google
geminicli.com
Droid — CLI инструмент от Factory AI
factory.ai/product/cli
OpenCode - бесплатный CLI инструмент с лучшим интерфейсом
opencode.ai
Qwen Coder - бесплатный CLI …
❤5⚡4🔥2🆒1
Showing the 12 most recent of 17 posts we hold for @gooselabs. 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
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
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@gooselabs named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@gooseui named in 2 posts, 11 August 2026 – 11 August 2026
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.
“GooseLabs” (@gooselabs), 38 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/gooselabs.
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.