#occam

Live, measured metrics for the hashtag #occam 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 #occam

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.

$1,129.43/ year · 5-character #name
Claim #occam — $1,129.43/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
2
Uses / 7 days
Mastodon
1
Accounts / 7 days
Mastodon
40
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 40
0.3
Avg reactions / post
Mastodon · last 40
—
Reddit posts / month
Reddit search
—
Open-web mentions
hashtag.org Firehose

Day-by-day usage

measured · mastodon.social (Mastodon public tags API) · fetched 2026-11-02 16:02 UTC
0
10-27
0
10-28
0
10-29
0
10-30
2
10-31
0
11-01
0
11-02

2 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.

Related hashtags

measured · mastodon.social (Mastodon public search API) · fetched 2026-11-02 16:02 UTC
#occamlang
2 uses · 1 accounts / 7d
#occamsrazor
0 uses · 0 accounts / 7d
#occamlist
0 uses · 0 accounts / 7d
#OccamsLaser
0 uses · 0 accounts / 7d
#occam_97
0 uses · 0 accounts / 7d
#OccamsFuckingRazor
0 uses · 0 accounts / 7d
#occamfi
0 uses · 0 accounts / 7d
#OccamsRazorFAIL
0 uses · 0 accounts / 7d
#OccamsRazorIsBlunt
0 uses · 0 accounts / 7d
#occamsrazer
0 uses · 0 accounts / 7d
#OccamRazer
0 uses · 0 accounts / 7d
#occamsrazor101
0 uses · 0 accounts / 7d

Live pulse

measured · mastodon.social (Mastodon tag timeline) · fetched 2026-11-02 16:02 UTC

Everything below is measured over the latest 40 public posts (spanning ~8572 hours).

Posting hours (UTC) — busiest: 11:00

00:0012:0023:00

Languages: English (35) · German (2) · Japanese (2)

Avg boosts / post: 0.3

Top of the latest posts

  • I've been quiet for about a year. Life has been 'busy' and I've been updating my mental firmware. But I'm feeling more social now, so I'm back. My current project is an Occam compiler - as used on Transputers. The compiler generates a form

    Bread80@[email protected]♥ 2↻ 22026-10-02 11:51 UTCView post →

  • So, concurrent reads are allowed: INT x,y,z : SEQ x, y, z := 10,20,30 PAR x := z y := z LOG x,y,z But concurrent writes give a compile error: INT x,y,z : SEQ x, y, z := 10,20,30 PAR x := z x := y LOG x,y,z As do read/write combos: INT x,y,z

    Bread80@[email protected]♥ 1↻ 02026-10-20 14:57 UTCView post →

  • Output results are currently incorrect because I've yet to fixup the variable addresses across processes but otherwise the code is running correctly. #occam #occamlang

    Bread80@[email protected]♥ 1↻ 02026-10-15 16:23 UTCView post →

#occam across platforms

every network with a public tag surface

Follow #occam 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.

X (Twitter) ↗Instagram ↗TikTok ↗Facebook ↗LinkedIn ↗YouTube ↗Threads ↗Bluesky ↗Mastodon ↗Reddit ↗Pinterest ↗Tumblr ↗

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/occam