Channel
@mundoJS
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
708subscribers
+0 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001057093904 |
|---|---|
| Type | Channel |
| Username | @mundoJS |
| Description | Canal sobre tudo que envolve javascript. |
| Created | Between 1 May 2016 and 28 February 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/mundoJS |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 16:36 | 708 | no change |
| 5 Aug 2026, 23:07 | 708 | first reading |
20 posts held, back to 25 April 2026 — 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.
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.
| Window | Rolling 30 days · latest post in window 23 July 2026 |
|---|---|
| Posts held | 20 (25 April 2026 – 23 July 2026) |
| Views total | 228 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 16:36 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.
Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
46 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 39.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 18 | 39.1% | |
| ❤ | 9 | 19.6% | |
| 👍 | 8 | 17.4% | |
| 😢 | 5 | 10.9% | |
| 😱 | 4 | 8.70% | |
| 🤩 | 2 | 4.35% |
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 15 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 46reactions 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 25 April 2026 to 23 July 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.
https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/ O TypeScript 7.0 substitui o compilador em JavaScript por uma implementação nativa em Go, com paralelismo e suporte a LSP. A Microsoft relata builds entre 8 e 12 vezes mais rápidos, menor consumo de memória e melhorias expressivas na velocidade e estabilidade do editor, do modo watch e de grandes monorepos. A versão mantém compatibilidade com o Ty…
❤3🔥1
https://bun.com/blog/bun-in-rust Bun está migrando de Zig para Rust principalmente por estabilidade: a equipe concluiu que muitos bugs recorrentes vinham de gerenciamento manual de memória, como use-after-free, double-free e vazamentos em caminhos de erro. Zig continua sendo elogiado como essencial para a criação inicial do Bun, mas Rust oferece garantias melhores via Drop, borrow checker e ferramentas como Miri, to…
👍3
https://code.visualstudio.com/blogs/2026/06/26/iterating-faster-with-ts-7
https://blog.emberjs.com/ember-released-7-0/ O Ember 7.0 foi lançado como uma major focada em limpeza: não traz novas APIs públicas nem novas depreciações, mas remove APIs já depreciadas no ciclo 6.x e inclui correções de bugs. A versão anterior, Ember 6.12, passa a ser LTS, e a recomendação de upgrade é chegar primeiro à 6.12, eliminar todos os avisos de depreciação e só então migrar para a 7.0. Entre as remoções …
https://voidzero.dev/posts/voidzero-cloudflare A VoidZero será incorporada à Cloudflare, mantendo Vite, Vitest, Rolldown, Oxc e Vite+ como projetos open source sob licença MIT. Evan You e a equipe continuarão liderando essas ferramentas, agora com suporte da Cloudflare para sustentar o desenvolvimento e fortalecer a integração entre o ecossistema Vite e a plataforma de deploy da empresa. A decisão vem após a VoidZe…
🔥6
https://deno.com/blog/v2.8
❤2
O artigo analisa o relatório "Software Supply Chain Security State of the Union 2026" da JFrog, destacando que o ano anterior redefiniu completamente a arquitetura das ameaças à cadeia de suprimentos de software. A principal conclusão é que o foco dos ataques se deslocou radicalmente para o início do ciclo de desenvolvimento (upstream), atingindo as ferramentas e o ambiente diário de quem programa. O relatório alert…
https://socket.dev/blog/laravel-lang-compromise Pacotes de terceiros do projeto Laravel Lang foram comprometidos com um backdoor de execução remota em mais de 700 versões, afetando laravel-lang/lang, http-statuses, attributes e actions. O ataque parece ter explorado o processo de release da organização, com criação rápida e coordenada de tags em 22 e 23 de maio de 2026, e não envolve o framework Laravel oficial. O…
😱3🔥1
https://socket.dev/blog/antv-packages-compromised Um ataque ativo de supply chain comprometeu centenas de versões de pacotes npm ligados ao ecossistema @antv e à conta de maintainer atool, incluindo bibliotecas populares como @antv/g2, @antv/g6, @antv/x6, @antv/l7 e echarts-for-react. A Socket associa o caso à campanha Mini Shai-Hulud, com 639 versões comprometidas em 323 pacotes nessa nova onda, ampliando uma camp…
😢2
https://www.stepsecurity.io/blog/mini-shai-hulud-is-back-a-self-spreading-supply-chain-attack-hits-the-npm-ecosystem O ataque Mini Shai-Hulud voltou em uma nova onda contra o ecossistema npm, comprometendo pacotes legítimos — principalmente do TanStack, mas também de UiPath, DraftLab, Mistral, OpenSearch e outros. A campanha publicou versões maliciosas usando o próprio pipeline de release via GitHub Actions, com tok…
😢3🔥1
https://turborepo.dev/blog/2-9 Turborepo 2.9 foca em qualidade, performance e adoção em monorepos grandes. A principal melhoria é a redução do Time to First Task, com ganhos de até 96% dependendo do tamanho e complexidade do repositório. A versão também estabiliza o turbo query, permitindo consultar o grafo do monorepo via GraphQL e atalhos como turbo query affected e turbo query ls. A release facilita a adoção em …
https://zero-native.dev/ zero-native é um framework para criar apps desktop nativos usando Zig no backend e uma UI web via WebView. A proposta é gerar binários pequenos, usar pouca memória e evitar o peso de runtimes embutidos, permitindo escolher entre WebView do sistema para leveza ou Chromium via CEF para consistência visual. O projeto destaca rebuilds rápidos, integração direta com bibliotecas C, bridge entre J…
👍1
Showing the 12 most recent of 20 posts we hold for @mundoJS. 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.
Citation-graph rank — 358,991 of 1,160,990entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 6 August 2026 — this entry's latest reading, not the date you are reading this.
“Mundo JS” (@mundoJS), 708 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/mundoJS.
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.