#lispinterpreter
Live, measured metrics for the hashtag #lispinterpreter from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #lispinterpreter
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 02: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 02:39 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 02:39 UTCEverything below is measured over the latest 3 public posts (spanning ~6996 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0.7
Top of the latest posts
One Open-source Project Daily Pampy: The Pattern Matching for Python you always dreamed of. https://github.com/santinic/pampy #1ospd #opensource #functional #lispinterpreter #patternmatching #python #python3
Ah, yet another thrilling guide on writing a Lisp interpreter in Python—because who doesn't want to spend their weekend reinventing the wheel while pretending to understand Alan Kay's analogy? 🤓🔧 It’s like watching a cat chase its tail, b
🚀 Behold! The pinnacle of human achievement: squeezing an entire Lisp interpreter into a mere 750 lines of Odin! 🤯 Meanwhile, your project still can’t compile without a 1,000-line README. 🙈 And don’t miss the riveting drama of this maste
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/lispinterpreter