Nostr Web Client

what is the average person expected p tag count for nip-17 events?

nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug nostr:nprofile1qqspycgrhlwu3he9ddhq407h7duheqxucn4g3a7zlp7agyzzyz6dvhcpzdmhxue69uhhyetvv9ujuun909sjuum4k6ff74 nostr:nprofile1qqs84k6jpsav0jmdeqjn2zxlpnsajaw6f8l0m2d4e9t8gjsyn53s4nspzamhxue69uhhyetvv9ujuumfv9khxarj9e3k7mgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmnyhat8ky nostr:nprofile1qqs2js6wu9j76qdjs6lvlsnhrmchqhf4xlg9rvu89zyf3nqq6hygt0spz9mhxue69uhkummnw3ezuamfdejj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uygje4n

#dev #devstr #asknostr #nip17

Reply to this note

Please Login to reply.

Discussion

Vitor Pamplona 8mo ago

100s. Big accounts are in the thousands. Mine? 15K events.

کیهان 8mo ago

umm, i think you misunderstood. i meant the number of p tags on a giftwrapperd event when we send nip-17 dms. how many p tags we can expect? 1,2? or more?

Vitor Pamplona 8mo ago

Just one. It's always one GiftWrap for every key in the group.

کیهان 8mo ago

seems complex. it's pubkey of sender or receiver?

Vitor Pamplona 8mo ago

There is always two: one wrap for the sender and one wrap for the receiver.

کیهان 8mo ago

oh. got it. thank you.

any reason for this? i was trying to use p tags to find a spam protection way for nip-17. this rule ruins everything.

Vitor Pamplona 8mo ago

It was designed to decouple sender and receiver from any public information. So, it will be impossible to know if the wrap is legit or spam from just looking at the event.

You could ask the sender to AUTH when submitting the event and filter by the authed user. However, the authed user might not have anything to do with the message and you also make it less private when you do so.

کیهان 8mo ago

i was thinking about this approach. but how about receiver event? we miss that? because we can't auth instead of the receiver.

Vitor Pamplona 8mo ago

The receiver relay gets the gift wrap encrypted to the receiver while authed as the sender (some clients will not auth in this case because it breaks privacy).

The sender relay gets the gift wrap encrypted to the sender while authed as the sender.

کیهان 8mo ago

lets assume my inbox is jellyfish relay which is paid. and im subscribed there.

you want to send me a dm. if the relay only checks the p tag, anybody can send me dms and spam me.

but if check the sender is subscribed as well, it can control who is sending the dm.

my last idea (which i think you believe hurts the privacy): make sure the publisher is whitelisted using auth.

if people trust that the relay won't log the information, it won't hurt the privacy.

Vitor Pamplona 8mo ago

I think that works. You can build a WoT of your members. Then when a message is received, you request an AUTH and you check if the authed key has a good enough WoT for the p-tag.

If the sender doesn't have enough WoT, you could place it on a wait-list and ask them to pay a lightning invoice to temporarily buy WoT. You could use the NOTIFY nip to make it visible to the user.

Then you can delete that info once the transaction is done.

Niel Liesmons 8mo ago

I'm fine with AUTH and/or PAY for these kind of messages.

:pointright: Inbox relay solution that I can set a price tag on for npubs that I don't have in my network / white list / ....

کیهان 8mo ago

publication fees are too complex and non-standard. but a auth would work.

Niel Liesmons 8mo ago

True. Probably the easiest is to AUTH and then have an auto-send invoice (in a Nip-17 mail) when your not in my network.

کیهان 8mo ago

or maybe this:

nostr:nevent1qqsqtjj8aqa2wx6hpcvkadhazfztz0y9w2cnfnwzfcelqy9egnmr9fcpz9mhxue69uhkummnw3ezuamfdejj7q3qh49w8en79xty6j2pwgnpm3znjhyf767jua6xgt3kvyn3w80ms86sxpqqqqqqza5vxw3

Niel Liesmons 8mo ago

Good that you are thinking about spam within this specs context :prayinghands:

کیهان 8mo ago

thanks. :salute: