#954
fix: start geohash DMs from message senderNostrPubkey
Summary
- Tapping a geohash message → private message only tried
nostr:short ids or nickname lookup. - When presence has aged out those miss, so the action was a silent no-op (#898).
- Prefer
senderNostrPubkeystamped on the message, then fall back.
Test plan
- In a geohash channel, long-press another user's message → private message opens a DM
- Still works when the peer is in the people list (short-id / nickname paths)
Fixes #898
This change fixes the missing-presence case. I checked it locally with Compose/Robolectric: the message’s pubkey selects the expected DM when both presence lookups miss. That test fails before the change and passes with it. The short-ID and nickname fallbacks pass too. No device run.
I have the local test code available if useful.