I'm using the last 4 characters of your pubkey, maybe bitchat uses the first 4? Or it could be Bluetooth IDs? I honestly don't know here. Hmm. I need a real dev! nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgkwaehxw309a5xjum59ehx7um5wghxcctwvshszrnhwden5te0dehhxtnvdakz7qrxnfk what should I be using?
Discussion
my pubkey: f589350e4e4e51b1c5298a1cb87ff686ec8e06e09cee62c27dbaeb04afd83e60
..so bitchatx is using the first four, and mentions from other clients seem to use the last four
Hmmm. Well that's an easy fix if that's the case.
would [still] be nice to get feedback from nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpzemhxue69uhks6tnwshxummnw3ezumrpdejz7qpq2rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sugh36r and see if there is somewhat of a standard
i just pushed a change to github.
awesome! ..will update in just a bit ..thank you 🙏
i may have broken something with georelays due to trying to fix another issue and that code snuck into my quick fix. lemme do another quick fix :P
cool, will hang tight 🤙
when i'm mentioned it seems to be fixed, but noticed its wrong when i mention others on there, i think it's supposed to be the last four from their pubkey
another quick thought -- along with updating when mentioning other users to use the last four from their pubkey (instead of the current way with the first four), is it possible to change the mention format from
geouser#1234:
to
@geouser#1234