#webcal
Live, measured metrics for the hashtag #webcal from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #webcal
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-09-13 00: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-09-13 00:08 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-13 00:08 UTCEverything below is measured over the latest 12 public posts (spanning ~43094 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (7) · German (3) · French (2)
Avg boosts / post: 1
Top of the latest posts
Part 1 of my #GNOMECalendar #webcal subscriptions #UX bugfixing trilogy has been merged today! No more duplicate calendars created by accident when adding a web calendar URL 🥳 https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/
One of the fixes merged in GNOME Calendar tonight is @tytan652's nice solution for those elusive "405: Method Not Allowed" errors when subscribing to some online calendars that had non-spec-compliant line breaks. It was one of my last known
@InfNITSH Ich muss mich korrigieren, der WebCal wird in der Tabelle der eigenen Termine (oc_calendarobjects) gespeichert und die Spalte calendartxpe <> 0 Testweise habe ich in der Datenbank bei den Feed-Terminen TRANSP: TRANSPARENT zu TRANS
What “webcal” means
WikipediaWebcal is a uniform resource identifier (URI) scheme for accessing iCalendar files.
“Webcal” on Wikipedia (CC BY-SA) →#webcal across platforms
every network with a public tag surfaceFollow #webcal 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/webcal