Thanks for clarification, I didn't consider that. The way spammers would win in that scenario is still through volume I would think, where curating takes time repeatedly, and spamming algorithmically takes time once. If the controls are on the user side or the user has options (using nostr.band statistics to show 'probable spammer' overlay, filtering by zap amount) each can have his own. It should be up to the community and not baked in - and perhaps there would be a reasonably workable model for capping or weighting that some would choose.