#Culinaryhistory
Live, measured metrics for the hashtag #Culinaryhistory from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #culinaryhistory
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-10-03 13:29 UTC2 uses by 2 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-10-03 13:29 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-10-03 13:29 UTCEverything below is measured over the latest 40 public posts (spanning ~3457 hours).
Posting hours (UTC) — busiest: 19:00
Languages: English (40)
Avg boosts / post: 0.9
Top of the latest posts
A recipe for fish in #aspic, and some thoughts on why Middle German insists on using the same words for jellies and bread sauces. Because of course it does. https://www.culina-vetus.de/2026/09/19/fish-in-jelly/ #culinaryhistory #foodhistory
The Solothurn S 392 recipe collection includes a dish that is basically beef and bacon in scrambled eggs. No maple syrup on top because they hadn't discovered America yet, but I guess you could have waffles. https://www.culina-vetus.de/2026
Being sick sucks, but having time for things is a comfort. The #fourteenth-century Rossauer Tischzucht explains how to eat soft-boiled eggs. https://www.culina-vetus.de/2026/07/19/a-fourteenth-century-poem-of-table-manners/ #culinaryhistory
#culinaryhistory across platforms
every network with a public tag surfaceFollow #culinaryhistory straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/culinaryhistory