#blogpress
Live, measured metrics for the hashtag #blogpress from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #blogpress
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-30 00: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-30 00:41 UTCNo related tags with measured usage found for #blogpress.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-30 00:41 UTCEverything below is measured over the latest 5 public posts (spanning ~8939 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0
Used together with
Top of the latest posts
#blogpress checkpoint: I managed to get the "tiled" tag of my blog converted from the last (mostly useless) #GoogleTakeout from June. It's looking satisfying on-screen, but I can't find a decent way to turn it into a printable pdf this far:
#blogpress thought ... converting into some experiment. Many posts contain parts that would be useful for a chapter (say, one about tiled game engines) but also parts that don't quite fit. So how about having <span> or <div> tags assigning
ah ? An interesting finding for #simple.css powered #blogpress effort: if I wrap each individual blog post between <section> tags, - I no longer have some part of the post body going to the margin - I no longer have pictures eating up space
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/blogpress