#expiration
Live, measured metrics for the hashtag #expiration from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #expiration
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 08:42 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 08:42 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 08:42 UTCEverything below is measured over the latest 35 public posts (spanning ~68871 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (33) · Spanish (1) · Chinese (1)
Avg boosts / post: 0.7
Top of the latest posts
Let’s Encrypt SSL certificate expiry warning emails If you use Let's Encrypt to secure the traffic to your web server, mailserver or other situations where you need a SSL-encrypted data exchange, you are probably using the dehydrated script
#signal #privacy #expiration I can't believe that. There is no fonctionnality to delete messages (text, images, videos) older than, for example, 6 months, one year, two years, and so on. Ephemeral message is not a solution: max is 4 weeks,
@EricAlper Yes, this is old. However: It did not have in-app purchases. Oh, it didn't come with #ads. It had no direct or indirect #expiration date where it stopped working altogether. It continued working even when its original #manufactur
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/expiration