#memory_management
Live, measured metrics for the hashtag #memory_management from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #memory_management
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 · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 11:15 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 11:15 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:15 UTCEverything below is measured over the latest 17 public posts (spanning ~21465 hours).
Posting hours (UTC) — busiest: 19:00
Languages: Russian (16) · English (1)
Avg boosts / post: 0
Top of the latest posts
Time to look back 2025. In 2025, I made 2nd and 1st biggest changes to Linux kernel memory management subsystem among the 321 people, in terms of lines of changes (6,661 / 73,685 lines) and commits (199 / 1,870 commits). For the Linux kerne
OSDEV: Разработка аллокатора на С++ часть 3. Финальный аллокатор со списками свободных блоков В третьей статье пойдет речь уже о готовом аллокаторе который вполне пригоден для распределения памяти https://habr.com/ru/articles/1045692/ #алло
Segmentation Fault: как оно устроено? Segmentation fault - одна из тех ошибок, с которой сталкивался каждый, но мало кто разбирался что за ней стоит. В этой статье копаем глубже обычного: смотрим как ядро Linux понимает что произошло, какие
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/memory_management