#opensourcecompliance
Live, measured metrics for the hashtag #opensourcecompliance from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #opensourcecompliance
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 · mastodon.online (Mastodon public tags API) · fetched 2026-09-29 22:12 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-09-29 22:12 UTCNo related tags with measured usage found for #opensourcecompliance.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-09-29 22:12 UTCEverything below is measured over the latest 7 public posts (spanning ~32147 hours).
Posting hours (UTC)
Languages: English (5) · German (1) · Galician (1)
Avg boosts / post: 1.4
Top of the latest posts
"Witzig": Der chinesische #Autohersteller MG veröffentlicht nach Eingang einer #GPL-Klage eine SBOM. Darin enthalten: Der #FOSS-Trojaner #Teardroid 🙃 https://www.linkedin.com/feed/update/urn:li:activity:7485220057564786689/ #ChinaSpeed #Op
THE CLOSED-SOURCE SHACKLE: Analyzing Bambu Lab’s Approach to AGPL Compliance 2,695 words, 14 minutes read time. Bambu Lab took the open-source guts of 3D printing, forked the hell out of it under AGPLv3, built a slick empire on top, and the
Timo Perala (Nokia) will discuss #ORCWG during his #CRA talk at Open Source Summit Europe. Learn more about Timo's session: https://osseu2025.sched.com/event/25VmN/the-cra-where-are-we-six-months-after-its-approval-timo-perala-nokia?iframe=
#opensourcecompliance across platforms
every network with a public tag surfaceFollow #opensourcecompliance 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/opensourcecompliance