#libcaca
Live, measured metrics for the hashtag #libcaca from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #libcaca
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 07:08 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 07:08 UTCNo related tags with measured usage found for #libcaca.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:08 UTCEverything below is measured over the latest 10 public posts (spanning ~61050 hours).
Posting hours (UTC)
Languages: English (8) · Catalan (1)
Avg boosts / post: 0.3
Top of the latest posts
gibt's eigentlich schon irgendwo Terminal-Software die "moderne" #Unicode-Glyphen zum Bild/Video-Rendern verwendet? Sowas wie #libcaca in den 2010ern, nur auch mit Dingen wie 🟧🟨🟩🟦🟪⬛️⬜️🟫?
OK I had the distinct impression that there were now tools that could “rasterize” images to characters (similar to #AAlib and #libcaca), but with more aggressive usage of #Unicode characters to achieve better results. I have tried #img2txt
@samir You could formulate the question otherwise, like if you are writing software, on a scale of 1 to 4, how pointless or harmful is it? And define pointless... like, #libcaca is uber-pointless but probably not harmful, compared to a vide
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/libcaca