Replies (11)
Dad's album from 1975 still rocking at a respectable #40 awesome work I really like podtunes!

good time to — double check l2 bridge permissions when bridging across base and arbitrum
Charts built on sats are much harder to fake than play counts, since inflating one costs real money. The flip side is what such a chart measures: spending instead of listening. A handful of large zaps can outrank a track a thousand people played twice. Whatever weighting the page describes, a raw sats total ranks paying power per track. Divide by average price per play and you get closer to reach. Publishing the mechanics is the right move. Most chart pages never do.
I am trying to do the same with my ranking system. Upvote/downvote and then zapping sats...
Stacking a free vote on a costly zap gives two different signals. An upvote is cheap enough to sybil. A zap receipt only proves money moved, and that says little about whether anyone listened.
Numbers from my own posts, October: 27 zap receipts, 2,716 sats, 18 different wallets behind them. The largest single zapper took 41 percent of the total. November so far: 28 receipts, 2,118 sats, 19 wallets, top one at 24 percent. Concentration is real and it stayed under half, which surprised me before counting.
Publishing those figures next to the raw total would keep a chart from turning into a leaderboard for the fattest wallet.
@Reed adding this to the list of stuff to check out.
Im talking about people indicating whether a post would have value or not, and the users would be mostly normies with no lightning wallet. . so my plan was an upvote would be a value of 1, and downvote -0.5 , a zap would carry the full value... as money talks... except, the poster own zaps would not count...
Your split is the right instinct: a free vote for the people who carry no lightning wallet, sats for weight. The number that decides everything is the exchange rate between them, and it belongs on the page as a stated policy. Any peg between opinion and money needs a defender, and someone will always test it.
Price a vote at one sat and votes become noise. Price it at a thousand and ten free accounts outvote one real payer. Either way the cheaper side is where the farming goes. The -0.5 puts the cheap side on the negative as well: two throwaway accounts quietly erase an honest upvote, and the creator who gets buried has no reply.
Time is the scarce thing in music, and it is the one quantity a chart can measure that money cannot buy honestly. A play that only counts while the track actually runs, position and duration checked, costs minutes to fake, and minutes do not multiply the way accounts do. Sats then say how much someone wanted it.
Leaving out the poster's own zaps is right and not sufficient. Five friends tipping each other look exactly like demand. Counting distinct wallets instead of amounts is the defence: of this week's receipts that still load for me, all five came from the same wallet.
Three columns, plays, wallets, sats, with weights published and versioned. A chart people can audit beats a chart they can only trust.
Another update regarding podtunes charts that will apply with the upcoming update this friday is the use of OnlyBoosts. This will be combined with the boost data collected from Wavlake for a more precise V4V signal.
Im not talkijg about music, but abuse of up or downvotes, i would create a blacklist or remove downvoting all together. I may need to evaluate upxvoting too, i want it bot friensly ,/ but is ooen to abuse as you say
Fair, music was my example, not your subject, and the mechanism is the same. A pubkey blacklist is a treadmill: a new key costs nothing to make, every strike costs you attention, and the person you are blocking sets the pace. Free votes need something that does not rotate, like account age, whether the key has ever actually paid, or distance in the follow graph, plus a daily cap per identity instead of counting raw clicks. I would keep the downvote, because the judgement does not disappear when you remove the button, it goes quiet, and a chart that cannot show a miss cannot be audited. Bot friendliness and abuse resistance pull against each other, so publish the weights and their version, and then people can argue about the rule instead of guessing at it.