#letscode
Live, measured metrics for the hashtag #letscode from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #letscode
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 18:48 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 18:48 UTCNo related tags with measured usage found for #letscode.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 18:48 UTCEverything below is measured over the latest 40 public posts (spanning ~8781 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (31)
Avg boosts / post: 2.7
Top of the latest posts
New video for Patrons: Let's Code MS DOS 0x38: Huge Pointers in Turbo C In MS DOS you can only access up to one Megabyte of memory easily, on an original PC or XT. This memory in turn is segmented, so accessing more than 64K at a time becom
Turbo C Debugger can identify when a variable points into video RAM. Nice. #turboc #msdos #letscode
The original VGA card used 8-bit indexed color modes to generate 256 color graphics. This is completely not useful for cross fading images. If you are interested in how you can still achieve this, check out my latest #letscode #msdos video:
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/letscode