#誤報

Live, measured metrics for the hashtag #誤報 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #誤報

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.

$11,525.77/ year · 2-character #name
Claim #誤報$11,525.77/yrBuy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
2
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 2
0
Avg reactions / post
Mastodon · last 2
Reddit posts / month
Reddit search
Open-web mentions
hashtag.org Firehose

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-08-24 05:52 UTC
0
08-18
0
08-19
0
08-20
0
08-21
0
08-22
0
08-23
0
08-24

0 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-24 05:52 UTC

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-24 05:52 UTC

Everything below is measured over the latest 2 public posts (spanning ~13306 hours).

Top of the latest posts

  • 英國電台「擺烏龍」宣布英王查理斯三世死訊 被裁定違反廣播規則 英國地方電台卡羅琳電台(Radio Caroline),因誤報英王查理斯三世(King Charles III […] The post 英國電台「擺烏龍」宣布英王查理斯三世死訊 被裁定違反廣播規則 appeared first on 棱角媒體. #最新 #熱話 #英國/歐洲 #Ofcom https://points-media.com/最新/英國電台「擺烏龍」宣布英王查理斯三世死訊-被裁/

    The Points 棱角@[email protected]002026-08-10 13:24 UTCView post →
  • #文春 の #誤報 だが、確か訂正はネットで記事が出てすぐに行われたはずだ。#橋下徹 が早くから指摘していたらしい。 それなのに、記事が出てから20日もたって、記者会見に出た400人もいる記者が誰もそれに気づかず、フジテレビが組織的に性接待をしているという前提で質問していたのがひどいと思う。 責任があるのは文春だけではない。文春に乗せられたマスコミに、文春を責める資格はないと思う。

    barlow2001@エアリプではなくぜひ直接リプ下さい@[email protected]002025-02-02 03:02 UTCView post →

#誤報 across platforms

every network with a public tag surface

Follow #誤報 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/誤報