gossip

gossip · Data directory census

What gossip can draw on

Every kind of data the house has touched, organised by the source-bucket taxonomy and tagged by how usable it is, feeding four instruments across past, present and future. The boundary is the load-bearing part: aggregate culture in, person-targeting refused.

gossip data directory census map A hub-and-spoke map: the source-bucket taxonomy (Band A observation with seven buckets, plus supporting bands B counting, C audience, D mechanism, E access and proof) flows into the harvest and through a boundary gate that refuses person-targeting sources, then out to the four instruments Hindsight, the cultural climate, Decode and Foresight. Each bucket carries a usability glyph for how much of it is live. BAND A · OBSERVATION · THE EVIDENCE BANDS B · C · D · E · SUPPORTING A1 Utterance live · 5 platforms A2 Curation live · 3 lanes A3 Behaviour live · 4 series A4 Market live · 2 venues A5 Interpretation mixed · 1 of 2 lanes live A6 Record mixed · baseline + 24 collections A7 Solicited empty · the moat, 0 rows B Counting 1 of 2 counts live C Audience idle · anchors ready D Mechanism reference · Library E Access/proof live · proof gap THE HARVEST the house’s own feeds THE BOUNDARY + the copy law aggregate in, person-targeting out OUT OF BOUNDS social-analyzer intelx · breach dumps PAST Hindsight provenance · A6 · A2 PRESENT cultural climate deviation from baseline · A1 · A2 · A5 PRESENT Decode audience · A1 · A3 · A5 · C FUTURE Foresight simulation, spread-only · A6 · A4 · C MAIN GOAL AGGREGATE SORT REFUSED USABILITY flowing (live) mixed / partial idle or empty reference (not a feed) refused (out of bounds) the focal boundary SOURCE: the house data directory · compiled 2026-08-13 · statuses collapse many per-bucket sources to a dominant reading

The map, in one line. Kinds of data on the left, tagged by how much of each is actually live, pass through the harvest into the boundary gate, and only the aggregate remainder reaches the four instruments. Band X is what the gate turns away. Full row-level detail and the cultural-collections stack live in the house data directory.

The register

Every source the house holds or has catalogued, one row each: its lane, its kind, its status, the type of open it is, and what may leave. The rows at egress never are counted and not listed; they name accounts and inboxes, and the boundary keeps them.

the register

·

source origin lane kind status open type egress items last used by
the house serves

Egress is computed from the lane’s open type, provenance and consent, never typed per row; the register that computes it is docs/data/source-register.json, built 2026-09-08. Items and last are the harvester’s counts for a registry row; a census row has none.

What obtaining it costs

The map above is about what data exists. This is what obtaining it costs, measured once on 26 August 2026: one paged sweep of ten Mastodon tags, through four instances verified keyless, with every post the house declined to keep counted against the reason it was declined.

fig 2 . one sweep, ten tags, and what did not survive the refusals

1,813posts seen
645refused: undiscoverable · 35.6%
126refused: bot · 6.9%
12refused: content warning · 0.7%
4refused: #nobot · 0.2%
1,026kept · 56.6%

1,026 kept + 787 refused = 1,813 seen, over 196 origin instances.

tag queried via seen kept undiscoverable bot content warning #nobot
#mechanicalkeyboardsfosstodon.org20011377910
#birdingmstdn.social20011387000
#sourdoughhachyderm.io20012867014
#fountainpensmas.to20015640040
#vaporwavefosstodon.org200109276400
#cottagecoremstdn.social20092108000
#houseplantshachyderm.io20010988210
#warhammer40kmas.to20088105250
#speedrunfosstodon.org200111404900
#gorpcoremstdn.social1376000
refusal what it means in this run
not-publicvisibility is not 'public'not counted
boosta reblog is not the booster's writingnot counted
content-warningsensitive set or spoiler_text present; the author covered it12
botaccount.bot, self-declared, taken at its word126
nobot'#nobot' in the bio, a convention with no enforcement4
undiscoverableaccount.discoverable is false, the user's own opt-out645

generated 2026-08-26 · from the refusal-audit run · not hand-edited. Two declared refusals carry no count in this run.

The largest branch is a ruling, not a limit. The discoverable field governs whether an account is listed in directories and search; it does not govern reading. Treating it as a signal not to harvest is the house being stricter than the platform asks. It is a ruling rather than a limit, which means it can be changed by one.