#elixirdev
Live, measured metrics for the hashtag #elixirdev from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #elixirdev
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-28 20:41 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-28 20:41 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 20:41 UTCEverything below is measured over the latest 3 public posts (spanning ~23233 hours).
Posting hours (UTC)
Languages: English (1)
Avg boosts / post: 0
Used together with
Top of the latest posts
something the elixir book i'm reading said was to give good names to the functions. i'm not sure any more how exactly they said it, but something like that. But then they do something i've seen in pleroma too, which is using "maybe_do_thing
probably a lot of work, but i'm thinking about alternate database options for pleroma quetzal. postgres is fine, but what about couchdb? or riak? what if the whole system could run on an OTP cluster? i want to make local social graph analys
Huh, apparently elixir can do nested maps. I didn't know that one. Since it's immutable, you can't do something like conn.assigns.user.tags = []. But it has a put_in function, such that you can do (among other things) conn = conn.assigns.us
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/elixirdev