#trustcor
Live, measured metrics for the hashtag #trustcor from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #trustcor
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-30 04:09 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-30 04:09 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-30 04:09 UTCEverything below is measured over the latest 14 public posts (spanning ~889 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (11) · German (3)
Avg boosts / post: 1.9
Top of the latest posts
When the allegations about #Trustcor first surfaced I thought, you know, maybe people are putting two and two together. However from the thread it’s pretty clear they can’t answer simple questions, and shouldn’t be a trusted root CA. https:
@filippo Has @alpinelinux distrusted #TrustCor yet?
The python-certifi maintainers seem to have requested and received a CVE for removing #TrustCor roots from their ca-bundle. Noticed our package does not rely on our system-wide CA bundle and as such does not respect reconfiguration done thr
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/trustcor