27 Jan 2026, 19:46 UTC13 viewsread 12 August 2026
Photo
В будущем нужно подумать об оптимизации статусов прочитанных сообщений мессенджера. Пока что это такой бэтч
Channel
Programmer Base
@redirexStudio
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
7subscribers
+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 | -1001497427968 |
|---|---|
| Type | Channel |
| Username | @redirexStudio |
| Description | Redirex - сообщество разработчиков web/server проектов. База знаний основных концепций и шаблонов проектирования, примеры использования кода. |
| Created | Between 1 October 2019 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/redirexStudio |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 16:46 | 7 | no change |
| 7 Aug 2026, 23:13 | 7 | first reading |
Engagement
20 posts held, back to 22 August 2023 — 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 27 January 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 15
- Links
- 7
Lifetime counters from Telegram’s own channel header, read 12 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.
Recent posts
19 Jan 2026, 23:53 UTC15 viewsread 12 August 2026
Современная схема передачи звука в сети: 🎤 ↓ Запись аудио ↓ Opus кодек ↓ UDP пакеты ↓ WebRTC ↓ Интернет ↓ WebRTC ↓ Opus decode ↓ 🔊
3 Jan 2026, 23:17 UTC13 viewsread 12 August 2026
Example of the method in golang package main import "fmt" type Contact struct { name string age int } func (x Contact) welcome() { fmt.Println(x.name) fmt.Println(x.age) } func main() { x := Contact{"James", 42} x.welcome() }
29 Dec 2025, 23:07 UTC15 viewsread 12 August 2026
Command for generete dependencies on the front protoc ` -I src/proto ` --plugin=protoc-gen-ts=.\node_modules\.bin\protoc-gen-ts.cmd ` --ts_out src/generated ` --ts_opt generate_dependencies ` --ts_opt long_type_string ` src/proto/*.proto
29 Dec 2025, 17:22 UTC11 viewsread 12 August 2026
But... we should add network for both containers (back-server and envoy): docker network connect lystivka-network envoy docker network connect lystivka-network back-server
29 Dec 2025, 17:21 UTC10 viewsread 12 August 2026
Build envoy docker run -d --name envoy -v /root/lystivka/envoy/envoy.yaml:/etc/envoy/envoy.yaml -p 8080:8080 -p 9901:9901 envoyproxy/envoy:v1.27.1 && docker network connect lystivka-network envoy
29 Dec 2025, 17:20 UTC8 viewsread 12 August 2026
Example of the valid Envoy yaml config static_resources: listeners: - name: listener_0 address: socket_address: address: 0.0.0.0 port_value: 8080 filter_chains: - filters: - name: envoy.filters.network.http_connection_manager typed_config: '@type': type.googleapis.com/envoy.extensions.filters.network.http_connection_manag…
15 Jun 2025, 10:13 UTC20 viewsread 12 August 2026
Photo
#js
15 Jun 2025, 09:45 UTC16 viewsread 12 August 2026
Here an example of Promise.all: const user = await getUser(); const products = await getProducts(); const [user, products] = await Promise.all([getUser(), getProducts()]); A better way is to use Promise.allSettled() instead, because Promise.all() works only if all requests are successful; it fails if even one fails. const [userResult, productsResult] = await Promise.allSettled([ getUser(), getProducts() ]); …
18 May 2025, 20:00 UTC27 viewsread 12 August 2026
Photo
Core principles behind the architecture ✅ Feature-first: Components, hooks, services, and types scoped by domain (features/products, features/users) ✅ Reusable UI: Centralized, shared components & layouts (components/common, components/layouts) ✅ Typed API layer: Service clients with robust error handling (services/apiClient.ts, errorHandler.ts) ✅ Modular State Management: Redux Toolkit slices, hooks, and scalable s…
7 Feb 2025, 11:32 UTC68 viewsread 12 August 2026
Как подтянуть определенные папки в проект vscode 1. Создаем файл с расширением: .code-workspace 2. Внутри файла прописываем, какие папки подтянуть: { "folders": [ { "path": "admin_client" }, { "path": "main_client" }, { "path": "server" }, { "path": "ms/auth" }, { "path": "ms/content" }, { "path": "ms/funds" }, { "path": "…
3 Feb 2025, 01:28 UTC56 viewsread 12 August 2026
Новое полезное выражение: const lastKey = Object.keys(setting || {})?.at(-1); делает тоже самое, что и: const lastKey = Object.keys(setting)[Object.keys(setting).length - 1]; .. но делает аккуратнее и красивее #js #javascript
Showing the 12 most recent of 20 posts we hold for @redirexStudio. 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Programmer Base” (@redirexStudio), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/redirexStudio.
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.