Connor McCormick ☀️
@nor
Got more WhatsApp spam so I'm here to say this again: A great pattern to prevent spam is to require a stake to send a message which can optionally be slashed by the recipients (where the tokens are destroyed). Required stake size can vary based on account reputation and other signals
2 replies
0 recast
7 reactions
Connor McCormick ☀️
@nor
1 reply
0 recast
1 reaction
Connor McCormick ☀️
@nor
Good discussion with @weeoo about this here https://warpcast.com/nor/0x21b527db
2 replies
0 recast
0 reaction
Connor McCormick ☀️
@nor
1 reply
1 recast
0 reaction
Dan Finlay 🦊
@danfinlay
You could do a version of this with gator.metamask.io where it doesn't cost a tx fee to "stake" (extend allowance). Allowance would have to be active to be visible, and the reader gets to determine when the "race" to withdraw begins, and so achieve good safety if they have a bundler they trust.
2 replies
0 recast
2 reactions
Dan Finlay 🦊
@danfinlay
I could make that feature's backend, but since I don't want to maintain a fc client, how would I go about monetizing it so the infra could pay for itself? .. We could run it off an API that takes a small fee off any stake slashed, although that might pervert our incentives to encourage bad messages lol.
1 reply
0 recast
1 reaction
Dan Finlay 🦊
@danfinlay
"I want to improve this software with one feature but not inherit the whole codebase or have to hard fork its community" is the major social challenge that a good monetized plugin system solves. Commoditize plugin systems. Hoot 0.5.0 is an exciting step forward. https://spritely.institute/news/guile-hoot-v050-released.html
1 reply
1 recast
2 reactions
