Nostr Web Client

💭 Thought of the day… 💭

Once NIP-57 is widely adopted, it will be possible to understand each pubkeys: zaps / events, or zaps / notes

🤔

This should make it easier to filter out a lot of spammers (who would score extremely low on these metrics) and also provides some motivation for everyone to do some negligible level of ⚡️⚡️ to stay above the filter and achieve good reach/persistence on Global. 🙂

Sophisticated spammers (if there is such a thing!! (Yes I know there is🙃)) will then need to monetise 🤣and will need to launder zaps to fake their zap / event metrics.

🙄

But crucially this means that creating a pubkey with high reach now has a cost and any spammer would need to employ working capital in order to launder the metrics and achieve any meaningful reach.

😲

The level of zaps / event can be determined by the user and adjusted to whatever level wipes out the spam from Global.

🤯

We are this close👌to solving spam forever.

Zaps will save the world, one problem at a time.

⚡️ 🌎

Reply to this note

Please Login to reply.

Discussion

Merrcurr⚡️ 2y ago

Your mind is so accurate Stu, i almost want to chip you to harvest data.

And Zappa ⚡️

[776981]

che 2y ago

Does this raise some privacy concerns?

⚡️🌱🌙 2y ago

Do you have different concepts of privacy when we use 👍 that are fiat, or ⚡️ that transmit value?

It’s the same information except we have taken the power of fiat from the spammers.

che 2y ago

That’s a fair point! And I can send sats privately if I wished

Karl 2y ago

They will just zap back and forth between their spam accounts.

Avi Burra 2y ago

I agree in broad principle, but have some concerns about the game theory ensuing from the implementation decisions. If each zap’s sender and zapped amount are both public on a note, I suspect it would reduce the number of zaps sent (no one wants to be seen as a cheapskate and conversely not wanting to bleed the ancestral wealth on frequent large zaps).

Showing only aggregate zap amounts at the note or npub level might be enough to fix this

StackSats.IO 2y ago

Good point, we are going to look crazy for current zapping in future.

This can be configurable though, private/public zaps?

Avi Burra 2y ago

I believe so. Will is working on that for a future release