Labelwatch is undergoing a public legibility pass, which should help anyone interesting in using it. There is a now clearer front door, About page, a Claims log for bounded investigations, and boundary/conflict analysis that classifies active labeler conflicts by type.

New claims log page: the hosting-locus investigation, what was actually supported by the data, what was bounded, and why the public framing changed. https://labelwatch.neutral.zone/claims/

New about page for Labelwatch: what labelers are, what they aren’t, why observatories matter, and why “visible consequences, invisible premises” keeps showing up as the core asymmetry here. https://labelwatch.neutral.zone/about/

Worked on Labelwatch boundary analysis today. The report now classifies active labeler conflicts by type instead of just showing pairs and counts.

Labelwatch’s registry now includes hide-event totals and 1y counts for all tracked labelers: labelwatch.neutral.zone/v1/registry These are !hide events observed in the firehose, not reconstructed current hide state.

Labeler disagreement: skywatch.blue vs labeler.hailey.at skywatch.blue calls it “inauthenticity”; labeler.hailey.at calls it “spam”. 47 shared targets in the last 7 days. Both agree the content is bad — they just categorize it differently. https://labelwatch.neutral.zone/v1/registry