#improperdisgorgementdemands
Live, measured metrics for the hashtag #improperdisgorgementdemands from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #improperdisgorgementdemands
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-10-19 06:31 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-10-19 06:31 UTCNo related tags with measured usage found for #improperdisgorgementdemands.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-19 06:31 UTCEverything below is measured over the latest 29 public posts (spanning ~10655 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (29)
Avg boosts / post: 0.7
Top of the latest posts
Entropic v. Cox - Plaintiff states, in a joint FRCP 26(f) statement, that it is "eligible to recover" design patent damages for utility patent infringement: https://www.scribd.com/document/663718240/Entropic-v-Cox-26-f-Report No, it is not.
And as you all know, § 289 damages are only available for certain acts of design patent infringement. They are not available for any acts of utility patent infringement. #ImproperDisgorgementDemands
In this #ScheduleA case, Floatup (represented by Doniger / Burroughs) asserts a utility patent, but calls--and treats it like--a design patent: https://www.scribd.com/document/699275045/Floatup-v-Schedule-A-Motion-for-TRO-sans-exhibits It i
#improperdisgorgementdemands across platforms
every network with a public tag surfaceFollow #improperdisgorgementdemands 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/improperdisgorgementdemands