#regulatingcode
Live, measured metrics for the hashtag #regulatingcode from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #regulatingcode
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 19:56 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 19:56 UTCNo related tags with measured usage found for #regulatingcode.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 19:56 UTCEverything below is measured over the latest 3 public posts (spanning ~59936 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0
Used together with
Top of the latest posts
Almost impossible to achieve slower enforcement of #magicAI illegal data usage but EU is going to try ... Instead of #RegulatingCode RE: https://bsky.app/profile/did:plc:wk7sybhegd37i7ljsltxbef6/post/3m5byskvbd225
Is it worth reminding everyone that we wrote about the solutions to digital dominance in #RegulatingCode (2013) & #InternetCoregulation (2011), based on multi year multidisciplinary multinational (multiple) studies for the European Commissi
RT @[email protected] Good piece. @[email protected] uses this case to illustrate the problems of over-broad computer fraud and anti-circumvention rules for competition. But it’s equally an argument for mandated interoperability of eg d
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/regulatingcode