#crlf
Live, measured metrics for the hashtag #crlf from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #crlf
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 13:33 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 13:33 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 13:33 UTCEverything below is measured over the latest 7 public posts (spanning ~36362 hours).
Posting hours (UTC)
Languages: English (7)
Avg boosts / post: 0.3
Top of the latest posts
Back on getting sync working on Windows in Site.js. I think I finally grok how paths and line-endings work via cygwin and so the next step is to integrate this into the binary and patch it in. What a world of hurt. PS. Documented it all her
Many people gave feedback, too many sites would not accept "just LF" in http headers, and Richard Hipp changed the proposal: https://fossil-scm.org/home/ext/stop-requiring-crlf.md #cr #lf #nl #crlf #SQLite
Call to action by Richard Hipp, best known as creator of #SQLite, to stop using the carriage-return/linefeed (CRLF) sequence alltogether. Linefeed (LF) is never used as "just a linefeed", we better rename the U+000a character to what it is
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/crlf