Do social clients understand naddr1qpqrvvfnvccrzdryxgunzvtxvgukge34xfjnqdpcv9sk2desxgmrscesvserzd3h8ycrywphvg6nsvf58ycnqef3v5mnsvt98pjnqdfs8ypzq3huhccxt6h34eupz3jeynjgjgek8lel2f4adaea0svyk94a3njdqvzqqqr4gudhrkyk ?
For devs who want to earn 2 million sats, please visit https://nostrbounties.com/b/naddr1qpqrvvfnvccrzdryxgunzvtxvgukge34xfjnqdpcv9sk2desxgmrscesvserzd3h8ycrywphvg6nsvf58ycnqef3v5mnsvt98pjnqdfs8ypzq3huhccxt6h34eupz3jeynjgjgek8lel2f4adaea0svyk94a3njdqvzqqqr4gudhrkyk ...
Where did you get this nAddr? I am confused on why it is different than your other post id
That's not a kind-1 event but a parametrized replaceable event which is addressable by author, kind and d-tag which is encoded in this naddr string. I can't quickly find a decoder :(
I know, my issue is that you seem to have 2 long form posts with the same title but two addresses.. 1 can be seen in Habla news and another in the bounty site. Neither site sees each other's posts. Amethyst only displays the habla news version.
The bounty site might be publishing to relays the app doesnt use.. or there is something else going on.
I'm confused. Can you show me the two nAddresses? I did edit my post a few times but I did not knowingly create two bounties and certainly not using Habla.
This is habla: https://habla.news/a/naddr1qq9rzd3h8y6nqwf5xyuqygzxljlrqe027xh8sy2xtyjwfzfrxcll8afxh4hh847psjckhkxwf5psgqqqw4rsty50fx
This is NostrBounty:
Look at the naddr1 in the url. I think Habla is addressing it correctly and NostrBounty is either wrong or has a new post, with a new id, for it. But I cannot find this new post anywhere.
I need to decode the bech32 now. Why is there no online decoder yet? Should I launch a bounty or is there one?
I suspect these reference the same post but using some slightly different semantics. Does nostr have a malleability issue?
It shouldn't, the naddr spec is very clear. If they are the same, they must have the same naddr. They definitely have different d tags. But I cannot find the original NostrBounty JSON to be sure. If so, then they are two separate events.
```
> nip19.decode('naddr1qq9rzd3h8y6nqwf5xyuqygzxljlrqe027xh8sy2xtyjwfzfrxcll8afxh4hh847psjckhkxwf5psgqqqw4rsty50fx')
{
type: 'naddr',
data: {
identifier: '1679509418',
pubkey: '46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d',
kind: 30023,
relays: []
}
}
> nip19.decode('naddr1qpqrwve3v56nxv3cxv6nvdeex9jrzctyvdskgcnyvcck2ce5xcekydrpvvungvf4v33njwfkvcmnjcf4vvmn2vrpxqenscnxxe3rwef4xgpzq3huhccxt6h34eupz3jeynjgjgek8lel2f4adaea0svyk94a3njdqvzqqqr4gukgahaj')
{
type: 'naddr',
data: {
identifier: '731e5328356791d1adcadbdf1ec463b4ac9415dc996f79a5c750a038bf6b7e52',
pubkey: '46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d',
kind: 30023,
relays: []
}
}
```
weird.
It's likely two different posts, the latter has an derived identifier from the post itself while the first one has a custom identifier (which should be d-tag in the event). Some clients posts to Relays that doesn't implement NIP-33 and that can cause some issues.
No, it's just a bug in the code: https://github.com/diamsa/nostrbounties/issues/2
Instead of metering by number of events, wouldn't it be better to meter by number of queries and complexity of queries?
"milliseconds spent on queries" tries to capture that. We can always refine it further. For example, measuring the ms/query is close to what I want to measure - server load - which can increase for the same query when the overall server load is high and there can be race conditions and bugs, punishing users and of course that needs to be fixed but long term I see "happy hour" metering and much more sophisticated metrics to totally be a thing.
Added to the bounty: #[0]
