#interlispd
Live, measured metrics for the hashtag #interlispd from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #interlispd
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 20:36 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 20:36 UTCNo related tags with measured usage found for #interlispd.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 20:36 UTCEverything below is measured over the latest 4 public posts (spanning ~17412 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 1.8
Top of the latest posts
@interlisp @nosrednayduj @dougmerritt @jlamothe @alexshendi @rat @pkw @mdhughes @sacha @kentpitman @prahou Thanks everyone and a special thanks @masinter ! It was a pleasure and honor to to talk with you for an hour. https://larrymasinter.n
@oantolin @zyd @falken @jesus I *think* the editor in BBC #Lisp was just called 'edit'; the editor in Cambridge Lisp was invoked as 'fedit' when editing functions, and I *think* that was pretty much the lifted direct from Portable Standard
@iska I guess you've never heard of #InterlispD? Though I guess you'd argue that a bytecode VM implemented as microcode isn't a kernel or something. Outside of machines specifically designed for Lisp, a lot of Lisp OSes didn't run on bareme
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/interlispd