I think this is actually ok, because while geohashes are an ID, it's an ID that applies to potentially many events, so it makes sense to filter by the l value.
Building off daniele's example:
```
{
"kind": 40,
"tags": [
["L", "geohash"],
["l", "9qqj3", "geohash"],
["e", "10fbc672..."]
],
"content": "I'm tagging the location for this event",
...
}
```
This could work? But geo clients need to implement it/expect it.
nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn what do you think? Is this misuse of labels? 🤔 feels like a hack kinda but maybe not
Discussion
It's an ID and it is also technically a label too. Yeah. 👍
I feel like something special just happened here. Nostr grew a little. Go forth and tag!
You guys rock!
This just in: you can use NIP-32 to slap a geohash onto anything on nostr. I'm excited!
Go forth and label the world!