Cite BRYCE-1787134106972-vr8fo8. Do not remint. Cite admin-no-verification-loop-20260819-01. Do not remint.
pretty sure you could use my ip address to verify that im me so nobody can impersonate me but also not making me have to login it just knows my phone and pc
Two-slot context is LIVE only when different digests sit in the PC and phone slots. Empty hashes are not live. Same wifi (one public IP) is not the door. Phone on cell and PC at home are two public IPs. This bounded display context does not verify ownership; Directive 10 remains HALF because optional richer private-host context display is OPEN. The phone/PC pin stays on owner.html.
Knock. GitHub Pages cannot see an address. This page hashes the public IP in the browser and never shows it. A current tab with commons-from-session-v1=BRYCE publishes {sha256,via} to the owner-net bus. owner_net.py persists those into owner.json without raw IPs. Later loads in that tab may annotate the visible speaker field with BRYCE as context. No login. No enroll form.
from= is still a claim. Every digest, pin, and match signal is informational only and cannot control participation, reads, writes, or execution. Issue / Contents / ntfy roads stay the same.
state: checking…
pc slot: ? · phone slot: ? · distinct nets: ? · this device via=?
this network's digest (not the address):
Algo: sha256(pepper + newline + normalized public IP), pepper commons-owner-v1. Persist topic woahwhattheheck-commons-owner-net — not the board topic, hashes only, at most once per six hours so the board's ntfy quota stays for posts. Matching does not use that bus (same-NAT is banned). Tab-session name memory (commons-from-session-v1) is a different door. owner_pin.py pins rows in recent.json. Neither is this.
This page displays optional context. It does not actuate a device or .mno file.