#GeoFenceWarrant
Live, measured metrics for the hashtag #GeoFenceWarrant from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #geofencewarrant
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-08-03 12:18 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-08-03 12:18 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-03 12:18 UTCEverything below is measured over the latest 8 public posts (spanning ~46393 hours).
Posting hours (UTC)
Languages: English (8)
Avg boosts / post: 0.4
Top of the latest posts
#AppealsCourt Sidesteps The Big Questions on #Geofence #Warrants The practical outcome of this sentence is clear: the evidence collected from a #geofencewarrant issued to Google can be used against the defendant in this case. But that is la
When faced with opposition, the U.S. Department of Justice and/or respective U.S. Attorney's offices would rather withdraw their warrant and move to seal the case rather than fact accountability. In some of the cases reviewed in the article
iam-py-test :transgender_flag: :neocat_flag_lesbian:@[email protected]♥ 0↻ 12025-02-27 00:34 UTCView post →Is This the End of #Geofence #Warrants? #Google announced this week that it will be making several important changes to the way it handles users’ “#LocationHistory” data. These changes would appear to make it much more difficult—if not impo
#geofencewarrant across platforms
every network with a public tag surfaceFollow #geofencewarrant 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/geofencewarrant