#weddingplanner
Live, measured metrics for the hashtag #weddingplanner from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #weddingplanner
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 05: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-28 05:33 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 05:33 UTCEverything below is measured over the latest 28 public posts (spanning ~60303 hours).
Posting hours (UTC) — busiest: 08:00
Languages: English (22) · Italian (2) · Spanish (1) · German (1)
Avg boosts / post: 0.2
Top of the latest posts
We've refactored the UI of the expenses table to include the payments breakdown in a collapsible section of each row. The previous version required the user to open a modal, where the list of payments was mixed together with the form to cre
In #LibreWeddingPlanner we have a dashboard where you can find the big numbers at a glance. Want to learn more about this feature? Check out the documentation: https://libreweddingplanner.org/docs/Features/dashboard #FOSS #FreeSoftware #Ope
We've just released a new reports feature! 📑 🥳 👓 Right now there is just one report (catering 🍗), but we plan to add more as they are needed. Is there a report you're missing? Let us know so we can add it! Find the docs of this feature
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/weddingplanner