If # is the character to start a hashtag, what is the character to start a geohash?
For instance, if we use ∆, then every time somebody writes ∆, it turns into the City name with a link that opens all notes that tagged that city.
Same character can bring up a list of locations just like @ brings up a list of user names.
Ideas?
I would just use #
That's already been used for hashtags. It wouldn't be able to know if you are looking for a hashtag or a geohash
That's only ambiguous for a tiny number of geohash, sucks to live in #lol
And then maybe even be smart and when some searches for a hash of a known city or country name, return anything with the corresponding geohash too.
That's a pretty clever idea, though I would prefer ^ as it's more easily accessible on most keyboards that I use.
$ since we’re going to need a new use for it anyways.
maybe this _
_ is commonly used as a placeholder, so "place" "holder", you know.
It only activates when there is a space before it
Something like nip-30 would be great 😌
It needs to be easy to type. It must exist on all keyboards.
! works for me, it’s like a pin, as you mentioned in another reply. Regarding NIP-30, I think it would be great if we could link the geohash in the content with a ‘g’ tag and add information such as the place name. We could render its name directly without decoding it or relying on other services that mostly return only the country or city name. This would allow us to specify the place’s name ourselves if we want, similar to POIs on Google Maps.
I like this one: §
° degrees character, for latitude longitude?
^ or ~ for geohash.
nostr has a super power call tags, it's amazing so we don't have to infer weird and new and arbitrary meanings in what people want to say, we can just neatly put them in a proper structure with well defined meanings. going the route of adding more and more on raw string data that may or may not be what we expect just removes freedom for the person writing because everything turns into something else and creates really hard to interpret parsers that now need to jump through hoops hoping for few false positives. if it is defined in tags, there's no more doubt and clients can freely expand on that, instead of trying to guess and interpret every word into a trigger. I already see a lot of bloat trying to interpret anything as a URL and auto inserting it into tags, this will just compound.
Terrible idea: % could represent lat/long degree locatioms
How about ¿
How about ! to represent the location? The exclamation mark is similar to the pin emoji 📍 and could be converted to the pin when used. For example:
!new-york,usa
It is turned into:
📍 New York, USA
# and @ are the only easily accessible keyboard characters that have a “block” design and so are easily recognized without getting in the way of the next word.
I would use a double #:
##venice
Or maybe !#:
!#venice
(slower to activate, but ! remind the map pin)
