I'm trying to imagine the use case @opn is exploring. I think it works like this: github
A small server is set up for the purpose of cooperating on a lan, possibly disconnected from the larger internet. A number of users discover this server by convenient means and begin cooperating using some identity that has been conferred upon them by the network. I think some multi-player games work this way and that "lan parties" were once popular for playing them.
To work in this way wiki would need to distinguish reads/writes to a player's own pages and still allow reads of other players' pages. We do something like this now when a user distinguishes themselves by logging into the origin.
It might be that zeroconf delivers enough identity that players could be known by the names they have given their laptops. As I type this my laptop is known as nr.local and I'm ssh'd into au.local. (I name my laptops after my employers.) I just checked, au.local knows nr.local as 10.0.1.195. It might be able to do better if it tried harder with some sort of zeroconf name server reverse lookup.
In the informal setting of a lan party it might be reasonable to equate individual identity with machine identity. DHCP leases numbers and zeroconf adds to that slightly more persistent names.
I have suggested elsewhere that transient identity be manufactured on first contact and stored in the user's browser as a session cookie. See Zero Steps to Claim
This mechanism has the advantage that an individual's manufactured identity is bound to their laptop login, not just the machine configuration. It has the disadvantage that it relies on wildcard addressing which might not be available within zeroconf. We should check.