Nostr Web Client

I've been looking at this. As open as OSM is, I wonder if there is a less centralized way of addressing places.

The geo: URI scheme seems like a good approach to store in nostr events, which can later be combined with a reverse Nomatim lookup to resolve it to, for instance a local business: https://nominatim.openstreetmap.org/ui/reverse.html?lat=53.56881&lon=9.96773&zoom=18

The issue with nodes is, what happens when a local business moves? Afaik there are two approaches, some people prefer keeping the node with the building and others with the business.

nostr:npub1arkn0xxxll4llgy9qxkrncn3vc4l69s0dz8ef3zadykcwe7ax3dqrrh43w what's your view on all this?

arkinox 1y ago

I appreciate you including me on this. This is a nuanced topic. IMHO:

- OSM is a centralized database

- OSM contains way more data than nostr needs

- The places NIP lets people own their location and edit it: https://github.com/nostr-protocol/nips/pull/927

- it also will allow for OSM tags to be applied to nostr places by the owner or by crowdsource; the client decides how to interpret these

- "official" places have the same problems and solutions that "official" identities have. Verifying a pubkey gets you the official location if such a thing exists. Other heuristics can filter lower quality places in favor of better curated ones, or high quality place-serving relays can supply a good base map. Many ways to do this.

- generally, I don't see a need to tie anything to OSM. I'd rather see people copy places that matter over to nostr. Satlantis.io is doing this using the Places NIP.

I wish I had time/money to work on this but things haven't worked out.

Reply to this note

Please Login to reply.

Discussion

franzap 1y ago

Fantastic, thank you!

I hope you find a way to keep working on this, Opensats could be an option for you

Alekandar Svetski 1y ago

nostr:npub1sy70twa0vadtk8hjs6wt2hmfszduj04tw78ccs3ktmr9u99mfmqsj62srx, the team & I will help bring this to life my friend!