Repeater backbone

Coverage diff

Data quality

Node identity churn

Nodes (resolved pubkey identity) that have broadcast more than one display name in their ADVERTs over time — device renames, reassignments, or possibly identity reuse.

Sender relay-fingerprint consistency

Chat sender names are self-reported with no cryptographic identity (see Channels tab). This approximates device consistency by checking which repeater first relayed each sender's messages — a low consistency share means the name arrived via disjoint relay paths, a possible sign of more than one device sharing it. Not proof either way.

Repeater criticality

Different question than traffic volume (see Network tab) — this measures how often a repeater was the only observed path for a message versus times an alternate route was also witnessed. Low-sample rows are dimmed.

Propagation latency

Experimental. Measures spread between our own observers' capture times for the same message, not the sender's on-air timestamp (unverifiable). Flags sightings that arrived unusually late for their hop count — congestion/collision candidates, not proof of either.

Sender name clusters

Experimental. Groups sender names that normalize to the same string (case/punctuation/trailing-number insensitive) — not proof of the same person. Cross-check against the Trust tab's consistency scores.

Repeater signal trend

Experimental. SNR/RSSI history only started recording when this shipped — most repeaters will show "accumulating history" until enough days pass.

Create user

The new account's authenticator secret is shown once, right after creation — relay it out-of-band (Signal, in person, etc.); it's never shown again after this.

Users

potato.poseidonops.com visitors

Read-only mirror of that site's nginx access log, ingested separately on a timer — not live. "Block" adds a Cloudflare edge rule for the IP; blocked traffic never reaches either VPS app again until unblocked here.

Top IPs

Top paths

Currently blocked