#qgis2web
Live, measured metrics for the hashtag #qgis2web from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #qgis2web
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-29 13:59 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-29 13:59 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 13:59 UTCEverything below is measured over the latest 26 public posts (spanning ~61081 hours).
Posting hours (UTC) — busiest: 08:00
Languages: English (22) · German (3) · Polish (1)
Avg boosts / post: 3.1
Top of the latest posts
I cannot tell you how happy I am that Andrea has just developed and released v 3.19.0 of #qgis2web, in which AT LAST layer groups are properly supported. This is the single biggest longstanding issue which affected the plugin, and it's a hu
#qgis2web announcement! The qgis2web repository has moved. It is now no longer in my Github account, but under a new qgis2web organization. This should be largely transparent, but take care if you have a local clone - check your upstream re
More terrific #qgis2web news: as well as Andrea starting work on the plugin, @osgeouk have granted him funding to achieve some specific improvements. Thanks to my colleagues on the committee! https://plugins.qgis.org/plugins/qgis2web/#plugi
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/qgis2web