My point wouldn’t be about blocking. It’s more about a client tuning in to the noise and give “far away” notes less priority. Like in real life where you need to go somewhere to hear a person speak.
The scaling factors of a note could be: distance and noise (real people get soar throats and cannot scream the whole day, this helps against spam) overridable by the listener.
Tags are discrete and not numeric. Location and loudness would be aggregatable, calculatable, interpolatabe.
In that case different algorithms for distance could be used instead of just geographical location.
Yes. And the main point would be that one npub has to commit for a locality. Moving could be possible, but would have opportunity costs attached: you loose access to the old locality. And moving too often could be considered spammy.
This could be a metric for a public reach equilibrium. An elastic system.
Certainly always overridable by the clients (e.g. by fellowship).
