It’s heavy work for sure on the charge of all current contributors (we would have to change our dev habits quite substantially), though on the long-term it’s worthy and it would avoid a lot of frustrations we’re seeing recently with discussions like consensus changes or OP_RETURN policy changes.
pull down to refresh
zaps forwarded to @standardcrypto (5%) @BITC0IN (5%)
25 sats \ 0 replies \ @kristapsk 3 May
https://github.com/JoinMarket-Org/joinmarket-clientserver/issues/1302
reply
5 sats \ 3 replies \ @OT 2 May
How would you stop unwanted posts from spamming up discussion?
I like how no one can get banned from nostr.
reply
33 sats \ 1 reply \ @theariard OP 3 May
ask every post to be counter-signed with a pubkey committed in a scarce utxo.
if too much spam posts originating from the pubkey, your client down scores the utxo.
now minimal fee cost on the spammer to get a new fresh utxo.
https://www.freehaven.net/doc/oreilly/accountability-ch16.html
reply
23 sats \ 0 replies \ @theariard OP 3 May
you have 4MB weight unit block and 10 min in average block time.
enough foundations to build internet-large anti-spams.
can ask the scarce utxo to be older than X blocks.
no need for everyone to have the same anti-spam policy, it’s a client-side config.
reply
0 sats \ 0 replies \ @jb55 3 May
deleted by author
0 sats \ 0 replies \ @88b0c423eb 2 May freebie
great idea