#twohourslispperday
Live, measured metrics for the hashtag #twohourslispperday from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #twohourslispperday
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-29 14:39 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-29 14:39 UTCNo related tags with measured usage found for #twohourslispperday.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 14:39 UTCEverything below is measured over the latest 12 public posts (spanning ~575 hours).
Posting hours (UTC) — busiest: 23:00
Languages: English (12)
Avg boosts / post: 1.3
Top of the latest posts
@nutilius apropos #twoHoursLispPerDay would you merge request a subdirectory like the first two into https://codeberg.org/j9000/lispusers with the beginnings of a package for READing files via 'read-delimited-list, and probably lisp path wi
Base #lisp seems to be like assembly language if you operate on strings (see split-sequence …) 😀🙈#twohourslispperday
#lisp is really different language: setq, let, open read-line, close … and only one line from file was read :-). But where is the parsing (string op), comparing (string op), extracting (string op) … long way before me :-) #twohourslispperda
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/twohourslispperday