Channel
@userver_news
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
314subscribers
+4 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001581355642 |
|---|---|
| Type | Channel |
| Username | @userver_news |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 25 August 2026 |
| On Telegram | t.me/userver_news |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 00:36 | 314 | +1 |
| 16 Aug 2026, 15:03 | 313 | +3 |
| 8 Aug 2026, 07:46 | 310 | no change |
| 8 Aug 2026, 00:03 | 310 | first reading |
20 posts held, back to 17 July 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 20 posts for this entry, the most recent from 1 July 2026. An engagement rate over an empty window would be a number about nothing.
226 reactions across 20 posts, in 7 distinct kinds. The most used accounts for 72.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 163 | 72.1% | |
| ❤ | 33 | 14.6% | |
| ❤🔥 | 12 | 5.31% | |
| 👍 | 10 | 4.42% | |
| 🎉 | 4 | 1.77% | |
| 🎄 | 3 | 1.33% | |
| 🤝 | 1 | 0.442% |
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 20 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 226reactions 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 17 July 2025 to 1 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.
⚙️ Optimizations and fixes ▫️ Reduced binary size across universal and related libraries by moving some definitions out of headers, reducing template/codegen bloat, and tuning debug-info generation, saving approximately 0.3–1% in tested binaries. ▫️ Optimized gRPC server to parse and serialize messages from raw grpc::ByteBuffer, allowing congestion control to reject calls before parsing unary request payloads. ▫️ Imp…
🔥8
🌟 Added engine::AwaitableToken and the engine::Awaitable concept for integration with engine::WaitAny, engine::WaitAnyContext and engine::WaitAllChecked. 🌟 Replaced TryGetContextAccessor() hooks with GetAwaitableToken(). This API is now stable, you can create your own awaitables by implementing GetAwaitableToken(). 🌟 Added a second stage to graceful shutdown for server http and ugrpc: after failing health checks, lis…
🔥4
#release 3.1 🌟 chaotic OpenAPI generator: Added comprehensive OpenAPI code generation for server-side HTTP handlers and corresponding config.yaml. Support with multiple content types, request body parsing, logging customization, and URL masking for sensitive parameters. 🌟 Added ScyllaDB driver: asynchronous C++ driver for ScyllaDB and Apache Cassandra with full CQL support, typed operations, and lightweight transact…
🔥9
#release 3.0 Big new features since the v2.0: 🌟 Chaotic - codegen parsers and serializers by JSON schema 🌟 Easy - library for single file prototyping. 🌟 Improved Kafka driver is now widely used and has Platinum Tier. 🌟 OpenTelemetry Protocol (OTLP) support. 🌟 Logging format customization, including JSON logging. 🌟 Numerous build improvements, including MacOS, Gentoo, Arch, Alpine. Improved Conan support. 🌟 SQLite Dr…
🔥13
⚙️ Detailed diff against v2.16: ▫️ Support of C++17 is removed. ▫️ Updated moodycamel to 1.0.5. Many thanks to Vasily Sviridov for the PRs. ▫️ Supported ydb::TableClient::RetryTx handle for execution lambda in a transaction with automatic retries. ▫️ MultiIndex LRU Container is now optimized and ready to use. Many thanks to hzhdlrp for the contributions! ▫️ Added heartbeat and message headers support for RabbitMQ. Ma…
🔥9
⚙️ Optimizations and fixes ▫️ New engine::WaitAnyContext (engine::MakeWaitAny) and engine::WaitAllChecked waiting primitives optimized for usage in loops. ▫️ Kafka: Reuse consumer after a user exception. ▫️ Redis: Optimized statistics storage - removed most of per-shard and per-instance statistics that are rarely used to save memory, CPU and network bandwidth. ▫️ Prevent an unnecessary copy inside the ServerImpl::Wri…
🔥6❤3🎉3
#release 2.16 🌟 Support of C++17 is deprecated and will be removed in one on the next releases. C++20 is the default for userver for quite some time. Use C++20 or even a more modern C++. 🌟 New readiness notification flow for tasks, futures, events and other awaitable objects. It provides a lightweight and efficient framework for more efficient implementation of waiting objects/methods like engine::WaitAny, engine::…
🔥6🎉1
#release 2.15 🌟 Support of C++17 is deprecated and will be removed in one on the next releases. C++20 is the default for userver for quite some time. Use C++20 or even a more modern C++. 🌟 Deadlock detector is now enabled by default in testsuite runs. The behavior can be changed by overriding the pytest_userver::plugins::config::userver_deadlock_detector_mode() fixture. 🌟 Redis driver internals were rewritten to rem…
🔥10❤2👍2
⚙️ Optimizations ▫️Drastically reduced memory usage by components::Redis statistics/metrics in case of network topology changes or multiple Valkey/Redis nodes going down. ▫️Stacktrace capturing via boost::stacktrace / std::stacktrace in Boost.Context became more than x50 faster on LLVM version of libunwind. Other unwinding libraries could have also gained profit. 🛠 Misc ▫️More docs for the USERVER_LOG_DYNAMIC_DEBUG,…
🔥18
#release 2.14 🌟 Added a ugrpc::RichStatus builder for creating rich gRPC error statuses with structured details following Google's error model 🌟 Added a utils::statistics::RegisterWriterScope for safe and easy registration of statistics. 🌟 No more need to call CacheUpdateTrait::StartPeriodicUpdates() from your caching components. 🌟 Implemented a Multi Index LRU container, thanks to hzhdlrp. 🌟 Statement name is now l…
🔥10
▫️Kafka is now more accurate in computing message time spent in kafka::ConsumerComponent queue. ▫️utils::statistics::RecentPeriod now does not lose precision under heavy contention. ▫️Added functionality to Dump coroutines in runtime ▫️Added DeadlockDetector that can be enabled via coro_pool.deadlock_detector option in components::ManagerControllerComponent. ▫️Added storages::mongo::Transaction ▫️Added server::middle…
🔥20🎄3👍1
#release 2.13 🌟 Recursive subscriptions on dynamic configs now work without deadlocks. 🌟 Added virtual method server::handlers::HttpHandlerBase::GetUrlForLogging() for custom URL logging. 🌟 Support parsing of HTTP keys without =, i.e. /endpoint?key1&key2. Many thanks to Norlin for the PR! 🌟 Dots in tag keys of logs and spans are now not changed to underscores. HTTP client/server spans are now written according to OT…
❤🔥12
Showing the 12 most recent of 20 posts we hold for @userver_news. 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.
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.
“userver framework news channel” (@userver_news), 314 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/userver_news.
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.