Telegram RegisterThe public register of Telegram
Telegram profile photo for 🧨 Web Reactiva · Programa con IA

Channel

🧨 Web Reactiva · Programa con IA

@webreactiva

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

1,074subscribers

+3 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001123468176
TypeChannel
Username@webreactiva
CreatedBetween 1 June 2017 and 30 September 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live25 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/webreactiva

Growth

1,0711,0761,073.56 August 2026 — 1,071 subscribers6 August 2026 — 1,071 subscribers10 August 2026 — 1,074 subscribers13 August 2026 — 1,073 subscribers16 August 2026 — 1,075 subscribers19 August 2026 — 1,074 subscribers22 August 2026 — 1,076 subscribers25 August 2026 — 1,074 subscribers1,0746 August 202625 August 2026
8 measurements spanning 19 days, net +3. 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 1,070–1,077 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 16:471,074-2
22 Aug 2026, 20:181,076+2
19 Aug 2026, 13:221,074-1
16 Aug 2026, 19:461,075+2
13 Aug 2026, 05:241,073-1
10 Aug 2026, 07:521,074+3
6 Aug 2026, 20:021,071no change
6 Aug 2026, 19:571,071first reading

Engagement

20 posts held, back to 9 July 2026the 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.

ERR · 30 days
18.8%
avg views ÷ 1,074 subscribers
Avg views / post
202
7 posts measured
Reaction rate
0.74%
reactions ÷ views · ER floor
Posts in window
7
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 3 of 7 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (9 July 20266 August 2026)
Views total1,415
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 20:02 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

7 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 57.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
457.1%
👍228.6%
🤩114.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 4 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 7reactions 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 9 July 2026 to 6 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

6 Aug 2026, 19:03 UTC35 viewsread 6 August 2026

Qué datos no compartir con un agente de IA (y por qué) Qué sale de tu máquina en cada sesión, cuánto lo guarda cada proveedor y cómo ponerle límites 🧨 https://www.webreactiva.com/blog/que-no-compartir-con-agentes-ia

5 Aug 2026, 19:03 UTC125 views2 reactionsread 6 August 2026

AGENTS.md: dónde vive cada regla de tu agente de IA Prompt, regla y contexto: dónde va cada uno y cómo auditar el fichero de instrucciones que ya tienes 🧨 https://www.webreactiva.com/blog/agents-md-reglas-contexto

2

4 Aug 2026, 19:03 UTC158 viewsread 6 August 2026

Open Design: la alternativa open source a Claude Design 162 skills, 25 agentes soportados y 151 design systems para convertir tu CLI en motor de diseño 🧨 https://www.webreactiva.com/blog/open-design

31 Jul 2026, 19:03 UTC290 views1 reactionsread 6 August 2026

Orca: el IDE para ejecutar agentes de código en paralelo Worktrees aislados, Design Mode y una CLI que los propios agentes usan para pilotar el editor 🧨 https://www.webreactiva.com/blog/orca

1

30 Jul 2026, 19:03 UTC276 viewsread 6 August 2026

Convierte cualquier libro en una skill (book-to-skill) Compila libros, PDFs y documentación en skills que tu agente consulta con 24-51 veces menos tokens 🧨 https://www.webreactiva.com/blog/book-to-skill

29 Jul 2026, 19:03 UTC270 viewsread 6 August 2026

MCP stateless: cómo funciona el protocolo sin sesiones Por qué el protocolo eliminó las sesiones y qué implica para tu servidor en producción 🧨 https://www.webreactiva.com/blog/mcp-stateless

28 Jul 2026, 19:03 UTC261 views2 reactionsread 6 August 2026

Qué son los modelos de pesos abiertos (y qué no te dan) La diferencia real entre open weights y open source, qué dicen las licencias y cómo elegir uno sin pegarte un tortazo 🧨 https://www.webreactiva.com/blog/modelos-pesos-abiertos

👍2

23 Jul 2026, 19:03 UTC360 views2 reactionsread 6 August 2026

Agent loops: ¿Cómo montar un sistema de agentes autónomos? Del loop suelto a una flota: manager/worker, cerebro compartido, guardarraíles y cómo medirlo 🧨 https://www.webreactiva.com/blog/agent-loops

1🤩1

22 Jul 2026, 19:03 UTC321 viewsread 6 August 2026

Cómo trabajar con agentes de programación en Cursor (plan, debug y revisión) El método planificar-implementar-verificar-revisar para dejar de corregir cada respuesta del agente 🧨 https://www.webreactiva.com/blog/cursor-agentes

21 Jul 2026, 19:03 UTC327 viewsread 6 August 2026

Graph engineering: el siguiente paso después del loop engineering Nodos, aristas, joins y blast radius para orquestar muchos agentes sin morir en el intento 🧨 https://www.webreactiva.com/blog/graph-engineering

20 Jul 2026, 19:03 UTC283 viewsread 6 August 2026

LazyPi: instala Pi con todo listo en un solo comando Deja el agente minimalista de Mario Zechner con 60+ skills, MCP y memoria sin configurar nada 🧨 https://www.webreactiva.com/blog/lazypi

19 Jul 2026, 19:03 UTC264 viewsread 6 August 2026

Qué es el nuevo Open Interpreter y por qué imita otros harness El fork de Codex en Rust para exprimir modelos abiertos baratos con emulación de harness 🧨 https://www.webreactiva.com/blog/openinterpreter

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

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

“🧨 Web Reactiva · Programa con IA” (@webreactiva), 1,074 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/webreactiva.

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.