#контекст_выполнения
Live, measured metrics for the hashtag #контекст_выполнения from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #контекст_выполнения
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mas.to (Mastodon public tags API) · fetched 2026-08-24 16:16 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-08-24 16:16 UTCNo related tags with measured usage found for #контекст_выполнения.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-08-24 16:16 UTCEverything below is measured over the latest 2 public posts (spanning ~4289 hours).
Posting hours (UTC)
Languages: Russian (2)
Avg boosts / post: 0
Top of the latest posts
Модель исполнения JavaScript по спецификации ECMAScript: call stack, контексты, окружения и замыкания Я довольно долго был уверен, что понимаю, как работает call stack. Ну а что там понимать? Положил кадр, снял кадр, LIFO. Потом открыл спец
contextvars: почему thread-local сломался в asyncio и как это починили В мире потоков всё было просто: threading.local() даёт каждому потоку свои данные. Request ID, текущий пользователь, database connection — положил в thread-local, достал
#контекст_выполнения across platforms
every network with a public tag surfaceFollow #контекст_выполнения straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/контекст_выполнения