You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I send REQ with #t: ['photography'], I receive plenty of results. But if I send #t: ['photography', 'photogr'], the results are empty. For some reason, the unmatched substring tag cancels matched full tag.
Sending REQ#t: ['photo', 'photography'] returns results with photo tag, results with both tags, but doesn't return results with photography only.
The same happened with #g tag (geohash).
Expected results
When I send REQ with #t: ['photography', 'photogr'], I would expect to receive events with ['t': 'photography'] tag.
Context
I tested and reproduced this issue against relays wss://relay.damus.io, wss://nostr.wine, wss://relayable.org with issues.
Tested against wss://lightningrelay.com which uses different software, without issues.
It looks like the issue is with this software, but I'm not sure.
Used nostr-tools to send the requests.
Thank you!
The text was updated successfully, but these errors were encountered:
Hello!
Bug
When I send
REQ
with#t: ['photography']
, I receive plenty of results. But if I send#t: ['photography', 'photogr']
, the results are empty. For some reason, the unmatched substring tag cancels matched full tag.Sending
REQ
#t: ['photo', 'photography']
returns results withphoto
tag, results with both tags, but doesn't return results withphotography
only.The same happened with
#g
tag (geohash).Expected results
When I send
REQ
with#t: ['photography', 'photogr']
, I would expect to receive events with['t': 'photography']
tag.Context
I tested and reproduced this issue against relays
wss://relay.damus.io
,wss://nostr.wine
,wss://relayable.org
with issues.Tested against
wss://lightningrelay.com
which uses different software, without issues.It looks like the issue is with this software, but I'm not sure.
Used
nostr-tools
to send the requests.Thank you!
The text was updated successfully, but these errors were encountered: